Head to head · Video generation · October 2026 research run
Luma AI API vs Vidu API
Luma AI API scores 51.7 (D) on agent readiness against Vidu API's 40.5 (E), and leads in 5 of 7 scored categories. Both do video generation.
Best video generation for AI agents · All 203 video comparisons
Which one, for what
Best for Pipelines that want one model for generate, edit, extend and reframe, and colourists who want HDR and EXR.
Ahead on
- Reliability, 57 against 35
- Schema & documentation, 53 against 48
- Agent ergonomics, 66 against 55
- Security & auth, 53 against 28
- Transparency & trust, 67 against 46
Watch for
Video rates are marked as subject to change before general availability
Vidu API E
Best for Batch jobs that can wait for off-peak prices and want reference-to-video or start-end frames with sound.
Also in its favour
- Runs on your own machine
Watch for
No llms.txt, OpenAPI file or error-code reference
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Security & auth Luma AI API +25
Luma AI API 53
Model reading of the checklist (credential, training, retention, operator visibility, programme). Bearer keys created in the platform and shown once, with quota and limits shared by all keys of a client. No scopes found (20). The API terms of 28 April 2026 say Luma won't use API inputs or outputs to train or develop its models (20). A deletion call is now documented, DELETE /v1/generations/{id} with a deletion task polled at GET /v1/deletions/{task_id}, though the guide says it may not be enabled for every API client and the SDKs don't include it yet (5). Retention is set per API client, with no default period stated, and a generation that fails moderation can be held for at least a year (0). Rate-limit headers, a request id per call, and GET /v1/usage for spend by session or end user, with no audit log found (8). No security.txt (lumalabs.ai/.well-known/security.txt returns 404), bug bounty or certification found for Luma AI (0). 20+20+5+0+8+0 = 53.
Vidu API 28
Model reading of the checklist (credential, training, retention, operator visibility, programme). One API key sent as Authorization: Token, no scopes found (20). The terms (effective 23 January 2025) let ShengShu examine, record, copy and use inputs and outputs for operational and other purposes, and don't rule out training (0). No retention period or deletion call found (0). Task list for per-task visibility, no audit log (8). No security.txt, bug bounty or certification found (0). Per the 1 October check, not re-read on 10 November (platform.vidu.com answered robots.txt with a redirect to its home page, so the host is left unread).
Reliability Luma AI API +22
Luma AI API 57
Better Stack status page at status.lumalabs.ai with API, Dream Machine and Luma Agents components, an incident list and an RSS feed (20). In the 90 days from 6 August the feed lists three incidents, all on legacy Ray2 models: Ray2 Flash timeouts on 2 to 3 September (about 9 hours) and 15 to 16 September (about 2 hours), and Ray2 queue times on 16 to 17 September (about 13 hours). The status page tags each with its API and Dream Machine components, and each hit one legacy model, so minor only (20). The authentication incident counted as a major on 1 October was on 16 July and has left the window. Limits are per minute and per concurrent job, but the numbers sit in the dashboard, not the docs (5). Every 429 carries Retry-After, with separate bodies for the per-minute and concurrency limits and backoff guidance with jitter. Rejected requests aren't queued and synchronous errors are never charged, which is safe-retry guidance, but there is no idempotency key, so 12 as settled in this run (12). No SLA document. The pricing page lists a latency SLA for Provisioned Throughput only as a table entry (0). The pricing page says video rates may change before general availability, so the video surface isn't GA yet (0). 20+20+5+12+0+0 = 57.
Vidu API 35
No status page found (0). No incident history to read (5). Standard accounts run 5 tasks at once and extra tasks queue in order, per the usage page (15). Queueing absorbs bursts, but we found no 429, retry or billing-on-failure guidance (5). No SLA (0). Q3 Pro and Q3 Turbo carry no preview label (10). Per the 1 October check, not re-read on 10 November (platform.vidu.com answered robots.txt with a redirect to its home page, so the host is left unread).
Transparency & trust Luma AI API +21
Luma AI API 67
Closed models. The terms give customers the outputs, with commercial use tied to an active paid plan (15). The API terms state that API inputs and outputs aren't used for training (10). The pricing page's comparison table says Pay-as-you-go has no no-train guarantee and only Provisioned Throughput does. That contradiction is charged once, as a misleading claim under negative events, as rime-prism's training contradiction is, so it doesn't also lower this line. The privacy policy (20 April 2026) describes retention by criteria without periods, and the deletion guide sets retention per API client with a one-year hold for moderation failures (5). The privacy policy was read and names US hosting with Standard Contractual Clauses for transfers. No DPA was read (5). A public migration guide without dates, retirement dates by email only (5). A subprocessor list (last updated 4 October 2026) names about 50 providers with their purpose, and the privacy policy says the services are hosted in the United States (15). 15+10+5+5+5+15 = 55.
Vidu API 46
Closed models under terms with ShengShu AI HK Limited and Hong Kong law. The terms don't restrict commercial use and forbid removing the AI-generated label, but don't say who owns the output (12). The terms let ShengShu record and use inputs and outputs for operational and other purposes, with no retention periods, and we didn't read the privacy policy against them (5). No deprecation policy (0). No subprocessor list or data locations found (0). Per the 1 October check, not re-read on 10 November (platform.vidu.com answered robots.txt with a redirect to its home page, so the host is left unread).
Agent ergonomics Luma AI API +11
Luma AI API 66
Generations come back as small JSON objects with a presigned URL for the output (15). We found no callback for the Agents API, so jobs are polled (0 of 10). Resolution and duration set output size (10). The API reference lists create, get and delete for generations and a list call only for files, so there is no list of past generations (0 of 10). The 429 detail string tells an agent whether to wait for Retry-After or for a job to finish, and failures carry codes (16). No idempotency key. Moderated and failed generations are refunded and synchronous errors aren't charged, so a retry after a failure is safe (10). One generation endpoint with few required fields, and official SDKs for Python, TypeScript and Go plus a CLI (15). 15+0+10+0+16+10+15 = 66.
Vidu API 55
Small task responses and a callback_url that removes polling (25). Resolution, duration and off-peak mode set output and cost, and there are task list and cancel endpoints (20). Task states run created, queueing, processing, success or failed, but we found no error-code reference (5). No idempotency key or safe-retry guidance found (0). Only model and images are required on image-to-video and the rest have defaults. No official SDK, and the Token scheme differs from the usual Bearer (5). Per the 1 October check, not re-read on 10 November (platform.vidu.com answered robots.txt with a redirect to its home page, so the host is left unread).
Schema & documentation Luma AI API +5
Luma AI API 53
No public OpenAPI document is linked from the docs. The API reference at /api/ is generated per method with no visible spec download (0). docs.agents.lumalabs.ai/llms.txt returns 404, but every docs page links a Markdown twin (for example /index.md and /guides/pricing/index.md) (10). Guides cover generation, keyframes, edit, extend, reframe, deletion, files, usage and the migration, and say which options don't combine, such as start and end frames with 10 second clips (14). Typed fields for model, type, resolution and duration with fixed values (12). curl and SDK examples, both 429 bodies and generation failure codes are documented (12). Responses carry an X-API-Version header and the SDK repositories keep dated changelogs, but the API docs have no changelog and the public changelog page on lumalabs.ai was last updated in June 2025 (5). 0+10+14+12+12+5 = 53.
Vidu API 48
No OpenAPI file (0). No llms.txt or Markdown copies, though the HTML reference pages render without a browser (0). The image-to-video reference says what each model family is for (Q3 for synced audio and storyboards, Q2 for speed and quality, Q1 for clarity) (15). Typed parameters with model lists, per-model duration ranges (1 to 16 seconds on Q3), resolution options and defaults, though one model field carries nine values whose valid durations differ (13). We found no error-code reference, and examples rest on the listing's check (5). A dated update log, latest entry 15 September 2026 (15). Per the 1 October check, not re-read on 10 November (platform.vidu.com answered robots.txt with a redirect to its home page, so the host is left unread).
Score by category
| Category | Weight | Luma AI API | Vidu API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 57 | 35 | Luma AI API +22 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 53 | 48 | Luma AI API +5 |
| Agent ergonomics | 13% | 66 | 55 | Luma AI API +11 |
| Security & auth | 14% | 53 | 28 | Luma AI API +25 |
| Payments & pricing | 10% | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 47 | 47 | even |
| Transparency & trust | 7% | 67 | 46 | Luma AI API +21 |
| Negative events | ≤15 | -2 | 0 | |
| Total | D 51.7/100 | E 40.5/100 |
Facts side by side
| Fact | Luma AI API | Vidu API |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Luma AI | ShengShu Technology |
| Hosted endpoint | https://agents.lumalabs.ai/v1 | https://api.vidu.com/ent/v2 |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | none |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-08-05 | 2026-09-15 |
| Terms last updated | 2026-05-14 | couldn't be read |
| Privacy policy last updated | 2026-04-20 | couldn't be read |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 2 stars, 982 npm/wk | 5 stars |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Luma AI API | Vidu API |
|---|---|---|
| GullBrowser and end-to-end tester | 3/5 Limits in the dashboard, retirements by email | 3/5 Token, not Bearer, then wait for off-peak |
| LedgerCost analyst | 3/5 Ten seconds costs three times five | 3/5 Off-peak halves the bill if the job can wait |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
What the same task costs
| Task | Luma AI API | Vidu API |
|---|---|---|
| Make a 30-second video clip30 seconds of generated video | $0.90 to $14.40 | $1.05 to $3.60 |
Estimated from each listing's published prices, the same tasks as on the price index. Plans, minimums and free allowances aren't counted.
How the scores have moved
Verdicts
Luma AI API
Clip prices are published per generation in credits at a $0.003 list rate, and 429s say which limit was hit. The API terms rule out training on API data, while the pricing table lists that guarantee only for Provisioned Throughput. Video rates may change before general availability, and retirement dates for older Ray models go out by private email.
Vidu API
Q3 Turbo from $0.035 a second at 540p, about half that off-peak. No llms.txt, OpenAPI file or error-code reference.
Before you call either
Luma AI API
- Send model
ray-3.2and typevideo, with resolution and duration insidevideo. Older model names are rejected - Poll GET /v1/generations/{id} until completed or failed, then copy the presigned URL
- On 429, read
detail. Rate limit exceeded means wait Retry-After, Too many concurrent jobs means wait for a job to finish - Use keyframes with
keyframe_indexesfor 10 second clips. start_frame and end_frame only work at 5 seconds - Convert credits to dollars with
overage_ratefrom GET /v1/usage when it is set, otherwise the $0.003 list rate
Vidu API
- Send
Authorization: Token $VIDU_API_KEY. The scheme is Token, not Bearer - POST the task, then poll the Get Creation endpoint by task id or set
callback_url - Set
off_peakonly for jobs that can wait up to 48 hours. It roughly halves the credit rate - Set
audioto true for dialogue and sound on Q3. It's off by default - Keep the AI-generated label on outputs. The terms forbid removing it
Questions
Which is better for AI agents, Luma AI API or Vidu API?
Luma AI API scores 51.7 (D) on agent readiness against Vidu API's 40.5 (E), and leads in 5 of 7 scored categories.
Do Luma AI API and Vidu API need an API key?
Both need an API key.
Can an agent call Luma AI API and Vidu API without installing anything?
Yes. Luma AI API has a hosted endpoint at https://agents.lumalabs.ai/v1 and Vidu API at https://api.vidu.com/ent/v2.
Other comparisons with Luma AI API or Vidu API
- Alibaba Wan (Model Studio) vs Luma AI API
- Alibaba Wan (Model Studio) vs Vidu API
- fal video models vs Luma AI API
- fal video models vs Vidu API
- framefields vs Luma AI API
- framefields vs Vidu API
- Gemini Omni 1.2 Flash vs Luma AI API
- Gemini Omni 1.2 Flash vs Vidu API
- Google Veo vs Luma AI API
- Google Veo vs Vidu API
- Higgsfield API vs Luma AI API
- Higgsfield API vs Vidu API
- HyperFrames vs Luma AI API
- HyperFrames vs Vidu API
- Kling AI API vs Luma AI API
- Kling AI API vs Vidu API
- Luma AI API vs Magic Hour MCP
- Luma AI API vs MiniMax Video API
- Luma AI API vs OpenAI Sora API
- Luma AI API vs Pika API
- Luma AI API vs PixVerse API
- Luma AI API vs Popcraft MCP
- Luma AI API vs Replicate video models
- Luma AI API vs Runway API
- Luma AI API vs Seedance on BytePlus ModelArk
- Magic Hour MCP vs Vidu API
- MiniMax Video API vs Vidu API
- OpenAI Sora API vs Vidu API
- Pika API vs Vidu API
- PixVerse API vs Vidu API
- Popcraft MCP vs Vidu API
- Replicate video models vs Vidu API
- Runway API vs Vidu API
- Seedance on BytePlus ModelArk vs Vidu API
- Clueso vs Luma AI API
- Luma AI API vs sync. labs MCP server
- sync. labs MCP server vs Vidu API
Machine-readable
- This page as Markdown
/compare/luma-vs-vidu.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/luma.json·/api/v1/tools/vidu.json - From a terminal
anchor compare luma vidu(the CLI) - Over MCP
compare_tools {"a": "luma", "b": "vidu"}at/mcp, no key