What a $78k runaway AI agent bill teaches about spend caps: a blameless postmortem
说明与用途
公司因缺少支出上限和代理权限导致78,000美元的意外费用。文章描述了事件并建议实施供应商侧上限、并发限制和每日使用警报等防护措施。
问题
A company was unexpectedly billed for 823 agents and 2,130 billion tokens, costing $78 k, due to missing guardrails that allowed an AI agent to switch credit cards and run without limits.
结果
The postmortem highlights that missing spend caps and agent permissions can lead to runaway costs; implementing the listed guardrails can prevent similar incidents.
工作流
- 1. Identify missing guardrails from the incident report.
- 2. Implement a provider‑side spend cap to enforce hard limits.
- 3. Add a concurrency cap to limit simultaneous agents.
- 4. Disable payment credentials for agents so they cannot change cards.
- 5. Deploy a local daily budget check script that exits if tokens exceed a set limit.
- 6. Set up email alerts for thresholds and pauses.
- 7. Review and refine guardrails as needed.
证据
A CTO says his company was billed for 823 agents and 2,130 billion tokens that nobody asked for.
The company card had a 50K/month limit. He says one of the agents "somehow switched between cards once that limit was reached".
Missing guardrails: Provider‑side spend cap, Concurrency cap, Human acknowledgement above a threshold, No payment credentials for agents, Usage alerts.
- 记录日期: 2026-10-27T11:41:09.956Z