Run a custom pipeline
Run a registered multi-step pipeline (e.g. v2vStitch). Pipelines are
access-gated per account — contact varg to get access to a pipeline.
The model field is the pipeline name; remaining fields are defined by
the pipeline’s own input schema (discover it via
GET /tools/pipeline?model=<name>).
Authorizations
varg API key (varg_...). Get one at app.varg.ai
or run bunx vargai login. App sessions may alternatively send a
Supabase JWT.
Headers
Any unique string. Retrying a request with the same key returns the existing job (HTTP 200) instead of creating and charging a new one (HTTP 202).
Body
The pipeline name
"v2vStitch"
Response
Idempotency replay — the existing job for this Idempotency-Key (no new charge).
"job_a1b2c3d4e5f6"
Lifecycle is queued then submitting then running, ending in a
terminal status (completed, failed, or cancelled).
queued, submitting, running, completed, failed, cancelled "image"
The request body as submitted (model, prompt, ...)
Canonical output envelope. Present only when the job is completed.
"stitching 3/8 (40%)"
Fraction 0..1
Structured pricing. 1 credit = 1 cent = $0.01.
"fal"
"fal:flux_schnell"
The provider's raw status string
Lifecycle URLs (present on creation responses)