Pika API Club: 100+ models at reduced pricing, questions to ask first
Pika's API Club (Aug 5) offers 100+ models at reduced pricing, and the Sep 17 relaunch adds audio models. Seven questions to ask an aggregator.

Pika's blog, read 2026-10-03, describes API Club (August 5) as access to 100+ models at reduced pricing, and the post "Welcome to the New Pika" (September 17, 2026). It also lists audio models named Soundtrack, Music, SFX and Speech from August. Before you move a pipeline onto any aggregator, get answers to seven questions.
What Pika published
Only these items come from the Pika blog.
| Date | Item |
|---|---|
| Aug 5, 2026 | API Club: 100+ models at reduced pricing |
| Aug 2026 | Audio models: Soundtrack, Music, SFX, Speech |
| Sep 17, 2026 | Welcome to the New Pika |
Seven questions for any aggregator
These apply to Pika, to Sume and to everyone in between.
- Reduced compared with what: the model owner's list price, or the aggregator's own earlier price?
- Is there a margin on top of provider list? On Sume the margin is stated: provider list times 1.25 on every video model.
- Can you list the catalog and its limits by API? Sume returns
supported_durations,supported_resolutionsandpricing_skusfromGET /v1/videos/models. - What happens when a provider is down or at capacity? Sume documents
provider_capacity_exceededand tells you to retry with the same idempotency key. - Are retries safe? Sume replays an
Idempotency-Keyas the original job. - Which model answered? With
sume/auto, Sume does not disclose the family that served the request; if you need to know, pin a catalog id. - How do you export your jobs and outputs if you leave?
The audio side
Pika's audio line-up, music and sound effects and speech, mirrors a normal video pipeline. On Sume, music goes through the Music Router (POST /v1/music-router/generate, sume/music-auto by default, Lyria 3.5 today), speech through the hosted MCP tts_create tool, and sound effects are not covered by the docs reviewed here, so do not plan on them without checking the catalog.
Sume's Music Router guide says every router model charges the fixed Music price per audio generation, and duration fields are rejected, so you steer length in the prompt.
Reading a reduced price
A reduced price is a claim about a baseline, so find the baseline. If the comparison is against the owner's list, ask whether the owner's list includes volume terms. If it is against the aggregator's earlier price, it says little about what you will pay compared with going direct.
Sume states its approach plainly: workspace USD balance, reserved at submit, provider list times 1.25. That gives you a number you can verify against the provider's own page.
Decide on a pilot
Run the same ten prompts through each candidate, record cost per finished clip, failure rate and time to result, then compare. A reduced price matters only if the output and the retry behavior meet your standard.
Sources
Related posts
More in Comparisons
- Capacity fallbacks: Replicate's model swap vs pinning on Sume
Replicate lists a model falling back to another at capacity. On Sume you pin a model or send sume/auto, and a capacity error is retried with the same key.
- Prediction deadlines vs a Sume client deadline: stopping isn't cancel
A client-side deadline stops you watching a Sume job; it does not cancel it. Cancel works only before generation starts, so a missed deadline still bills.
- Runway enterprise exception requests vs Sume's queue-first admission
Runway's docs mention enterprise exception requests for higher volume. Sume takes extra jobs as queued and sets concurrency by plan. How to plan a big batch.
- Seedance 2.5, Wan 3.0 and Omni Flash: where each one is sold
Runway lists seedance2_5, wan3 and gemini_omni_flash_1.1 as API ids, Luma hosts Seedance 2.5, and Sume routes all three. How to compare.
Written by Sume