Head to head · Video generation · October 2026 research run
Luma AI API vs PixVerse API
Luma AI API scores 51.7 (D) on agent readiness against PixVerse API's 42.3 (E), and leads in 5 of 7 scored categories. PixVerse API leads on schema & documentation. 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
- Security & auth, 53 against 28
- Payments & pricing, 30 against 15
- Maintenance & community, 47 against 42
- Transparency & trust, 67 against 46
Watch for
Video rates are marked as subject to change before general availability
Best for Agents doing many short edits (restyle, swap, lip sync, sound effects) on a budget.
Ahead on
- Schema & documentation, 58 against 53
Also in its favour
- Runs on your own machine
Watch for
Plan prices and the dollar value of a credit sit on a JavaScript-only billing page
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.
PixVerse API 28
Model reading of the checklist (credential, training, retention, operator visibility, programme). One API key in an API-KEY header (20). The platform terms (still dated 4 September 2026 on 5 November) don't say whether inputs or outputs train models (0). No retention period or deletion call found (0). A usage deduction query API since 18 August 2026 shows what each job cost, no audit log (8). No security.txt, bug bounty or certification found (0). The docs and security.txt per the 30 September check, not re-read on 10 November. 20 + 0 + 0 + 8 + 0 = 28.
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.
PixVerse API 35
No status page found (0). No incident history to read (5). Concurrent jobs per plan are published, 3 on Free, 15 on Essential, 20 on Scale and 25 on Business (15). Credits come back on failed or moderated jobs and after 2 hours without a result, and a stuck concurrency slot frees after 10 minutes, but we found no 429 or backoff guidance (5). No SLA (0). V6 and C1 are current models with no preview label (10). Per the 30 September and 1 October checks, not re-read on 10 November (PixVerse's Terms of Service bar robots and page-scrapes on its websites). 0 + 5 + 15 + 5 + 0 + 10 = 35.
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.
PixVerse API 46
Closed models under platform terms (updated 4 September 2026, re-read on 5 November) with MOTIVAI PRIVATE LIMITED, with AIVORA PTE. LTD. named as an affiliate and as the operator in the general Terms of Service (29 October 2026). The platform terms give API users the rights in generated video and allow commercial use (15). The terms don't address training on inputs or outputs and give no retention period, only that data may be deleted when service ends. We didn't read the privacy policy against them (5). No deprecation policy, but legacy models are labelled, per the 1 October check (5). No subprocessor list or data locations found (0). 15 + 5 + 5 + 0 = 25.
Payments & pricing Luma AI API +15
Luma AI API 30
No x402, MPP or L402 (0). Per-clip prices in dollars are published without a login, $0.30 for a 5 second 720p clip (20). No free tier, pay as you go from the first call (0). A person signs up in the platform and creates the key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
PixVerse API 15
No x402, MPP or L402 (0). Credits per second are public for every model, and the docs peg $1 at five 5 second V6 720p clips, but plan prices sit on a billing page that needs JavaScript, so the dollar price of a credit isn't stated outright (10). A Free API plan with 3 concurrent jobs is listed, but the docs don't say whether it includes credits (0). A person signs up on the platform (0). Per the 30 September and 1 October checks, not re-read on 10 November (PixVerse's Terms of Service bar robots and page-scrapes on its websites). 0 + 10 + 0 + 0 = 10. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.
Schema & documentation PixVerse 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.
PixVerse API 58
No OpenAPI file published (0). llms.txt on the platform docs (10). Each endpoint page says what the operation does, and the model tables say which models support it. Older model tables still sit beside current ones (12). Typed parameters with fixed values for model, quality, duration and aspect ratio (11). Examples on each endpoint. Results use numeric status codes (1 done, 5 generating, 7 moderation failure, 8 failed) that an agent has to look up (10). A dated changelog that adds models and endpoints every few weeks (15). Per the 30 September and 1 October checks, not re-read on 10 November (PixVerse's Terms of Service bar robots and page-scrapes on its websites). 0 + 10 + 12 + 11 + 10 + 15 = 58.
Maintenance & community Luma AI API +5
Luma AI API 47
Model reading. The latest dated API change found is SDK v0.5.0, whose changelog dates it 4 August 2026 (tag 5 August), adding the layering parameter to generations. That is more than 90 days before 4 November, so 10 (within 180 days). The docs now carry deletion, files and usage guides with no dates, and the 3 November MCP connector runs Luma Agents workflows on a subscription, which the API doesn't serve, so neither counts (10). Ray 2, Ray 3 and their variants are retiring, but the cutoff dates go out in private notices and the migration guide gives none (5). No API changelog. The SDK changelogs are dated and support is an email address on the migration guide (7). Official SDKs for Python, TypeScript and Go and a CLI, last released on 5 August with Ray 3.2 and files support, though the new deletion routes aren't in them yet (15). Each SDK repository has a CI workflow (10). 10+5+7+15+10 = 47.
PixVerse API 42
Model reading. The changelog's latest entry is the One-click VibeMV API on 24 September 2026, per the 1 October check, not re-read on 10 November (PixVerse's Terms of Service bar robots on its websites). That is 47 days before 10 November 2026, within 90 (20, was 30, cause time). PixVerse's official CLI released v1.4.6 to v1.4.16 from 24 September to 29 October 2026, but it runs on the web app's subscription credits and app models, not the Platform API, so it doesn't count. Legacy models from V3.5 to V5.6 stay callable, and no removals were found (10). Dated changelog and support through the platform (12). No official SDK. The stdio MCP package's last version is 0.2.2, committed on 21 October 2025, with a v2.0.0 README commit on 22 October 2025 and nothing since (0). Nothing current to assess for package health (0). 20 + 10 + 12 + 0 + 0 = 42.
Score by category
| Category | Weight | Luma AI API | PixVerse API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 57 | 35 | Luma AI API +22 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 53 | 58 | PixVerse API +5 |
| Agent ergonomics | 13% | 66 | 70 | PixVerse API +4 |
| Security & auth | 14% | 53 | 28 | Luma AI API +25 |
| Payments & pricing | 10% | 30 | 15 | Luma AI API +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 47 | 42 | Luma AI API +5 |
| Transparency & trust | 7% | 67 | 46 | Luma AI API +21 |
| Negative events | ≤15 | -2 | 0 | |
| Total | D 51.7/100 | E 42.3/100 |
Facts side by side
| Fact | Luma AI API | PixVerse API |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Luma AI | PixVerse |
| Hosted endpoint | https://agents.lumalabs.ai/v1 | https://app-api.pixverse.ai/openapi/v2 |
| Transports | HTTP | 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 | yes |
| Last release | 2026-08-05 | 2026-09-24 |
| Terms last updated | 2026-05-14 | 2026-09-04 |
| Privacy policy last updated | 2026-04-20 | 2026-05-07 |
| Customer content may train models | yes | yes, with an opt-out |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 2 stars, 982 npm/wk | none |
| 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 | PixVerse API |
|---|---|---|
| GullBrowser and end-to-end tester | 3/5 Limits in the dashboard, retirements by email | 3/5 A UUID on every request, a lookup table for every status |
| LedgerCost analyst | 3/5 Ten seconds costs three times five | 3/5 Cheap per second, but the credit price is inferred |
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 | PixVerse API |
|---|---|---|
| Make a 30-second video clip30 seconds of generated video | $0.90 to $14.40 | $1.20 |
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.
PixVerse API
V6 at about $0.04 a second at 720p, with audio and clips up to 15 seconds. Plan prices and the dollar value of a credit sit on a JavaScript-only billing page.
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
PixVerse API
- Generate a new UUID for Ai-trace-id on every new submit. Reuse it only to fetch the same job again
- Poll the result endpoint. Status 1 is done, 5 generating, 7 moderation failure, 8 failed
- Moderate prompts before calling. Repeated status 7 results can suspend the key
- Use model v6 or c1 for new work. Older model tables still sit in the docs
Questions
Which is better for AI agents, Luma AI API or PixVerse API?
Luma AI API scores 51.7 (D) on agent readiness against PixVerse API's 42.3 (E), and leads in 5 of 7 scored categories. PixVerse API leads on schema & documentation.
Do Luma AI API and PixVerse API need an API key?
Both need an API key.
Can an agent call Luma AI API and PixVerse API without installing anything?
Yes. Luma AI API has a hosted endpoint at https://agents.lumalabs.ai/v1 and PixVerse API at https://app-api.pixverse.ai/openapi/v2.
Other comparisons with Luma AI API or PixVerse API
- Alibaba Wan (Model Studio) vs Luma AI API
- Alibaba Wan (Model Studio) vs PixVerse API
- fal video models vs Luma AI API
- fal video models vs PixVerse API
- framefields vs Luma AI API
- framefields vs PixVerse API
- Gemini Omni 1.2 Flash vs Luma AI API
- Gemini Omni 1.2 Flash vs PixVerse API
- Google Veo vs Luma AI API
- Google Veo vs PixVerse API
- Higgsfield API vs Luma AI API
- Higgsfield API vs PixVerse API
- HyperFrames vs Luma AI API
- HyperFrames vs PixVerse API
- Kling AI API vs Luma AI API
- Kling AI API vs PixVerse 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 Popcraft MCP
- Luma AI API vs Replicate video models
- Luma AI API vs Runway API
- Luma AI API vs Seedance on BytePlus ModelArk
- Luma AI API vs Vidu API
- Magic Hour MCP vs PixVerse API
- MiniMax Video API vs PixVerse API
- OpenAI Sora API vs PixVerse API
- Pika API vs PixVerse API
- PixVerse API vs Popcraft MCP
- PixVerse API vs Replicate video models
- PixVerse API vs Runway API
- PixVerse API vs Seedance on BytePlus ModelArk
- PixVerse API vs Vidu API
- Clueso vs Luma AI API
- Clueso vs PixVerse API
- Luma AI API vs sync. labs MCP server
- PixVerse API vs sync. labs MCP server
Machine-readable
- This page as Markdown
/compare/luma-vs-pixverse.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/luma.json·/api/v1/tools/pixverse.json - From a terminal
anchor compare luma pixverse(the CLI) - Over MCP
compare_tools {"a": "luma", "b": "pixverse"}at/mcp, no key