| title | Docs for the media processing API | |||||
|---|---|---|---|---|---|---|
| sidebarTitle | Overview | |||||
| description | Start with the quickstart, then browse job types, storage connections, automation platforms, and the SDK, CLI and MCP server. | |||||
| icon | book-open | |||||
| keywords |
|
|||||
| boost | 2 | |||||
| canonical | https://rendobar.com/docs |
Rendobar runs media jobs on our infrastructure and hands back a finished file. You POST a job with your inputs, we execute it on isolated cloud workers, and you collect the output by webhook or by polling. One endpoint covers raw FFmpeg, media inspection, timeline composition, compression, captions, and image generation.
Submit your first job, poll it to completion, and download the result. Hand your coding agent one prompt and let it write the integration.Every job shares the same shape, whatever its type. Read how a job works for the lifecycle and the output contract, scopes and access for what an API key is allowed to do, and credits for how work is billed.
Results arrive two ways: webhooks for signed delivery to your endpoint, or callbacks when you want the job to call your own service.
Run any FFmpeg command in a sandbox, with guardrails. Probe media metadata from a URL, normalized plus raw. Render video from a declarative JSON timeline. Shrink a file to a target size or quality budget. Burn static subtitles or animate word-level captions. Generate, edit and upscale images on hosted models.Connect a bucket you own and jobs read inputs from it and write outputs back, so your files never need to be public. Start at storage connections, then pick your provider: Cloudflare R2, Amazon S3, Supabase, or any S3-compatible bucket.
Run jobs from n8n or Activepieces, no code required. TypeScript SDK, plus the rb command line tool. Let Claude, Cursor and other agents run jobs directly.Check the FAQ first, then error codes to handle failures by machine code rather than message text. Limits covers plan caps, and versioning covers how the API changes.