Agent Budget Controls
The practice of setting explicit per-agent spending limits inside a multi-agent system, so runaway costs can't blow up the business before a human notices. Paperclip treats budgets as a first-class feature on every agent [src-001].
Key points
- Every agent in Paperclip has its own monthly spend cap. If a designer agent is configured with a $50/month budget, it stops working when it hits the cap — regardless of what the CEO agent wants it to do [src-001].
- Spend analytics only surface when using pay-per-token billing. If you're running inside a Claude subscription, the budget figures show as zero because there's no per-token meter [src-001].
- Budget limits function as a safety rail for autonomy. The more you let agents self-direct (e.g., letting the CEO hire without approval), the more important it is that each agent has a hard stop on spending.
- Budgets are per agent, not per company or per task. This means a high-priority task can't temporarily borrow budget from low-priority agents — a design choice that favours predictability over flexibility.
- Datadog adds a reliability angle: budgets can force ReAct loops or multi-agent workflows to terminate after a maximum number of calls or tokens, preventing runaway loops from exhausting capacity or triggering cascading rate-limit failures [src-037].
- In production LLM systems, budgets work alongside queues, backoff, and fallback capacity as part of LLM Capacity Engineering [src-037].
- Google Cloud expands budgets into fiscal responsibility: agents should choose token/API/MCP paths judiciously and reserve limited budget for higher-priority business work [src-043].
- Fiscal responsibility is part of the Agent Governance Framework, not only a finance dashboard; the agent's choice of path can itself be governed [src-043].
Related entities
Related concepts
- Agent Orchestration
- Multi Agent Companies
- Zero Human Companies
- LLM Capacity Engineering
- Token Economics
- React Loop
- Agent Governance Framework
- Enterprise Agent Governance
- Tool Schema Tax
Source references
- [src-001] Nate Herk — "Claude Code + Paperclip Just Destroyed OpenClaw" (2026-03-28)
- [src-037] Datadog — "State of AI Engineering" (2026-04-21)
- [src-043] Google Cloud Events — "Operationalize AI: A blueprint for managing enterprise agents at scale" (2026-04-24)
2026-07-17 mission-and-value update
- Decathlon's CDO proposes evaluating an agent like a new employee: define its mission, expected value, cost, support model, and monitoring at creation time [src-243].
- This extends budget control from a hard spending ceiling into a business case and lifecycle responsibility [src-243].
Recommended next
Keep reading from this thread
From 500 indexed pages and articles.
- Wiki concept LLM Capacity Engineering The discipline of keeping AI applications reliable when model-provider rate limits, concurrency caps, retries, long loops, and tool fan-out Related by capacity
- Wiki concept Agent Governance Framework Google Cloud's four-vector framing for evaluating whether enterprise agents are behaving acceptably in production. Related by budget
- Wiki concept Multi-Agent Companies A pattern where a set of AI agents is organised as a company org chart — CEO, engineers, designers, marketers, QA — each with Related by 001