POST a YAML, get an MP4.
Programmatic rendering for CI, agents, and dashboards. Bearer-authed, JSON in / JSON out, pollable job status, signed URLs for the artifact.
POST /api/v1/renders
Accepts a project ID for a stored YAML, or raw YAML in the body. Returns a job ID and a status URL. Poll with GET /api/v1/renders/:id for status; the job goes pending → running → succeeded with an mp4Url.
Every render of this feature is deterministic. Capture writes the metadata; the composition reads it. Re-render after a UI change to get the new output without re-recording.
curl -X POST https://capturebeam.com/api/v1/renders \
-H "Authorization: Bearer cb_live_…" \
-H "Content-Type: application/json" \
-d '{ "projectId": "prj_a1b2c3" }'
# Or send raw YAML:
curl -X POST https://capturebeam.com/api/v1/renders \
-H "Authorization: Bearer cb_live_…" \
-H "Content-Type: application/yaml" \
--data-binary @demos/onboarding.yamlGET /api/v1/schema
Returns the JSON Schema (draft-07) for a demo.yaml plus a quickRef summary of step types, target examples, presets, qualities, and aspect ratios. No auth — agents can read it during evaluation.
Every render of this feature is deterministic. Capture writes the metadata; the composition reads it. Re-render after a UI change to get the new output without re-recording.
Soft caps, not hard ones
RENDER_CONCURRENCY_PER_USER (default 3) and RENDER_YEARLY_SAFETY_NET (default 5000) protect against runaway scripts. Both are advertised as 'unlimited fair use' because real usage rarely approaches the cap.
Every render of this feature is deterministic. Capture writes the metadata; the composition reads it. Re-render after a UI change to get the new output without re-recording.
Render with Render API.
$19.99/mo or $199/yr. Render through the dashboard or via the API — same access either way.