Product / Capture
Connect your tools. We remember what they made.
The best production record is the one nobody has to keep. Connect a tool once and every generation arrives with its prompt, model, seed, and workflow - captured at the source, the moment it exists.
Start capturing for freeSix ways in.
How does Archibal capture AI generations? Archibal connects to generation tools - every tool Claude orchestrates (Higgsfield, fal, Runway, Kling, ElevenLabs, Gemini, Replicate) through the Claude connector, ComfyUI through the Archibal node, developers' own pipelines through the API, and Frame.io for review events - and records each generation's model, prompt, seed, and workflow automatically at the moment it is created. Files made elsewhere join by upload.
Claude
Paste one connector URL into Claude settings. Every generation Claude orchestrates through any tool it is connected to - Higgsfield, fal, Runway, Kling, ElevenLabs, Gemini, Replicate, Comfy - lands in your project with its prompt, model, and file, unprompted.
ComfyUI
Local or Comfy Cloud. The Archibal node pushes renders straight from the graph; embedded workflow metadata is parsed either way - models, seed, references, the full recipe.
Runway API
For developers whose own code calls the Runway API: pass the Archibal webhook with each task and the render arrives with its model. Work made in the Runway app reaches Archibal through Claude.
Frame.io
Review comments, approvals and new versions become part of the record - the review trail rides along with the provenance.
Your own pipeline (API)
Render farms and in-house tools log each job through the Archibal API with an API key - matched to files by name or fetched from result URLs, recorded as studio-logged.
Upload
Add material from outside: Archibal reads what a file still carries - embedded ComfyUI workflows, generator metadata, signed Content Credentials (Adobe, OpenAI, Google, ElevenLabs and others). Finished exports usually carry nothing; connect tools to keep the history as work is made.
Files made elsewhere still join the record: uploads are scanned for embedded workflows, generator metadata, and signed Content Credentials.
Honesty by construction
Not every channel earns the same confidence - and the record says so.
A render with an embedded workflow graph is stronger evidence than a vendor webhook, which is stronger than a pipeline log, which is stronger than a person's word. Archibal grades every capture - attested, integration-reported, studio-logged, or user-declared - and the grade travels with the file into every delivery and verification page. Nothing is silently upgraded, and an unrecognised model stays labelled unknown - flagged for identification, never marked clean.
More on grades at Verification.
Frequently asked
Which tools can Archibal capture from?
Claude through the Archibal connector, ComfyUI with the Archibal node, your own pipeline through the API, and Frame.io for review events - which covers every tool Claude orchestrates: Higgsfield, fal, Kling, Gemini, Replicate, Runway, ElevenLabs, Comfy. Plus a plain webhook for anything that can POST a file, an orchestration-log import for studio pipelines, and direct upload, which reads embedded recipes and Content Credentials.
Does capture change my creative workflow?
No. You connect a tool once and generation happens exactly as before - capture is a side effect. There is no manual logging and nothing to remember mid-session.
What if a generation arrives without full details?
It is still captured, and the record says exactly how much is known. Every claim carries its evidence grade - attested, integration-reported, studio-logged, or user-declared - and an unknown model stays labeled unknown rather than being silently marked clean.