Head to head · Video generation · October 2026 research run

PixVerse API vs Runway API

Runway API scores 60.4 (C) on agent readiness against PixVerse API's 42.3 (E), and leads in every scored category. Both do video generation.

Best video generation for AI agents · All 203 video comparisons

Which one, for what

PixVerse API E

Best for Agents doing many short edits (restyle, swap, lip sync, sound effects) on a budget.

Also in its favour

  • Runs on your own machine
  • No incidents deducted, where Runway API loses 3 points for them

Watch for

Plan prices and the dollar value of a credit sit on a JavaScript-only billing page

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 58
  • Agent ergonomics, 75 against 70
  • Security & auth, 51 against 28
  • Payments & pricing, 30 against 15
  • Maintenance & community, 62 against 42
  • Transparency & trust, 53 against 46

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

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.

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

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.

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

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.

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

Maintenance & community Runway API +20

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.

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.

Payments & pricing Runway API +15

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.

Runway API 30

No x402, MPP or L402 (0). Per-second credit prices for every model are published at $0.01 a credit without a login, 12 credits a second for Gen-4.5 (20). No free generation credits, $10 minimum first purchase (0). A person signs up in the developer portal and buys credits (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Transparency & trust Runway API +7

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.

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

CategoryWeightPixVerse APIRunway APIEdge
Reliability16%3567Runway API +32
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5893Runway API +35
Agent ergonomics13%7075Runway API +5
Security & auth14%2851Runway API +23
Payments & pricing10%1530Runway API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4262Runway API +20
Transparency & trust7%4653Runway API +7
Negative events≤150-3
TotalE 42.3/100C 60.4/100

Facts side by side

FactPixVerse APIRunway API
KindModel APIModel API
VendorPixVerseRunway
Hosted endpointhttps://app-api.pixverse.ai/openapi/v2https://api.dev.runwayml.com/v1
TransportsHTTP, stdioHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicencenoneApache-2.0 (SDKs)
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-242026-10-28
Terms last updated2026-09-042026-09-15
Privacy policy last updated2026-05-072026-05-11
Customer content may train modelsyes, with an opt-outyes
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularitynone20 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

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

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.

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

PixVerse API

  1. Generate a new UUID for Ai-trace-id on every new submit. Reuse it only to fetch the same job again
  2. Poll the result endpoint. Status 1 is done, 5 generating, 7 moderation failure, 8 failed
  3. Moderate prompts before calling. Repeated status 7 results can suspend the key
  4. Use model v6 or c1 for new work. Older model tables still sit in the docs

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

Runway API scores 60.4 (C) on agent readiness against PixVerse API's 42.3 (E), and leads in every scored category.

Do PixVerse API and Runway API need an API key?

Both need an API key.

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

Yes. PixVerse API has a hosted endpoint at https://app-api.pixverse.ai/openapi/v2 and Runway API at https://api.dev.runwayml.com/v1.

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