Skip to content
Back
Pricing briefing
PPika
Pika
PACKAGING CHANGE

Pika restricts top-up credits to its own Create tool, locking out API and MCP users

By , Co-founder, PricingSaaS

Published

Pika’s pricing page · Change detected

What changed

Pika added a disclaimer to the Credit Packs section of its pricing page stating that top-up credits are only usable within Pika Create on pika.art, and cannot be applied toward the API, MCP, iOS app, or old.pika.art. No credit prices or pack sizes changed — this is a scope restriction on where already-purchased credits can be spent, not a pricing change.

Why it matters

As AI-video tools multiply, access surface — web app versus API versus third-party integration — is becoming a real fault line for how credits get priced and restricted, not just how much they cost. Watch whether Pika follows with a dedicated API/MCP credit or pricing tier, or whether this restriction stands alone as a one-time clarification.

In context

Pika's move is its second in three days, coming right behind a commercial-license restriction to Creator+ added Sep 21 — a burst that's unusual against its normal ~50-day cadence between changes. It's also the company's first tracked move in the credits-and-usage-billing pattern, which has touched 348 companies over the past six months, including Snyk's shift of Enterprise to credit-based pricing and Notion ending its free Workers beta trial ahead of October credit billing. Unlike those moves, Pika isn't changing what credits cost — it's narrowing where they can be spent, keeping top-ups tied to the consumer Create surface rather than the API or MCP. That's a smaller, more defensive move than the market's broader credit-pricing overhauls, tightening a leak rather than chasing a trend.