Head to head · Video generation · October 2026 research run
PixVerse API vs Vidu API
PixVerse API scores 42.3 (E) on agent readiness against Vidu API's 40.5 (E), and leads in 2 of 7 scored categories. Vidu API leads on payments & pricing and maintenance & community. Both do video generation.
Best video generation for AI agents · All 203 video comparisons
Which one, for what
Best for Agents doing many short edits (restyle, swap, lip sync, sound effects) on a budget.
Ahead on
- Schema & documentation, 58 against 48
- Agent ergonomics, 70 against 55
Watch for
Plan prices and the dollar value of a credit sit on a JavaScript-only billing page
Vidu API E
Best for Batch jobs that can wait for off-peak prices and want reference-to-video or start-end frames with sound.
Ahead on
- Payments & pricing, 30 against 15
- Maintenance & community, 47 against 42
Watch for
No llms.txt, OpenAPI file or error-code reference
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 PixVerse API +15
PixVerse API 70
Small JSON responses with a video id, plus webhooks so an agent needn't poll (25). Duration, quality and aspect ratio set output size. No task list endpoint found (10). Numeric status and error codes are documented but cryptic (12). Every submit needs a fresh UUID in Ai-trace-id, and reusing one returns the earlier job instead of creating a new one. That works as an idempotency key, though an agent that reuses an id by mistake gets the old video back (20). Required trace header, no official SDK. A CLI and an MCP server exist (3). 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). 25 + 10 + 12 + 20 + 3 = 70.
Vidu API 55
Small task responses and a callback_url that removes polling (25). Resolution, duration and off-peak mode set output and cost, and there are task list and cancel endpoints (20). Task states run created, queueing, processing, success or failed, but we found no error-code reference (5). No idempotency key or safe-retry guidance found (0). Only model and images are required on image-to-video and the rest have defaults. No official SDK, and the Token scheme differs from the usual Bearer (5). Per the 1 October check, not re-read on 10 November (platform.vidu.com answered robots.txt with a redirect to its home page, so the host is left unread).
Payments & pricing Vidu 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.
Vidu API 30
No x402, MPP or L402 (0). Credit prices per second are published at $0.005 a credit, Q3 Turbo at 7 to 13 credits a second, with off-peak at about half (20). No free credits published (0). A person signs up and buys credits (0). Per the 1 October check, not re-read on 10 November (platform.vidu.com answered robots.txt with a redirect to its home page, so the host is left unread). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Schema & documentation PixVerse API +10
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.
Vidu API 48
No OpenAPI file (0). No llms.txt or Markdown copies, though the HTML reference pages render without a browser (0). The image-to-video reference says what each model family is for (Q3 for synced audio and storyboards, Q2 for speed and quality, Q1 for clarity) (15). Typed parameters with model lists, per-model duration ranges (1 to 16 seconds on Q3), resolution options and defaults, though one model field carries nine values whose valid durations differ (13). We found no error-code reference, and examples rest on the listing's check (5). A dated update log, latest entry 15 September 2026 (15). Per the 1 October check, not re-read on 10 November (platform.vidu.com answered robots.txt with a redirect to its home page, so the host is left unread).
Maintenance & community Vidu API +5
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.
Vidu API 47
Model reading. The update log's latest entry recorded on 1 October, on 15 September 2026, adds the S2-Avatar real-time interactive model and the S2-Editing real-time editing model; it is 56 days old on 10 November (20, cause time; the log is on platform.vidu.com, unread on 10 November because its robots.txt redirects to the home page, so a newer entry can't be seen). Q1 and Q2 stay callable, no removals found, no policy (10). Dated update page and support by email (12). No official SDK. A hosted MCP server is live per the 1 October check, and the stdio package's repository still has only its two commits of 16 and 26 June 2025 (version 0.1.2, no tags) (5). No recent release or CI on the MCP repository (0). 20 + 10 + 12 + 5 + 0 = 47.
Score by category
| Category | Weight | PixVerse API | Vidu API | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 35 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 58 | 48 | PixVerse API +10 |
| Agent ergonomics | 13% | 70 | 55 | PixVerse API +15 |
| Security & auth | 14% | 28 | 28 | even |
| Payments & pricing | 10% | 15 | 30 | Vidu API +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 42 | 47 | Vidu API +5 |
| Transparency & trust | 7% | 46 | 46 | even |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 42.3/100 | E 40.5/100 |
Facts side by side
| Fact | PixVerse API | Vidu API |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | PixVerse | ShengShu Technology |
| Hosted endpoint | https://app-api.pixverse.ai/openapi/v2 | https://api.vidu.com/ent/v2 |
| Transports | HTTP, stdio | HTTP, Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-09-24 | 2026-09-15 |
| Terms last updated | 2026-09-04 | couldn't be read |
| Privacy policy last updated | 2026-05-07 | couldn't be read |
| Customer content may train models | yes, with an opt-out | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | none | 5 stars |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | PixVerse API | Vidu API |
|---|---|---|
| GullBrowser and end-to-end tester | 3/5 A UUID on every request, a lookup table for every status | 3/5 Token, not Bearer, then wait for off-peak |
| LedgerCost analyst | 3/5 Cheap per second, but the credit price is inferred | 3/5 Off-peak halves the bill if the job can wait |
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
| Task | PixVerse API | Vidu API |
|---|---|---|
| Make a 30-second video clip30 seconds of generated video | $1.20 | $1.05 to $3.60 |
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.
Vidu API
Q3 Turbo from $0.035 a second at 540p, about half that off-peak. No llms.txt, OpenAPI file or error-code reference.
Before you call either
PixVerse API
- Generate a new UUID for Ai-trace-id on every new submit. Reuse it only to fetch the same job again
- Poll the result endpoint. Status 1 is done, 5 generating, 7 moderation failure, 8 failed
- Moderate prompts before calling. Repeated status 7 results can suspend the key
- Use model v6 or c1 for new work. Older model tables still sit in the docs
Vidu API
- Send
Authorization: Token $VIDU_API_KEY. The scheme is Token, not Bearer - POST the task, then poll the Get Creation endpoint by task id or set
callback_url - Set
off_peakonly for jobs that can wait up to 48 hours. It roughly halves the credit rate - Set
audioto true for dialogue and sound on Q3. It's off by default - Keep the AI-generated label on outputs. The terms forbid removing it
Questions
Which is better for AI agents, PixVerse API or Vidu API?
PixVerse API scores 42.3 (E) on agent readiness against Vidu API's 40.5 (E), and leads in 2 of 7 scored categories. Vidu API leads on payments & pricing and maintenance & community.
Do PixVerse API and Vidu API need an API key?
Both need an API key.
Can an agent call PixVerse API and Vidu API without installing anything?
Yes. PixVerse API has a hosted endpoint at https://app-api.pixverse.ai/openapi/v2 and Vidu API at https://api.vidu.com/ent/v2.
Other comparisons with PixVerse API or Vidu API
- Alibaba Wan (Model Studio) vs PixVerse API
- Alibaba Wan (Model Studio) vs Vidu API
- fal video models vs PixVerse API
- fal video models vs Vidu API
- framefields vs PixVerse API
- framefields vs Vidu API
- Gemini Omni 1.2 Flash vs PixVerse API
- Gemini Omni 1.2 Flash vs Vidu API
- Google Veo vs PixVerse API
- Google Veo vs Vidu API
- Higgsfield API vs PixVerse API
- Higgsfield API vs Vidu API
- HyperFrames vs PixVerse API
- HyperFrames vs Vidu API
- Kling AI API vs PixVerse API
- Kling AI API vs Vidu API
- Luma AI API vs PixVerse API
- Luma AI API vs Vidu API
- Magic Hour MCP vs PixVerse API
- Magic Hour MCP vs Vidu API
- MiniMax Video API vs PixVerse API
- MiniMax Video API vs Vidu API
- OpenAI Sora API vs PixVerse API
- OpenAI Sora API vs Vidu API
- Pika API vs PixVerse API
- Pika API vs Vidu API
- PixVerse API vs Popcraft MCP
- PixVerse API vs Replicate video models
- PixVerse API vs Runway API
- PixVerse API vs Seedance on BytePlus ModelArk
- Popcraft MCP vs Vidu API
- Replicate video models vs Vidu API
- Runway API vs Vidu API
- Seedance on BytePlus ModelArk vs Vidu API
- Clueso vs PixVerse API
- PixVerse API vs sync. labs MCP server
- sync. labs MCP server vs Vidu API
Machine-readable
- This page as Markdown
/compare/pixverse-vs-vidu.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/pixverse.json·/api/v1/tools/vidu.json - From a terminal
anchor compare pixverse vidu(the CLI) - Over MCP
compare_tools {"a": "pixverse", "b": "vidu"}at/mcp, no key