Hard spending caps matter when agents can create billable work

Simon Willison argues that usage-based services need hard spending limits by default as agents make it easier to create applications and API workloads. A warning email leaves the service running and accumulating charges; a hard cap stops it. His central tradeoff is explicit: some builders would rather accept an interruption than discover an unexpectedly large bill.

Simon Willison · Oct 3, 2026

Why it matters

Agent-assisted projects need a decision about spending limits before unattended workloads run.

More context

Read this as an operational argument, then check what your actual provider enforces: alerts, per-service limits or a project pause. Choose a budget and decide how the application should behave when it reaches that limit.

Keep in mind

This is the author’s recommendation, not evidence that every provider offers a strict cap. Availability and covered charges vary. Stopping paid services can interrupt users, so account for that in your own design.

Original read