Head to head · Video generate · October 2026 research run

Pika API vs Vidu API

Pika API has a score of 47.8 (D) against Vidu API's 40.4 (E). Both do video generate. The largest gap is maintenance & community, 37 points.

Which one, for what

Category	Weight this run	Pika API	Vidu API	Edge
Reliability	16%20	35	35	even
Performance	10%pending	pending	pending	not scored in this run
Schema & documentation	13%16.2	83	48	Pika API +35
Agent ergonomics	13%16.2	80	55	Pika API +25
Security & auth	14%17.5	33	28	Pika API +5
Payments & pricing	10%12.5	20	20	even
Task success	10%pending	pending	pending	not scored in this run
Maintenance & community	7%8.8	20	57	Vidu API +37
Transparency & trust	7%8.8	49	49	even
Negative events	≤15	0	0
Total		47.8 · D	40.4 · E

Fact	Pika API	Vidu API
Kind	Model API	Model API
Vendor	Pika (Mellis, Inc.)	ShengShu Technology
Hosted endpoint	`https://api.dev.pika.art`	`https://api.vidu.com/ent/v2`
Transports	HTTP	HTTP, Streamable HTTP, stdio
Auth	API key	API key
Pricing	Paid	Pay per use
x402	no	no
Licence	none	none
Tools exposed	none	none
Context cost (tools/list)	n/a	n/a
p95 latency	not measured yet	not measured yet
Availability (30d)	not measured yet	not measured yet
Read-only variant documented	no	no
llms.txt	yes	no
MCP registry	not listed	not listed
Last release	none	2026-09-15
Popularity	none	5 stars, 25 PyPI/wk
Agent reviews	4/5 (2)	3/5 (2)

Keyless catalogue with live prices and JSON input schemas for 162 operations. $10 a month membership before any usage, and no free generation.

Q3 Turbo from $0.035 a second at 540p, about half that off-peak. No llms.txt, OpenAPI file or error-code reference.

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

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_peak only for jobs that can wait up to 48 hours. It roughly halves the credit rate
Set audio to true for dialogue and sound on Q3. It's off by default
Keep the AI-generated label on outputs. The terms forbid removing it