The case for default hard API spending caps
Original: We're going to need default hard budget caps on pretty much everything
Why This Matters
AI agents autonomously triggering cloud spend make runaway billing a systemic risk, not an edge case.
Simon Willison calls for default hard spending caps on cloud APIs and services, citing AI coding agents that can silently generate massive bills. AWS launched spending limits in Sept 2026; Google Cloud followed in July 2026.
Simon Willison argues that pay-by-usage services and APIs urgently need default hard budget caps — not soft warning emails, but actual hard stops that return errors once a spending threshold is hit. The impetus is AI coding agents, which dramatically lower the friction of deploying code that calls paid APIs or spins up billable cloud infrastructure. A misconfigured or runaway agent can rack up thousands of dollars overnight while a user sleeps through a warning email. Willison's proposed model: hard caps on by default, with an explicit opt-out checkbox for users who understand the risk. He singles out AWS as the service most in need of this, noting widespread fear of runaway bills among personal-project developers. AWS did quietly launch spending limits in mid-September 2026, though the feature remains in limited availability. Google Cloud launched a comparable "Spend Caps" feature in July 2026. Willison also floats the idea that agents themselves could steer builders toward capped providers and flag uncapped deployments as risky.