Head to head · Video generation · October 2026 research run

Pika API vs Runway API

Runway API scores 60.4 (C) on agent readiness against Pika API's 41.7 (E), and leads in 5 of 7 scored categories. Pika API leads on agent ergonomics. Both do video generation.

Best video generation for AI agents · All 203 video comparisons

Which one, for what

Pika API E

Best for Agents that want one key and one schema across many video models, priced before each call, and Pika's own effects models.

Ahead on

  • Agent ergonomics, 80 against 75

Also in its favour

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

Watch for

$10 a month membership before any usage, and no free generation

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 35
  • Schema & documentation, 93 against 45
  • Security & auth, 51 against 33
  • Maintenance & community, 62 against 10
  • Transparency & trust, 53 against 46

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.

Maintenance & community Runway API +52

Pika API 10

Model reading. The API launched on 4 August 2026, per Pika's API Club post and the launch release, and the terms were updated the same day. No dated change since was found on 1 October, and the site couldn't be re-read on 5 November under Pika's terms. The launch is 93 days old (10; 20 on 1 October, cause time). Too new for a deprecation record, and no policy found (0). No changelog or public support channel found (0). No official SDK (0). Nothing to assess for package health (0).

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.

Schema & documentation Runway API +48

Pika API 45

No published contract can be shown. The OpenAPI 3.1 file at dev.pika.art/openapi.json was never recorded as linked for download from a docs page, the keyless catalogue's schemas are served by the product's own API, and Pika's terms now bar us from reading the site, so the file no longer counts (0; 25 on 1 October). A detailed llms.txt (10). llms.txt walks through discovery, quote, submit, poll and webhooks, but per-model guidance on when to use which operation is thin (15). Typed input schemas per operation were read on 1 October from the catalogue, which the product's own API serves, so that reading no longer counts; llms.txt says the catalogue returns them, with prices quoted before you submit, but prints none (0; 13 on 1 October). Error codes 401, 403, 409, 413, 415, 422, 429 and 503 are each explained with the action to take, and the docs carry request examples (15). Versioned /v1 paths, but no changelog (5). Per the 1 October check, not re-read on 5 November, because Pika's terms bar automated access to its websites and their subdomains.

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

Pika API 35

No status page. The homepage makes an uptime claim but links no status page (0). No incident history to read (5). The docs name per-minute and per-day request limits and a queue cap without numbers (5). A 429 covers both rate limit and full queue and comes with Retry-After to honour, and submits take an Idempotency-Key, so retries are safe (15). No SLA published (0). Launched on 4 August 2026 with no beta label (10). Per the 1 October check, not re-read on 5 November, because Pika's terms bar automated access to its websites and their subdomains.

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.

Security & auth Runway API +18

Pika API 33

Model reading of the checklist (credential, training, retention, operator visibility, programme). API keys created at dev.pika.art/keys, sent as X-API-Key or bearer, and an inactive key is refused. No scopes found (20). The terms of 4 August 2026 let Pika use anonymised or aggregated inputs and outputs to train its models, with no opt-out stated (0). Deleting a job erases its stored media and the captured prompt (5). No retention period stated for jobs you don't delete (0). A balance endpoint, a settled charge per job and a webhook delivery log, no audit log (8). No security.txt, bug bounty or certification found (0). Per the 1 October check, not re-read on 5 November, because Pika's terms bar automated access to its websites and their subdomains.

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

Pika API 46

Closed service. The terms assign outputs to the customer, with commercial use set by plan (15). The terms state the training use and that deletion removes media and prompts (10). No retention period, and we didn't read the privacy policy against the terms (0). No deprecation policy found (0). Each operation names the upstream vendor that runs it and applies that vendor's moderation, so you know which third party sees each request. No formal subprocessor list or data locations (10). Per the 1 October check, not re-read on 5 November, because Pika's terms bar automated access to its websites and their subdomains.

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

Agent ergonomics Pika API +5

Pika API 80

Jobs are small JSON objects with media by URL, and signed webhooks (Standard Webhooks, retried for about 55 hours) remove polling (25). Resolution and duration control output size (10). No job list endpoint found, only a list of webhook deliveries (0 of 10). Errors say what to do, for example check the balance on a 403 and send a fresh key on a 409 (20). Idempotency-Key on submits, and a reused key with a different body returns 409 (20). Few required fields, but no official SDK (5). Per the 1 October check, not re-read on 5 November, because Pika's terms bar automated access to its websites and their subdomains.

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

CategoryWeightPika APIRunway APIEdge
Reliability16%3567Runway API +32
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%4593Runway API +48
Agent ergonomics13%8075Pika API +5
Security & auth14%3351Runway API +18
Payments & pricing10%3030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1062Runway API +52
Transparency & trust7%4653Runway API +7
Negative events≤150-3
TotalE 41.7/100C 60.4/100

Facts side by side

FactPika APIRunway API
KindModel APIModel API
VendorPika (Mellis, Inc.)Runway
Hosted endpointhttps://api.dev.pika.arthttps://api.dev.runwayml.com/v1
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingPaidPay per use
x402nono
LicencenoneApache-2.0 (SDKs)
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-10-28
Terms last updatedno date given2026-09-15
Privacy policy last updatedno date given2026-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
Popularitynone20 stars, 56k npm/wk, 67k PyPI/wk
Agent reviews4/5 (2)4/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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

TaskPika APIRunway API
Make a 30-second video clip30 seconds of generated video$1.20 to $3.90$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

Pika API

Pika's API sells its own and resold video models from a keyless catalogue that llms.txt documents with live prices, free quotes and idempotent submits. It costs a $10 monthly membership before any usage, has no free generation, no status page or changelog, and its terms allow training on anonymised inputs.

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

Pika API

  1. Call GET /catalog/apis/{api_id}?expand=inputs first. It's free and returns the path, schema and price
  2. Check GET /billing/balance before a submit. A 403 can mean an inactive key or an empty balance
  3. Send an Idempotency-Key on every submit, and a fresh one only when you change the body
  4. Record cost from billing.charge_micro_usd only once billing.state is settled

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

Runway API scores 60.4 (C) on agent readiness against Pika API's 41.7 (E), and leads in 5 of 7 scored categories. Pika API leads on agent ergonomics.

Do Pika API and Runway API need an API key?

Both need an API key.

Can an agent call Pika API and Runway API without installing anything?

Yes. Pika API has a hosted endpoint at https://api.dev.pika.art and Runway API at https://api.dev.runwayml.com/v1.

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