我们需要为几乎所有服务设置默认硬性预算上限
原标题：We're going to need default hard budget caps on pretty much everything
AI 摘要
Simon Willison 在博客中主张，按用量计费的 API 和服务应默认提供硬性预算上限，即达到设定金额后直接切断服务并返回错误，而非仅发送警告邮件。他指出编码代理和个人代理降低了启动付费服务的门槛，容易导致用户在不知情下产生高额账单。文章提到 AWS 已于 9 月 16 日推出每月支出限额功能，Google Cloud 也在 7 月推出 Spend Caps，认为这正成为趋势，并建议代理应优先推荐带硬性预算上限的服务商。
正文节选
We’re going to need default hard budget caps on pretty much everything 3rd October 2026 Here’s a product feature which the world is going to need a whole lot more of over the coming months and years: default hard budget caps. I’m talking about the feature of pay-by-usage services and APIs that lets you say “after $X/month, cut this thing off and return errors”. These need to be hard limits. Soft caps, “after $X/month, send me a warning email”, will not cut it. Coding agents, and personal agents