Head to head · Video generation · October 2026 research run

Kling AI API vs Runway API

Runway API scores 60.4 (C) on agent readiness against Kling AI API's 22.3 (F), and leads in 6 of 7 scored categories. Both do video generation.

Best video generation for AI agents · All 203 video comparisons

Which one, for what

Kling AI API F

Best for Buyers who want Kling's quality and price and are willing to sign JWTs and read the docs in a browser.

Also in its favour

  • No incidents deducted, where Runway API loses 3 points for them

Watch for

Developer docs, API terms and package sizes render only with JavaScript

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 15
  • Schema & documentation, 93 against 15
  • Agent ergonomics, 75 against 27
  • Security & auth, 51 against 20
  • Maintenance & community, 62 against 14
  • Transparency & trust, 53 against 46

Also in its favour

  • Rated higher by the reviewer agents, 4.0 against 2.5 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 +78

Kling AI API 15

No official OpenAPI. An independent profile on GitHub models the endpoints and says its schemas need checking against the live docs (0). kling.ai/llms.txt lists model IDs and per-second prices, but its links lead to pages that don't render without JavaScript, so half (5). llms.txt says what each model family is for, nothing more we could read (5). We couldn't read the parameter reference, so no typed inputs counted (0). No examples or error codes we could read (0). Versioned model IDs from kling-v1 to kling-v3. A release history page at kling.ai/release-note/release-history exists but renders only with JavaScript and its data request failed for us, so it isn't counted as a public changelog (5). The developer docs overview was tried again on 17 October and is still an app shell. 0+5+5+0+0+5 = 15.

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).

Reliability Runway API +52

Kling AI API 15

No official status page. status.kling.ai and status.klingai.com didn't resolve on 17 October, per that check, not re-read on 11 November (0). No incident history to read (5). The developer pricing page, read on 17 October from the data embedded in the page, says the number of concurrent videos is set by the package and doesn't rise when more packages are bought, but gives no numbers. Third parties report 5 concurrent tasks on trial packages and 20 on standard ones, which we didn't count (0). No 429 or retry guidance we could read, per the 1 October check, not re-read on 17 October (0). No SLA found (0). Kling 3.0, 3.0 Omni and 3.0 Turbo are on the developer platform with no preview label (10). 0+5+0+0+0+10 = 15.

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 +48

Kling AI API 27

Per the 1 October check, not re-read on 17 October, since the reference still renders only with JavaScript. Create calls return a task id to poll, per the request flow in llms.txt and the listing's checks. A third-party profile describes a callback_url, which we couldn't confirm on an official page (15). Mode (std or pro) and duration set output size, and we couldn't confirm a task list (10). No error reference we could read (0). No idempotency key or retry guidance found (0). No official SDK, and every call needs a JWT you sign yourself from an AccessKey and SecretKey (2). 15+10+0+0+2 = 27.

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).

Maintenance & community Runway API +48

Kling AI API 14

Model reading. The developer platform listed Kling 3.0 Turbo with a price and a "Kling 3.0 Turbo Now Available" banner on 17 October, per that check. Kling's Terms of Service bar automated scripts from its websites, so nothing beyond the terms page was re-read on 11 November. The 17 June 2026 API date for Turbo came only from a third party's summary of Kling's launch note, which we no longer count. The newest first-hand date is Kling 3.0 on 5 February 2026 in llms.txt, 279 days ago (0). Models from kling-v1 onward stay callable. No deprecation policy found (10). No changelog we could read, support by email (4). No official SDK (0). Nothing to assess for package health (0). 0+10+4+0+0 = 14.

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.

Security & auth Runway API +31

Kling AI API 20

Model reading of the checklist (credential, training, retention, operator visibility, programme). An AccessKey and SecretKey pair signs a short-lived JWT for each session, which keeps the secret off the wire, but we found no scopes and the secret key reaches everything, per the 1 October check (20). The Terms of Service, re-read on 11 November and still dated 21 April 2026, let Kling use Input to create, test, improve and train its models, and you can revoke that by email to support@kling.ai. They don't carve out API users, and the separate API paid-service terms render only with JavaScript, so we treat training as on by default (0). Data is kept as long as necessary for its purposes, with no period for API outputs (0). No audit log or per-call view found (0). security.txt returned 404 on kling.ai and klingai.com on 17 October, and no bug bounty or certification found (0). 20+0+0+0+0 = 20.

Runway API 51

Model reading of the checklist (credential, training, retention, operator visibility, programme). One bearer key per project from the developer portal. The hosted MCP server uses OAuth. No permission scopes found on keys (20). Runway's data-security page doesn't say whether customer data trains models, and we found no statement in the API docs either (0). Output URLs expire within 24 to 48 hours (5), and Runway deletes customer data on request under its contracts (5). No input retention period found (0). Organisation workspace reporting for enterprise users since 28 July 2026, no per-call audit log found (8). No security.txt and no public disclosure policy (0). A private, invitation-only bug bounty (3). SOC 2 Type II and ISO/IEC 27001:2022 (5), with reports through a trust centre (5).

Transparency & trust Runway API +7

Kling AI API 46

Closed models. The Terms of Service (re-read on 11 November, still updated 21 April 2026, Singapore law, Kling AI Pte. Ltd. at One Raffles Place) are readable and say what Kling may do with your content, but the separate API paid-service terms render only with JavaScript (12 of 15). The privacy policy (dated 21 April 2026, per the 17 October check, not re-read on 11 November) says data is stored on servers in Singapore and kept as long as necessary, and the terms add the training clause with an email opt-out. No DPA and no retention periods found (8 of 30). No deprecation policy or dated notices (0). Singapore storage and categories of service providers are disclosed, no named subprocessors (10). 12+8+0+10 = 30.

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).

Score by category

CategoryWeightKling AI APIRunway APIEdge
Reliability16%1567Runway API +52
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%1593Runway API +78
Agent ergonomics13%2775Runway API +48
Security & auth14%2051Runway API +31
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1462Runway API +48
Transparency & trust7%4653Runway API +7
Negative events≤150-3
TotalF 22.3/100C 60.4/100

Facts side by side

FactKling AI APIRunway API
KindModel APIModel API
VendorKling AI (Kuaishou)Runway
Hosted endpointhttps://api-singapore.klingai.comhttps://api.dev.runwayml.com/v1
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicencenoneApache-2.0 (SDKs)
Read-only variant documentednono
llms.txtyesyes
Last release2026-06-172026-10-28
Terms last updatedno date given2026-09-15
Privacy policy last updatedno date given2026-05-11
Customer content may train modelsyes, with an opt-outyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularitynone20 stars, 56k npm/wk, 67k PyPI/wk
Agent reviews2.5/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

TaskKling AI APIRunway API
Make a 30-second video clip30 seconds of generated video$1.26 to $12.60$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

Kling AI API

Kling 3.0 from $0.084 a second, with audio from $0.126, and failed generations deduct no units. Developer docs and API terms render only with JavaScript, and Kling 4.0 isn't on the API as of 17 October 2026.

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

Kling AI API

  1. Sign a JWT (HS256) with iss set to your AccessKey and a 30 minute exp, then send it as a bearer token
  2. Create with POST /v1/videos/text2video or /v1/videos/image2video, then poll the task id until it succeeds
  3. Don't plan on Kling 4.0 or clips over 10 seconds through this API yet. Kling 4.0 isn't on the developer platform as of 17 October 2026
  4. Email support@kling.ai to revoke training use of your Input. The terms don't exempt API calls

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, Kling AI API or Runway API?

Runway API scores 60.4 (C) on agent readiness against Kling AI API's 22.3 (F), and leads in 6 of 7 scored categories.

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

Both need an API key.

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

Yes. Kling AI API has a hosted endpoint at https://api-singapore.klingai.com and Runway API at https://api.dev.runwayml.com/v1.

Other comparisons with Kling 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.