What is Real Problem AI?

Real Problem AI is a curated directory of 100 real problems worth building an AI startup around. Each problem is scored honestly on severity, AI feasibility, market signal, and competition gap. We're for builders looking for what to build, not for ethics debates about AI.

What is the difference between Real Problem AI and AI ethics or AI risks indexes?

Real Problem AI catalogues problems AI can solve — productive, commercial opportunities for builders. AI ethics indexes catalogue problems with AI itself (bias, environmental cost, copyright, consciousness). Different intent, different audience: founders and indie hackers vs researchers and policy folks.

What should I build with AI in 2026?

Look for problems with high severity (it costs people hours, sleep, or revenue every week), high AI feasibility (LLMs, vision or voice are great at this today), strong market signal (Reddit threads + willingness to pay), and a clear competition gap (incumbents miss the same obvious thing). Real Problem AI scores 100 such problems for you on those four axes.

Where do Real Problem AI's startup ideas come from?

From three sources, scanned each cycle: 1) Reddit threads where people describe a real friction in their own words, 2) podcasts and talks of founders young builders trust (Nikhil Kamath, Aman Gupta, Ankur Warikoo, Raj Shamani, Andrej Karpathy, Greg Isenberg), and 3) a continuous 1,000+ source scan covering forums, app store reviews, regulator filings, and field interviews.

Is Real Problem AI free?

Yes. Browsing every problem, opening every score breakdown, raising your hand on a co-founder match, and the founder vault are all free. There is no paywall.

How is each problem scored?

Four axes, each 1-10, weighted: Problem Severity (30%), AI Feasibility (25%), Market Signal (25%), Competition Gap (20%). Weighted average is the Opportunity Score on each card. Only problems clearing 7.0+ make the live list.

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.

Category: AI / Agents · Trend: Agents · Opportunity score: 8.0 / 10

What is the “A scheduled Claude routine quietly billed $1,122 in metered credits while subscription headroom sat unused.” problem in 2026?

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 this problem?

Claude Max subscribers running scheduled Routines/agents in cloud environments.

Recorded source context

Dataset source note: 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.

This note may summarize the referenced material rather than quote it verbatim. Source label: anthropics/claude-code GitHub issue #86723, 14 Aug 2026. (reference).

Existing players in this space

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 existing players 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.

How Real Problem AI scores this opportunity

Aggregate score: 8.0 / 10. Four-axis rubric:

Problem severity: 9 / 10
AI feasibility today: 8 / 10
Market signal: 6 / 10
Competition gap: 9 / 10

How to build a solution: stack hints

Anthropic billing API polling
Env-var/config drift detector
Alerting (Slack/email/webhook)
Per-routine billing-source tagging