BeatAPI

@BeatAPI list all available video generation models and show me which ones support text-to-video

Found 4 video generation models currently available: 1. **runway-gen3** – Text-to-video and image-to-video. Max 10s duration, 1280×768 resolution. Best for realistic motion and camera movement. 2. **kling-v1** – Text-to-video only. Max 5s, 720p. Faster turnaround, lower cost per task. 3. **luma-dream** – Text-to-video with style presets. Max 5s, 1024×1024. Optimized for abstract and artistic content. 4. **minimax-v1** – Text-to-video. Max 6s, 1280×720. Supports Chinese prompts natively. All models bill per second of generated video. Check your account balance with Get Usage before queuing tasks.

This example demonstrates the read-heavy discovery workflow — users explore model capabilities before committing to paid generation. BeatAPI charges per task, so knowing model constraints (duration, resolution, input types) up front prevents wasted spend. The MCP requires an API key with read access to the models catalog.

@BeatAPI create a 5-second product video for our new wireless earbuds using the uploaded image earbud-hero.jpg, then poll until it's ready

Started ecommerce video task **task_8x3k9m** using your uploaded image. Current status: **processing** (stage: storyboard generation). Polling every 8 seconds… [12s later] Status: **processing** (stage: rendering frame 45/120). [28s later] Status: **succeeded**. Video ready at `https://cdn.beatapi.com/out/task_8x3k9m.mp4` (5.2s, 1920×1080). Charged $0.47 USD. Remaining balance: $23.18. The video shows the earbuds rotating with a subtle glow effect and ends with your logo fade-in. Download expires in 7 days.

This write-and-poll example shows the full lifecycle of a paid async task: creation, polling, and retrieval. BeatAPI tasks can take 20–90 seconds depending on queue depth. The MCP handles polling intervals automatically but does NOT retry failed tasks — if rendering fails mid-job, you'll see the failure reason and must manually resubmit. Requires API key with task:create and storage:read scopes.

@BeatAPI check my account usage for this month and tell me if I have enough balance to generate three more 10-second videos

**Account Usage Summary (December 2024)** - **Current balance:** $18.32 USD - **Tasks this month:** 47 (42 succeeded, 3 failed, 2 canceled) - **Total spend:** $31.68 - **Concurrent task limit:** 3 **Cost estimate for 3×10s videos:** Assuming runway-gen3 at ~$0.95/10s, you'd need **$2.85**. ✅ You have sufficient balance. **Note:** If all 3 tasks run concurrently, you'll hit your account's concurrency cap. Queue them sequentially or request a limit increase from BeatAPI support.

This synthesis example pairs the MCP's usage data with the AI's cost reasoning — users get a go/no-go decision before expensive work. BeatAPI does not auto-recharge; if balance runs out mid-task, the task fails and partial work is billed. The concurrency warning is critical for teams running batch jobs. Requires API key with account:read scope.

When BeatAPI wins for small-team product drops

A 3-person DTC brand launching a new product line needs 20 product videos for social ads in 48 hours. BeatAPI's ecommerce video tool takes uploaded product shots and generates ad-ready clips without a videographer or editor. The team uploads images, polls task status, and downloads finished videos—all from Switchy's shared workspace so the founder, designer, and media buyer see progress in real time. The trade-off: BeatAPI is a paid service billed per task, so budget-conscious teams should batch requests and check usage totals with the Get Usage tool before scaling. If your launch calendar has predictable creative bursts and you lack in-house video talent, BeatAPI keeps your pipeline moving without hiring freelancers.

When BeatAPI fits iterative creative testing

A 5-person growth team running paid social campaigns tests 10 video concepts weekly to find winning creatives. BeatAPI's video generation and effects tools let the team spin up variants fast—different styles, transitions, or AI-generated backgrounds—without round-tripping to a design agency. The media buyer creates tasks in Switchy, the copywriter reviews storyboards as they populate, and the analyst tracks which outputs drive conversions. The boundary: if your team already has a motion designer on payroll or runs fewer than 5 creative tests per month, BeatAPI's per-task cost may exceed the value of speed. But for teams in high-velocity testing mode with no dedicated video resource, BeatAPI turns creative hypotheses into testable assets in hours, not days.

When BeatAPI's video analysis supports feedback loops

A 6-person SaaS support team collects video testimonials from customers but struggles to extract themes or highlight reels at scale. BeatAPI's video analysis tool processes uploaded testimonials and surfaces metadata—sentiment, key moments, or visual patterns—that the team uses to prioritize which clips to feature in marketing or product roadmaps. The head of support uploads videos to Switchy, runs analysis tasks, and shares results with product and marketing in the same workspace. The catch: BeatAPI requires videos already uploaded to your account, so teams without a video library or consistent testimonial flow won't see immediate ROI. If you're collecting 10+ customer videos monthly and need structured insights without manual review, BeatAPI turns raw footage into actionable intelligence for cross-functional teams.