Complaints that English-speaking developers posted publicly between Nov 2 and Nov 4, 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. LLMjacking: stolen keys, $100k in a day, up to ~$1M before anyone revoked.

What developers are complaining about: Google Threat Intelligence / Mandiant coverage of LLMjacking dominated English feeds — attackers steal cloud tokens and LLM API keys, resell access, and leave victims with $100,000+ fraudulent charges in a single day and up to about $1M before access is cut (@DarkWebInformer, @NedPeterson99, @michaeloroberts, @niconuzzi). Reddit threads on OpenRouter and Claude keys echo the same failure mode: disable is not always enough; delete/rotate, and soft budget alerts do not hard-stop spend (r/openrouter, r/AI_Agents).

How PoYo answers: Treat every PoYo key as cash on your server — Getting Started says never put keys in frontend code, mobile apps, or public repos. Documented blast-radius controls on the API key page:

1. Revoke / rotate compromised keys immediately (delete, don't only "pause" in your head).
2. Enable an IP whitelist so a copied key only works from approved server IPs.
3. Set hourly / daily / total usage caps per key so a lingering secret has a ceiling.
4. Send X-End-User-ID on generation and native chat so you can block one abusive caller with 403 end_user_blocked without rotating every integration (End-user identification).
5. Watch GET /api/user/balance and stop on 402 insufficient_credits_error (user balance, error codes).

Billing is prepaid credits per successful output; failed generation tasks are not charged (homepage, llms.txt). Public docs do not promise refunds for usage made with a leaked key. Contact [email protected] if you believe a PoYo key was misused (Getting Started).

Q2. Plant a fake OpenAI-compatible key in a public repo — scavenged in under two hours.

What developers are complaining about: A honeypot experiment: a fake OpenAI-compatible API key seeded in public repos was used in less than two hours, then followed by model enumeration and test prompts to verify what the endpoint actually served (@polydaic). Same week, builders kept repeating that keys in client bundles or old git history are still live until you delete them.

How PoYo answers: Keep PoYo keys server-side only (Getting Started). Assume anything that ever hit a public commit is burned:

1. Rotate the key on the API key page; issue a new one for the real backend.
2. Lock the replacement with IP whitelist + per-key hourly / daily / total caps.
3. For multi-tenant proxies, require X-End-User-ID and block abusers with 403 without rotating the whole key (End-user identification).
4. Alert on GET /api/user/balance drops and treat 402 as a hard stop (user balance, error codes).

PoYo does not document a "honeypot key" product or automatic secret scanning of your GitHub — those stay on your side. Failed generation tasks are still not charged (llms.txt).

Q3. GhostAction-style supply chains: MCP configs and AI platform tokens in the blast radius.

What developers are complaining about: Security posts described GhostAction-style GitHub supply-chain compromises (hundreds of accounts/repos) that specifically hunt MCP configs, AI platform tokens, and SSH keys (@morphisec). Adjacent posts warned that once a panel or agent host is hijacked, planted SSH keys and stolen API credentials follow (@PacketReport1).

How PoYo answers: A PoYo key in an MCP config, agent host, or CI secret is still a prepaid wallet. Documented mitigations:

• Never commit keys; keep them out of frontend and public repos (Getting Started).
• Separate per-environment keys with IP whitelist and hourly / daily / total caps (API key page).
• Prefer PoYo's hosted MCP with a key you control and can rotate (Connect with MCP, Authentication).
• On suspicion: rotate, tighten caps/IP, check GET /api/user/balance, open [email protected] if needed.

Public docs do not claim automatic detection of compromised GitHub Actions or MCP hosts, and do not promise refunds for traffic that used a still-valid key.

Q4. DIY "llm-key-rotator": when one key 429s, flip to the next.

What developers are complaining about: Open-source and tip posts pushed tiny gateways that rotate API keys when one hits its rate limit (@jojeangsaing). Nearby ops chatter treated per-key RPM walls and shared-pool 429s as something you paper over with more keys rather than fix at the product layer.

How PoYo answers: Rotating keys around a 429 can hide the wrong problem. On PoYo, separate the codes (error codes):

Generation defaults: up to 20 new /api/generate/submit requests per 10 seconds per account; overage returns 429 and does not enter the queue. LLM endpoints are currently not rate limited (Getting Started). Prefer one key with documented caps over a rotator farm (API key page). Docs describe no automatic failover across labs — switch model IDs in your client if you need another provider. Failed generation tasks are not charged (llms.txt).

Q5. Same rebuild window: Gemini 503 upstream, DeepSeek 429, free-tier also 429.

What developers are complaining about: A rebuild log listed concrete failures in one window — gemini-4-barium → 503 / upstream unavailable after backoff, deepseek-v4-flash → 429, and a free DeepSeek route also 429 — then a single cooldown retry before shipping what still worked (@KeyoAPI). Gemini image/TTS burst 429s remain a standing Reddit theme for credit-tier / preview quotas (r/googlecloud, r/Bard).

How PoYo answers: Map retries to the documented codes (error codes):

• 429 → queue / exponential backoff (generation: 20 req / 10s default; LLM currently not rate limited) (Getting Started).
• 402 → top up credits; never treat as rate limit (user balance).
• 502 / 503 → transient upstream / busy; backoff and retry.

One PoYo key covers chat (OpenAI-compatible / Claude Messages / Gemini-native) plus media async submit/status (llms.txt, API overview). Live model schemas and prices: https://poyo.ai/models/<id>/llms.txt. Prefer webhooks over aggressive polling for long jobs. Docs do not claim transparent multi-lab failover or a published shared free-pool SLA — Getting Started states stability may be slightly lower than official providers.

Q6. Claude cache math: dashboard shows zero cache reads while you pay 1.25× on every cache write.

What developers are complaining about: Claude API billing threads warned that a misplaced cache_control can leave cache reads at zero while every write bills at a 1.25× multiplier — so "I turned on caching" still means full-price-ish input on every turn (@webtkdev). Separately, Anthropic Message Threads beta was pitched as a way to stop resending the entire agent transcript every turn (@readmodelmag).

How PoYo answers: PoYo chat is prepaid credits per successful output from one wallet — not a consumer plan mixed with a Platform cache ledger (homepage, llms.txt). Pick a Claude (or other) model ID, call Chat Completions / Messages / Gemini-native as documented, and read live pricing at https://poyo.ai/models/<id>/llms.txt (chat models, Anthropic). Cap runaway agents with per-key hourly / daily / total limits (API key page); empty balance returns 402 (error codes).

Public PoYo docs do not document Anthropic prompt-cache multipliers, Message Threads semantics, or a "cache hit %" dashboard of our own — if a model's upstream billing rules matter to you, verify them on that model's llms.txt and the provider's own docs before assuming a discount.

Q7. "Am I actually getting the model I paid for?" — aggregator authenticity anxiety.

What developers are complaining about: Builders asked how you know a reseller/router (OpenRouter called out by name) returns the same model you selected and paid for; Anthropic "FlashProve"-style verification was framed as filling that gap (@shlokafc, @AgentFilipHQ). Trust in inference providers is now a product requirement, not a footnote.

How PoYo answers: PoYo is a unified API key across image, video, music, 3D, and chat (API overview, llms.txt). You pass an explicit model ID; each model publishes a live schema and pricing file at https://poyo.ai/models/<id>/llms.txt. Media uses one async submit → status / webhook flow; chat uses documented OpenAI / Claude / Gemini-shaped endpoints.

What public docs do not claim today: a cryptographic "this response was signed by lab X" attestation product, automatic transparent failover between labs, or a published multi-tenant free-pool SLA. Getting Started sets realistic stability expectations versus official providers. Failed generation tasks are not charged (homepage). Cap keys and check GET /api/user/balance (API key page, user balance).

Q8. Agents now mint most of the tokens — and soft budgets don't hard-stop a runaway loop.

What developers are complaining about: Menlo Ventures' 2026 enterprise AI numbers circulated hard: enterprise AI spend jumped, Anthropic took a large share of LLM API spend, and agents now generate about 80% of tokens (@guilleflorvs, @MenloVentures). Cost-comparison posts showed enormous Claude vs DeepSeek gaps on the same workload (@aetherfrontier). Reddit builders argued major providers still offer alerts/soft budgets but not a hard absolute spend cap, so a hacked account or stuck agent loop can still print a six-figure bill (r/AI_Agents).

How PoYo answers: Price-per-token math does not cap monthly burn — your credit balance and key caps do. Operational controls documented today:

• Prepaid credits that never expire, no subscription (homepage).
• Per-key hourly / daily / total caps (API key page).
• GET /api/user/balance before large agent batches (user balance).
• Treat 402 as a hard stop; treat 429 as pace-and-retry (error codes).
• Do not blindly resubmit generation work: submission retries are not deduplicated and may create another task (Getting Started).
• For long media jobs, prefer webhooks; failed tasks are not charged (llms.txt). Generated media is retained 3 days — download promptly (Getting Started, video models).

There is no documented agent "stop condition" product that auto-kills a runaway tool loop for you — set key caps and build client-side step/budget limits if you need that. Public docs do not promise refunds for loops that spent a valid key's credits.

Quick map

Browse models and live prices on poyo.ai, schemas via llms.txt, and the full docs index at docs.poyo.ai/llms.txt.