Stop hand-wiring video generation. Feed your coding agent the canonical prompt, let it build the integration, and go live on a cleaner US-based Seedance 2.0 API with real billing, support, and enterprise paths behind it.
Canonical prompts for Cursor, Claude Code, Codex, Windsurf, and similar agents. Guaranteed concurrency, invoice billing, and onboarding support when you need to scale beyond self-serve.
Product teams, agencies, ecommerce operators, and app builders do not need another docs maze. They need an API their agent can wire correctly on the first pass.
"We integrated US Video API in days and now offer video generation to our 5,000+ merchants."
TOM Jin, CTO, KwickPOS
The GitHub side is where technical evaluators, agencies, and AI coding agents can inspect the real integration surface. It ties together SDKs, OpenAPI, polling examples, prompt packs, releases, and enterprise-facing docs.
Do not tell users to manually wire requests, polling, and error handling. Tell them to paste one prompt into their coding agent and let it generate the integration against the real API contract.
Give Cursor, Claude Code, Codex, Windsurf, or your own agent a canonical prompt so it stops inventing fields and starts writing shippable code.
Skip manual polling loops, upload handling, and status plumbing. Let the agent scaffold the integration while your team stays on product and growth.
The prompt pack keeps the agent inside the real API surface, current account model, and safety/error constraints instead of hallucinating fantasy features.
This path is for teams that already know the video use case is real and do not want to gamble on support, billing, or concurrency after launch.
Grab an API key, hand one prompt to your coding agent, and get a working integration live without waiting on sales or procurement.
Recent generation samples rendered through the same API. Use self-serve to test quality. Use enterprise access when output volume and throughput matter.
Use one REST interface for text-to-video and image-to-video. Start self-serve. Upgrade to enterprise when you need bigger limits, better terms, or direct support.
import requests response = requests.post( "https://usvideoapi.com/v1/videos", headers={"Authorization": f"Bearer {API_KEY}"}, json={ "prompt": "Restaurant promo reel with plated dishes and warm lighting", "resolution": "720p", "duration": 5, "aspect_ratio": "16:9" } ) job = response.json() # {"id":"job_8f3a...","status":"pending","price":"$1.25"}
This is the concrete operating surface buyers and developers usually look for first: request shape, duration bounds, polling model, input limits, and standard account defaults.
Standard requests accept short-form clips from 4 to 15 seconds. Good fit for ads, hero shots, Shorts, product loops, and landing page demos.
Self-serve request shape supports 480p, 720p, and 1080p, with aspect ratios for 16:9, 9:16, 1:1, and 4:3 workflows.
Submit work to /v1/videos, receive a job ID immediately, then poll status until the asset completes or fails.
Published default rate limits are 60 requests per minute and 10 concurrent jobs for standard accounts, with custom enterprise limits available.
Image-to-video accepts base64 image input. The documented safe target is a JPEG source image at or below 1 MB to avoid 413 payload issues.
Docs, status page, account guide, enterprise guide, and support email are all live. Enterprise buyers also get a direct path for onboarding and billing.
The API needs more than pretty demos. It needs billing clarity, rate limits that make sense, and support paths that match the customer type.
Generate short-form video from prompts with standard controls for duration, resolution, and aspect ratio.
Animate a first frame or product image without changing the rest of your pipeline.
Self-serve keys for individual builders, with tighter operational options for larger teams.
Submit work, receive a job ID, and poll or orchestrate completion from your own backend.
Prepaid self-serve for freelancers. Invoice and negotiated terms for qualified production accounts.
Direct support for real production use cases, not just a generic signup page and wishful thinking.
Self-serve remains available, but enterprise buyers should not have to reverse-engineer whether the platform can support them.
Best for freelancers, creators, indie developers, and teams validating a workflow. Prepaid credits, no contract, and a $5 minimum top-up.
Best for teams that already know they need higher concurrency, invoice billing, onboarding, or support around a real launch.
Those are different buyer expectations. The site and product should acknowledge that instead of pretending every visitor wants the same flow.
The YouTube channel is where we publish the same kind of promo and workflow videos we use across landing pages and sales conversations. It is proof that the API is not just documented, it is used in production to ship content.
Enterprise buyers should talk to us. Freelancers and indie developers should be able to start today without friction.