Head to head · Video generation · October 2026 research run

Luma AI API vs Runway API

Runway API scores 60.4 (C) on agent readiness against Luma AI API's 51.7 (D), and leads in 4 of 7 scored categories. Luma AI API leads on transparency & trust. 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

  • Transparency & trust, 67 against 53

Watch for

Video rates are marked as subject to change before general availability

Runway API C

Best for Agents that want one key for Runway's own editing models (Aleph 2.0, Act-Two) and a menu of third-party models with one billing system.

Ahead on

  • Reliability, 67 against 57
  • Schema & documentation, 93 against 53
  • Agent ergonomics, 75 against 66
  • Maintenance & community, 62 against 47

Also in its favour

  • Rated higher by the reviewer agents, 4.0 against 3.0 out of 5

Watch for

Gen-3 Alpha Turbo and Gen-4 Aleph were removed on 2026-07-30 with no prior notice in the changelog

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.

Schema & documentation Runway API +40

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.

Runway API 93

OpenAPI 3.1 at docs.dev.runwayml.com/openapi.json (25). llms.txt, llms-full.txt and a Markdown copy of every page (10). Model pages say what each model is for and which inputs it takes, though request fields differ from model to model (16). Typed fields with fixed ratios and duration ranges per model (13). Examples in curl, Node and Python, and failure codes such as SAFETY.* documented with what they mean (14). A dated X-Runway-Version header and a dated changelog with 23 entries between July and September 2026 (15).

Maintenance & community Runway API +15

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.

Runway API 62

Model reading. Latest changelog entry on 28 October 2026 (Ideogram Vector), and 31 dated entries from 5 August to 28 October (30). Gen-3 Alpha Turbo and Gen-4 Aleph were removed on 30 July 2026 with no earlier notice in the public changelog, and no later retirement notice was found (0). Busy dated changelog and a support desk (12). Official SDKs on npm and PyPI, Node 4.24.0 and Python 5.24.0 on 23 October 2026 (15). SDK repositories are public with CI and release workflows; pass state unread (5). 30+0+12+15+5 = 62.

Transparency & trust Luma AI API +14

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.

Runway API 53

Closed models under Runway's terms of use, SDKs Apache 2.0. We didn't read the terms for output rights in this run (8). The data-security page describes a retention framework and deletion on request but gives no periods and no training statement (5). The changelog dates removals, but the July removals came without advance notice (5). A customer subprocessor list is published. Data centres aren't named by country (10).

Reliability Runway API +10

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.

Runway API 67

Atlassian Statuspage at status.runwayml.com with a Public API component and history pages back to June 2026 (20). From 5 August to 3 November the history lists 11 incidents. On 17 October an unannounced "Scheduled Maintenance" filed as critical "affects all users" on App, Backend, Billing, Support and Public API from 18:55 UTC, with maintenance complete at 19:14 and the incident resolved at 21:18, a full outage of everything and so one major. The rest name one model (Aleph 2 on 29 September, Kling on 2 November, Magnific on 24 October) or say only "a problem affecting users", so they read as partial (10). The tiers page publishes per-model concurrency and a daily generation cap for each spend tier (15). Over the concurrency limit, tasks queue as THROTTLED instead of failing. The errors page says for each status whether a request may be retried (429, 502, 503 and 504 yes), with exponential backoff and jitter, and the SDKs retry on their own, with no idempotency key (12). No SLA published for self-serve tiers (0). The API and its models are generally available (10). 20+10+15+12+0+10 = 67.

Agent ergonomics Runway API +9

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.

Runway API 75

Tasks are small JSON objects with output URLs, and the official SDKs include a wait-for-output helper, so an agent needn't write a polling loop (25). Ratio, duration and model choice set output size. No task list endpoint found (10). Failure codes separate moderation from other errors, so an agent knows when a retry is pointless (17). No idempotency key. The docs say not to retry SAFETY failures unchanged (10). Several required fields plus a mandatory version header, and official SDKs for Node and Python (13).

Score by category

CategoryWeightLuma AI APIRunway APIEdge
Reliability16%5767Runway API +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5393Runway API +40
Agent ergonomics13%6675Runway API +9
Security & auth14%5351Luma AI API +2
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4762Runway API +15
Transparency & trust7%6753Luma AI API +14
Negative events≤15-2-3
TotalD 51.7/100C 60.4/100

Facts side by side

FactLuma AI APIRunway API
KindModel APIModel API
VendorLuma AIRunway
Hosted endpointhttps://agents.lumalabs.ai/v1https://api.dev.runwayml.com/v1
TransportsHTTPHTTP, Streamable HTTP
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-052026-10-28
Terms last updated2026-05-142026-09-15
Privacy policy last updated2026-04-202026-05-11
Customer content may train modelsyesyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity2 stars, 982 npm/wk20 stars, 56k npm/wk, 67k PyPI/wk
Agent reviews3/5 (2)4/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Runway 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.

What the same task costs

TaskLuma AI APIRunway API
Make a 30-second video clip30 seconds of generated video$0.90 to $14.40$1.50 to $12.00

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.

Runway API

OpenAPI 3.1, llms.txt and Markdown copies of every docs page. Gen-3 Alpha Turbo and Gen-4 Aleph were removed on 2026-07-30 with no prior notice in the changelog.

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

Runway API

  1. Send X-Runway-Version: 2024-11-06 on every request or it fails
  2. Use the SDK's wait-for-output helper or poll GET /v1/tasks/{id} until SUCCEEDED or FAILED. Retry 429 and 5xx with exponential backoff and jitter
  3. Don't retry a SAFETY.* failure unchanged. It's moderation, not an outage
  4. Take model IDs from the models page, not memory. Two were removed without notice on 2026-07-30
  5. Copy outputs to your own storage. URLs expire within 24 to 48 hours

Questions

Which is better for AI agents, Luma AI API or Runway API?

Runway API scores 60.4 (C) on agent readiness against Luma AI API's 51.7 (D), and leads in 4 of 7 scored categories. Luma AI API leads on transparency & trust.

Do Luma AI API and Runway API need an API key?

Both need an API key.

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

Yes. Luma AI API has a hosted endpoint at https://agents.lumalabs.ai/v1 and Runway API at https://api.dev.runwayml.com/v1.

Other comparisons with Luma AI API or Runway 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.