Evidence-linked trend hypothesis

Agent economics moves to completed work

Token prices and subscription fees are weak proxies when turns, retries, delegation, verification, latency, and successful outcomes drive the real cost.

Current thesis

  • The economically meaningful unit for agent systems is becoming cost per verified completed task rather than cost per token or model call.
  • Confidence: high.
  • Supported by 5 normalized raw signals.

Source ledger

Publishable sources attached to this record.

5 public sources
#SourceRolePublic status
1cognition.comsourceprimary receiptsource_urls
2databricks.comsourcesupporting receiptsource_urls
3claude.comsourcesupporting receiptsource_urls
4platform.claude.comdocssupporting receiptsource_urls
5engineering.ramp.comsourcesupporting receiptsource_urls

Why token price is incomplete

An agent run accumulates cost through repeated context, tool calls, failed attempts, delegated work, and human verification. A more expensive lead model can lower total cost when it takes fewer turns, delegates earlier, writes a better task contract, and avoids redoing sidekick work.

Supporting evidence

  • Cognition reports that Fable plus the same sidekick cost less per benchmark run than Opus plus sidekick despite a higher token price. The observed difference came from turn count, context use, and delegation behavior.
  • Databricks measures coding-agent outcomes against internal tasks together with time, tokens, and cost rather than relying on a public benchmark score alone.
  • Claude Code exposes effort as a separate runtime control from the model, making cost and persistence tunable per task.
  • Ramp argues for assigning spend to use cases and completed outcomes, including retries and human review.

Operational consequence

Each run should record task identity, route, models, turns, tool calls, elapsed time, retries, review effort, outcome, and failure class. Cost optimization can then target the whole trajectory instead of a single line item.