Run published community genjutsu through the API. This page lists every genjutsu that is currently available, together with the JSON payload schema and the endpoints used to list, inspect, execute, and poll a genjutsu run.
Endpoints
Community genjutsu are exposed through a dedicated set of endpoints. Every request must include Authorization: Bearer bd_YOUR_API_KEY. Replace {WORKFLOW_ID} and {RUN_ID} with the values returned by the list and execute calls.
Use this call to read the input schema of a single genjutsu. Each public input node exposes a config.input.key — that key is the property name you send inside input when executing the genjutsu.
Execute payload
Execution is asynchronous. Send an input object whose properties are the public input keys of the genjutsu, plus a unique Idempotency-Key (header or idempotency_key body property). Active execution returns HTTP 202 with a workflow_run and a status_url.
json
{
"input": {
"<input-key>": "value or https:// URL for image/video inputs"
},
"idempotency_key": "unique-string"
}
Text inputs take a plain string. Image and video inputs take a public HTTP(S) URL — upload the file first (see Upload Files) and pass the returned URL. Reusing the same key with the same input does not create another run; changing the input with the same key returns 409. The creator-test: prefix is reserved.
Poll run status
Poll GET /api/v1/workflow-runs/{RUN_ID} until the current stage finishes, then call POST /api/v1/workflow-runs/{RUN_ID}/continue to start the next stage. Repeat until the run is COMPLETED or FAILED. Only runs created with your own API key can be retrieved.
Expand a genjutsu to see its input JSON Schema, a ready-to-run payload, the matching cURL request, and the response format. Credits shown are estimates — the final charge is computed when the run executes.