15.1 What the work costs
Book 2 · Delegated IntelligenceChapter 6 · section 1 of 7
The bill for a workload is not one number. It is a stack of behaviors, and each one is a design decision someone made:
- Tokens in and out. The obvious line. Every run reads context and produces output, and both are metered. The toolkit survey’s price list covers the spread as of early October 2026: at the flagship list, GPT-6 Astra and Claude Fable 5.1 at $10 input and $50 output per million tokens; one generation down, GPT-6.1 Sol and Claude Opus 5.5 at $2 and $4 input, $10 and $20 output — the slot Google’s Gemini 4 Argon post-introductory pricing ($4 and $20) also targets, with GPT-6.1 Terra (added October 26) one rung below at $1 and $5; at the cheap end, open-weight tiers under a dollar for output. Same job, order-of-magnitude different bills.
- Cached and repeated context. A system that re-reads the same context every run pays for it every run. Caching discounts those reads; persistent memory can reduce them by retrieving only the records the task needs. Retrieved records still consume context tokens. Memory is an economic decision as much as a capability one.
- Tool calls and side effects. Searches, API calls, and sub-agents each carry their own price — some metered, some just slow.
- Retries and failures. A failed run still costs money, even when its output gets thrown away. If equally costly attempts fail independently one time in three and retry until success, the expected bill is one and a half times the cost of one attempt.
- The always-on tax. Heartbeats, watchers, and scheduled checks run whether or not there is work. The toolkit survey’s arithmetic: an hourly heartbeat re-reading a 300,000-token context costs about a dollar a day on its cheap open-weight model and about seventy-five dollars on Claude Fable 5.1. A fleet of a thousand multiplies both bills by a thousand. Model choice, context size, and interval are decisions about money.
Itemize the bill this way and each line turns out to be a lever the orchestrator controls: what context the run reads, how long memory persists, which model the step runs on, whether a failed run retries, and whether the heartbeat exists at all. The bill is an architectural document that happens to be denominated in dollars.
Contents