2026-10-23: 7 API complaints we heard today

Complaints that English-speaking developers posted publicly between Oct 21 and Oct 23, 2026, paraphrased below with links to the original posts. Each answer uses only what PoYo's public site and docs say today, and links to the page it comes from. Where the docs don't cover something, we say so.

---

Q1. My Gemini key was still sitting in Railway env vars — someone burned $800 overnight.

What developers are complaining about: The Railway env-var disclosure is still producing fresh bills. One developer said he lost $800 when someone used his Google Cloud Gemini API key on Gemini 4 Argon priority tier. Another said OpenRouter emailed him that two personal keys had been revoked after they were used to run someone else's agents. A third summed up the week as OpenCode, Railway, and LiteLLM all targeting AI inference keys within five days. The recurring advice: a leaked key keeps getting spent until someone reads the bill.

How PoYo answers: Rotate first — a leaked secret is still a leaked secret. After that, our docs list controls that limit what a stolen PoYo key can do:

• IP whitelist. Allow only your approved server IPs on a key, so a key copied out of an env var does not work from the attacker's machine. See the API key page and Getting Started.
• Per-key usage caps (hourly, daily, and total), so one key has a hard ceiling before you notice.
• Per-end-user blocking. Send an X-End-User-ID header and you can block one abusive caller on a key without rotating it. See End-user identification.

If you still want Gemini 4 Argon itself, PoYo lists it at $1.60 input / $8.00 output per 1M tokens (20% below official standard rates), behind the same PoYo key as your other models.

Our public docs don't promise refunds for usage made with a leaked key. If you think a PoYo key was misused, revoke it and contact support ([email protected]).

---

Q2. Gemini AI Studio and Vertex both hit 429s and timeouts — is yesterday still not over?

What developers are complaining about: One developer wrote that Gemini API from AI Studio or Vertex was "unbearably unstable and slow" with 429s and timeouts, and asked whether the previous day's problems had even ended. Separately, Reddit threads in r/openrouter keep explaining that a paid aggregator balance does not raise an upstream model's quota — you still get 429 when the shared pool is full.

How PoYo answers: Our error codes page gives each status one meaning and one recommended action:

Getting Started publishes the default generation limit: up to 20 new generation requests per 10 seconds, per account. Requests over that limit get HTTP 429 and do not enter the queue. Chat and media models share one PoYo key and are listed in llms.txt, so switching models is a model string change — not a new vendor onboarding.

The docs describe no automatic failover between providers. Build fallback into your client. Getting Started also says PoYo's "overall stability may be slightly lower than official providers."

---

Q3. My agent needs image, video, audio, and chat — that's five SDKs and five billing dashboards.

What developers are complaining about: One builder framed the problem plainly: analyzing an image, generating a video, transcribing audio, and embedding text meant five SDKs, five API keys, and five billing dashboards. Product pitches on X kept echoing the same fatigue — tired of managing multiple AI API keys and billing dashboards.

How PoYo answers: llms.txt describes PoYo as one unified model API: image, video, music, 3D, chat, and tools behind one API key. Media models use one async submit/status workflow (POST /api/generate/submit, then poll status or set callback_url). Chat uses OpenAI-compatible, Claude Messages, or Gemini native endpoints on the same key. The API overview documents that two-endpoint architecture, and the homepage repeats "one async API" for image, video, music, chat, and 3D.

---

Q4. Seedance generated three videos and charged me like I ordered six.

What developers are complaining about: One creator apologized for messy edits and added that Seedance generated three videos instead of one and charged twice as many credits. Another thread reminded people that reference seconds can be billable too — a 15-second reference plus a 15-second output can mean 30 billable seconds. A third called Seedance 2.5 absurdly slow and expensive for authentic UGC.

How PoYo answers: The Seedance 2.5 model page publishes the billing rule in plain language: with video input, billed seconds = output duration + reference video duration. Per-second prices are listed by resolution (for example 480p without video input at $0.140/s, 1080p without video input at $0.570/s). Iterate at 480p, then render the final cut at higher resolution. All video routes share the same async flow on the AI Video API page. llms.txt and the homepage both state that failed tasks are not charged — but a finished clip you don't like still counts as successful output.

---

Q5. Anthropic says my credit balance is too low — I thought my subscription covered this.

What developers are complaining about: Multiple posts over the window just pasted the same Anthropic error: "Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits." Separately, people building n8n agents were reminded that OpenAI API billing is separate from a ChatGPT subscription. The complaint underneath is the same: product plans and API credits look alike until a request dies mid-flow.

How PoYo answers: PoYo's billing model is documented as prepaid credits only:

• The homepage says one-time purchases with no recurring subscriptions, and credits never expire.
• When the balance is gone, the API returns 402 insufficient_credits_error (error codes) instead of silently opening a post-pay invoice.
• You can poll GET /api/user/balance for credits_amount in real time (user balance).

Compare chat and media prices on the pricing page before you submit paid work.

---

Q6. I keep losing track of what my AI coding actually costs today.

What developers are complaining about: One developer said he kept losing track of AI coding costs, so he built desktop widgets for OpenRouter spend and remaining credits. After the Railway week, another reminder was blunt: set billing caps on AI providers so a leaked key has a ceiling.

How PoYo answers: Three documented pieces fit this complaint:

1. Live balance. GET /api/user/balance returns credits_amount for dashboards and alerts (user balance). The docs suggest caching and refreshing after tasks rather than polling constantly.
2. Per-key hourly, daily, and total caps on the API key page, so a coding agent key cannot drain the whole account (Getting Started).
3. Prepaid stop. Empty balance → 402, not an unbounded invoice (error codes).

---

Q7. My long agent run hits a hard gateway timeout before the model finishes thinking.

What developers are complaining about: One developer said he could not push Gemini Argon hard in the consumer app, moved to Google AI Studio, and still hit a hard server-side gateway limit of exactly 10 minutes. That is the classic sync-HTTP pain: the model is still working, the connection is already dead.

How PoYo answers: Generation on PoYo is designed to be asynchronous. Getting Started and the API overview say: submit a task, save the task_id, then poll status or receive a webhook. A successful submit returns HTTP 200 and a task_id — it does not mean generation finished. For production workloads, the docs prefer signed webhooks over frequent polling. Chat can use streaming on the documented OpenAI-compatible, Claude Messages, or Gemini native endpoints (llms.txt), while long media jobs stay on the submit/status path so they are not tied to a single gateway timeout.

---

Quick map