Video background removal for scripts and AI clients

Current limits

MP4, MOV and WebM encoded with H.264, HEVC or VP9. Up to 1080p, 30 fps and 5 minutes, subject to your account’s shorter limit. Trial accounts support up to 30 seconds. Paid access uses your existing entitlement, capped at 5 minutes. One active task per account, shared with the website.

Direct upload: 500 MiB. HTTPS import: 200 MiB. Files are checked on the server before processing. Transparent VP9 WebM output preserves source audio when present.

REST API

Create an API key in settings. Send it as Authorization: Bearer YOUR_API_KEY. The base URL is https://videobgremover.net/api/v1.

For uploads, import, completion and task creation, send a stable Idempotency-Key of 8–128 letters, digits, dots, underscores, colons or hyphens. Reuse it with identical fields after a timeout. Different fields with the same key return 409.

Import first, poll the upload until ready, then submit a job with its upload_id and your approved max_credits.

curl https://videobgremover.net/api/v1/uploads/import \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: import-example-001' \
  -d '{"url":"https://example.com/video.mp4","name":"video.mp4"}'

# After GET /uploads/UPLOAD_ID reports ready:
curl https://videobgremover.net/api/v1/jobs \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: removal-example-001' \
  -d '{"upload_id":"UPLOAD_ID","max_credits":30}'

A direct upload request uses {"name":"video.mp4","content_type":"video/mp4","size_bytes":123456}. PUT bytes to the signed URL, without your API key. For multipart uploads, obtain each part URL and complete with {"parts":[{"part_number":1,"etag":"ETAG"}]}. Single uploads complete with {}.

Remote MCP

Add a remote HTTP MCP server in your client using https://videobgremover.net/api/mcp. Sign in with Google on VideoBGRemover and review the requested permissions and connection credit budget. MCP uses OAuth; no separate API key is required.

Clients with file and HTTP tools can use the signed upload plan. Otherwise, provide a public HTTPS video URL for import. Availability of write tools depends on your client and plan. A local path or a chat attachment alone is not a downloadable video URL.

Tools: get_account, create_upload, get_upload_part, complete_upload, import_video, get_upload, delete_upload, remove_video_background, get_job, cancel_job and get_download. Mutating create/complete tools require a stable request_id. Background removal also requires max_credits.

Credits, progress and recovery

API, MCP and the website share your balance. Video background removal costs one credit per second, rounded up. Each key or connection starts with a 1,000 credit spending ceiling; change it in settings. A budget is not a credit grant.

Import, completion and job submission return 202. Poll at the returned interval, starting at five seconds. Task states are queued, running, succeeded, failed and canceled. Queue capacity can delay a queued task; your task remains saved. Processing is asynchronous and does not require an open chat.

Repeated requests and status polling do not add processing charges. Failed tasks release reserved credits according to the account ledger. If a submission needs checking, wait for recovery before creating another paid task.

Read limit: 60 requests/minute. Write limit: 5 requests/minute, shared across an account’s keys and connections. A 429 response includes Retry-After. Download URLs expire after ten minutes; request another while the result is available.