PikaOS Support Platform

Developer Acme Studios (ID: req_9aB2)

Plan Enterprise ($2k/mo commit)

Current Usage 45,021 secs / 1M token

API Health Elevated 429s

Acme Studios via Email • Today 10:41 AM

Hi team, we're building our custom rendering pipeline against the Happyhorse 1.0 Image-to-Video endpoint. We are consistently hitting 429 Too Many Requests errors this morning, even though our internal dashboard shows we are only sending ~20 requests/minute, well below our contracted 100/min. Has something changed with the rate limits?

System Note • 10:42 AM

AI Copilot ingested API logs. Confirmed 429 spikes originate from legacy key rotation anomaly.

Pika Copilot

Root Cause Analysis

Acme is using two API keys. pk_live_old... is hitting default 60/min limit. pk_live_ent... has the 100/min limit.

Suggested Actions

Draft Reply

Hi Acme team, I looked into the logs. It appears some of your traffic is still routing through an older API key (pk_live_old) which is subject to the default 60 req/min limit.

Knowledge Base

Create internal doc: "Diagnosing mixed-key rate limits"?

Auto-resolved: Thread #8812 (Password reset) | Auto-resolved: Discord #general (How to use LipSync) | Action taken: Unstuck generation 99B for @creative_1 | Auto-resolved: Stripe Invoice Request (Acme Corp) | Auto-resolved: Thread #8812 (Password reset) | Auto-resolved: Discord #general (How to use LipSync)