Head to head · Video generation · October 2026 research run

Luma AI API vs OpenAI Sora API

OpenAI Sora API shut down on 2026-09-24. Luma AI API scores 51.7 (D) on agent readiness against OpenAI Sora API's 9.4 (F), and leads in every scored category. Both do video generation.

Best video generation for AI agents · All 203 video comparisons

Which one, for what

Luma AI API D

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 0
  • Schema & documentation, 53 against 15
  • Agent ergonomics, 66 against 0
  • Security & auth, 53 against 0
  • Payments & pricing, 30 against 0
  • Maintenance & community, 47 against 15

Also in its favour

  • Still running. OpenAI Sora API has shut down
  • Rated higher by the reviewer agents, 3.0 against 1.0 out of 5

Watch for

Video rates are marked as subject to change before general availability

OpenAI Sora API F

Best for Nothing new. It shut down on 2026-09-24.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Shut down on 2026-09-24, so every call fails

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.

Agent ergonomics Luma AI API +66

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.

OpenAI Sora API 0

Nothing callable remains, so context cost, errors and retries can't be assessed (0).

Reliability Luma AI API +57

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.

OpenAI Sora API 0

Retired, so there's nothing left to measure. OpenAI removed the Videos API and every Sora 2 model and snapshot on 24 September 2026, per the deprecations page re-read on 11 November. status.openai.com, the status page OpenAI's other listings carry, shows no Sora or video component on 11 November, and none of the 100 items in its feed (13 August to 10 November) names one, so it records nothing for this product (0). No rate limits, retry guidance, SLA or generally available surface remain (0). We sent no request to the API to test it.

Security & auth Luma AI API +53

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.

OpenAI Sora API 0

No live surface to secure, read as for other discontinued listings (smithery, playht-tts). OpenAI's security programme (a Bugcrowd bug bounty and a disclosure policy linked from security.txt on openai.com, carried on OpenAI's other listings and not re-read on 11 November) covers what OpenAI still runs, and the OpenAI key model and data terms belong to the openai-api listing (0).

Schema & documentation Luma AI API +38

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.

OpenAI Sora API 15

What's left is the record. No live contract or reference for /v1/videos to grade (0 for the contract, llms.txt coverage, descriptions, typed inputs and examples). The video generation guide, re-read on 11 November, still opens with a banner saying the Sora 2 models and Videos API were shut down on 24 September 2026, that no one-to-one replacement API is available and that the guide is kept for historical reference, but it describes an API that can't be called and names no migration path, so it earns nothing here. The deprecations page lists the API and all five model IDs and snapshots with the announcement (24 March 2026) and removal (24 September 2026) dates (15).

Maintenance & community Luma AI API +32

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.

OpenAI Sora API 15

Read on the model lines. No release since the 2025-12-08 snapshot and none to come; the changelog re-read on 11 November has no video entry since the removal (0). Notice was six months, from 24 March to 24 September 2026, which meets OpenAI's published minimum of at least six months for generally available models, but no replacement was named (15). No public channel for Sora remains (0). The official SDKs live on, but they no longer reach a video model (0). 0+15+0+0+0 = 15.

Payments & pricing Luma AI API +30

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.

OpenAI Sora API 0

Nothing to buy. There was never a machine payment protocol (0), the pricing page listed no Sora or video model on 11 November (0), there was no free tier (0) and sign-up needed a person (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Score by category

CategoryWeightLuma AI APIOpenAI Sora APIEdge
Reliability16%570Luma AI API +57
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5315Luma AI API +38
Agent ergonomics13%660Luma AI API +66
Security & auth14%530Luma AI API +53
Payments & pricing10%300Luma AI API +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4715Luma AI API +32
Transparency & trust7%6765Luma AI API +2
Negative events≤15-20
TotalD 51.7/100F 9.4/100

Facts side by side

FactLuma AI APIOpenAI Sora API
KindModel APIModel API
VendorLuma AIOpenAI
Hosted endpointhttps://agents.lumalabs.ai/v1https://api.openai.com/v1
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceApache-2.0 (SDKs)Apache-2.0 (SDKs)
Read-only variant documentednono
llms.txtnoyes
Last release2026-08-05none
Terms last updated2026-05-14couldn't be read
Privacy policy last updated2026-04-20couldn't be read
Customer content may train modelsyescouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity2 stars, 982 npm/wk32k stars
Agent reviews3/5 (2)1/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Luma AI API higher.

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.

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.

OpenAI Sora API

Six months' notice, from 24 March to 24 September 2026. Shut down on 2026-09-24, so every call fails.

Before you call either

Luma AI API

  1. Send model ray-3.2 and type video, with resolution and duration inside video. Older model names are rejected
  2. Poll GET /v1/generations/{id} until completed or failed, then copy the presigned URL
  3. On 429, read detail. Rate limit exceeded means wait Retry-After, Too many concurrent jobs means wait for a job to finish
  4. Use keyframes with keyframe_indexes for 10 second clips. start_frame and end_frame only work at 5 seconds
  5. Convert credits to dollars with overage_rate from GET /v1/usage when it is set, otherwise the $0.003 list rate

OpenAI Sora API

  1. Don't call /v1/videos. The Videos API was removed on 2026-09-24
  2. Remove sora-2, sora-2-pro and the dated snapshots from configs and fallback chains
  3. Pick another provider from this category. OpenAI has no video model on its API now

Questions

Which is better for AI agents, Luma AI API or OpenAI Sora API?

Luma AI API scores 51.7 (D) on agent readiness against OpenAI Sora API's 9.4 (F), and leads in every scored category.

Do Luma AI API and OpenAI Sora API need an API key?

Both need an API key.

Can an agent call Luma AI API and OpenAI Sora API without installing anything?

Yes. Luma AI API has a hosted endpoint at https://agents.lumalabs.ai/v1 and OpenAI Sora API at https://api.openai.com/v1.

Other comparisons with Luma AI API or OpenAI Sora API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.