Skip to main content

Documentation Index

Fetch the complete documentation index at: https://rendobar.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Get an API key, submit a raw.ffmpeg job, poll until complete, download the output.

​
1. Get an API key

Sign up at app.rendobar.com and create a key from Settings → API keys. Keys start with rb_. New accounts get $5 in free credits. Prefer the terminal? Skip steps 2–4 and use the CLI instead.

​
2. Submit a job

curl -X POST https://api.rendobar.com/jobs \
  -H "Authorization: Bearer rb_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "raw.ffmpeg",
    "inputs": {},
    "params": {
      "command": "ffmpeg -i https://example.com/video.mp4 -vf scale=1280:720 -c:v libx264 -preset fast -crf 23 output.mp4"
    }
  }'
Put input URLs directly in -i flags. The output format is inferred from the trailing filename (output.mp4 → MP4). Response: 
{ "data": { "id": "job_abc123", "status": "dispatched" } }

​
3. Poll for completion

curl https://api.rendobar.com/jobs/job_abc123 \
  -H "Authorization: Bearer rb_live_YOUR_KEY"
Statuses: waiting → dispatched → running → complete | failed | cancelled. Poll every 1–2 seconds. For push instead of poll, configure a webhook.

​
4. Download the result

When status is complete, the response contains outputUrl — a signed R2 URL valid for one hour: 
{
  "data": {
    "id": "job_abc123",
    "status": "complete",
    "outputUrl": "https://r2.rendobar.com/...",
    "cost": { "nanodollars": 50000000, "formatted": "$0.05" }
  }
}
Re-fetch the job to refresh the URL after it expires.

​
What’s next

  • Rendobar CLI — skip the curl, run rb ffmpeg from your terminal
  • Authentication — keys, sessions, MCP auth
  • Raw FFmpeg — full guide with the security model and examples
  • Webhooks — push events instead of polling
  • Credits — plans, balance, billing
  • MCP — drive Rendobar from an AI agent