Beat API
Solves a real integration problem: music video generation normally means stitching a storyboard model, a video model and a compositor yourself, and this collapses that into one async task with a ledger behind it. Editable storyboards mean one ruined shot does not cost a full re-render. What is missing is a rate card - you learn what a job costs after it runs.
Pros
- A single task endpoint covers storyboarding, rendering, composition and hosted MP4 delivery
- Storyboards are editable, so individual shots can be swapped or re-rendered
- One key spans workflow, video, image, effect and realtime WebRTC APIs
- Charges are reserved on acceptance and refunded on eligible failures, with a usage ledger to audit
Cons
- No published per-second or per-video rate - pricing is only knowable from the ledger after a run
- No company name, registered entity or country appears anywhere in the docs
- The marketing site returns 403 to ordinary fetchers, so independent verification is awkward
- Audio is capped at 180 seconds on standard and 300 on premium