Video
Preview / access
Image, video, and audio generation as developer APIs
Media API is not a workflow builder or editor. BatchIn owns model supply, task status, failure reasons, cost estimates, fallback, usage, and receipts.
Image
Per-model state
Audio
Per-model state
Receipts
Request-level
Media interfaces developers actually need
Customers own editing, templates, and workflows; BatchIn owns model calls and production control.
- Image, video, and audio generation share auth, billing, and error shape.
- Async jobs must expose task status, failure reason, and cost estimate.
- Chinese closed-source video model supply is the differentiator, but only real access states are shown.
Shared ledgers with Model API
Media API is not a separate billing system; media requests also flow into usage, billing, traces, and VaaS Ledger.
- Supports fallback and normalized provider errors.
- Per-second, per-image, and token costs must remain attributable in the ledger.
- Video exposes the /v1/videos compatibility entry.