Cite as: Real Problem AI problem “A scheduled Claude routine quietly billed $1,122 in metered credits while subscription headroom sat unused.”. Opportunity score 8.0 out of 10 (severity 9, AI feasibility 8, market signal 6, competition gap 9). Category AI / Agents. Trend Agents. Source signal: anthropics/claude-code GitHub issue #86723, 14 Aug 2026.. Canonical URL: https://www.realproblem.ai/idea/why-did-a-scheduled-routine-quietly-bill-1122-in-metered-credits.
A scheduled Claude routine quietly billed $1,122 in metered credits while subscription headroom sat unused.
Setting ANTHROPIC_API_KEY in a cloud routine's environment silently redirects billing off the subscription and onto pay-as-you-go credits, with no UI warning, for two months straight.
Who has it: Claude Max subscribers running scheduled Routines/agents in cloud environments.
Evidence
“Scheduled Routines created and owned under a Max 20x subscription ($200/mo) were billed entirely to pay-as-you-go API credits rather than drawing down subscription usage, while substantial subscription headroom remained... Over two months this amounted to $1,122.83 in metered API charges.”
Quoted word for word from the public post linked below. Nobody submitted it to Real Problem AI.
anthropics/claude-code GitHub issue #86723, 14 Aug 2026.Scoring breakdown
Existing players
- Routines UI · No indication that an env var silently reroutes billing.
- Manual billing statement review · Only catches the surprise after weeks of charges.
- Auto-reload credit grants · Keep paying the metered bill instead of surfacing the misconfiguration.
What they are missing
A billing-source sentinel that watches for subscription-vs-metered drift on scheduled agent runs and alerts the moment a routine starts drawing from the wrong pool.
Stack hint
#ATB4 · Canonical URL: https://www.realproblem.ai/idea/why-did-a-scheduled-routine-quietly-bill-1122-in-metered-credits