Picture the meeting. Finance has the monthly AI invoice open, and the line items say how many input and output tokens went to which model. Someone asks what the money was actually spent on, and you have no good answer. That is the sentence Kong opens with in its release, Take Control of the Economics of AI with Kong AI Gateway: enterprises "can see what they're spending on AI, but often can't explain what they're spending it on."
The post is clear about why the bill falls short. As Kong puts it, "businesses don't operate in tokens. They operate in teams, applications, products, programs, customers, cost centers, people, and increasingly agents." A provider invoice speaks the first language. Your budget owners speak the second.
Kong's answer is architectural, and the post says its figures are an illustration, not customer data. The example is an enterprise that spends 500,000 dollars on AI in a month and knows only the split by provider. The gateway sits, in Kong's words, "directly between AI consumers and the models they use." Because of that position, it can see the consumer, application, model, provider, tokens and cost on each request as it happens.
You might assume you could multiply tokens by a rate and be done. Kong says no: "there isn't a universal 'cost per token'." Rates vary by input and output, cached tokens, context-window thresholds and service tiers. So the gateway prices each request individually.
Then it attributes that cost up a chain. The example starts with an agent: Customer Support Agent, then Returns & Refunds Workflow, then North America, then Customer Experience, ending at $27,000. That is a number you could put in front of the person who owns that cost center. Budgets, planning and routing to cheaper models follow from having that attribution.
If you want to see where this lives, the APIs.io catalog holds the surfaces it ships on. The Kong provider page lists 139 API pages. The release lands on the Kong AI Gateway, the agent traffic it attributes passes through the Kong Agent Gateway, and the tools that traffic reaches are registered in the Kong MCP Registry. The agentic access profile maps 1,242 operations, 782 of them acting.
Now the turn, because the catalog holds a record on Kong too, and part of it was filed against our own side. On the Agent Readiness score, error semantics, reversibility, the event surface, agent skills, delegated identity and protected resource metadata are lit. The Kin Score is 71.8, exemplar band, carried by access clarity at 84.2 and contract quality at 67.6. Agent Readiness is 46.9, agent-ready.
Three dimensions are not lit. The MCP server dimension is still unlit, the regression this series reported two weeks ago and filed on the catalog's side. Agentic commerce is unlit, and this release is the closest Kong has come to it: a per-request price attached to an identified agent is the meter that commerce between agents needs.
The third matters most for a ledger like this one. Idempotency is unlit. A retried request that is priced twice is a budget error, and your finance partner will not care that the retry was automatic.
So here is what you take away. Kong has made AI spend attributable to the agent that caused it, which is the thing your next budget meeting needs. But attribution is only as trustworthy as the contract underneath it. Before you lean on those dollar figures, ask whether the same request can only be charged once.
Read the original: https://apis.io/2026/10/19/kong-prices-every-ai-request-and-attributes-it-to-the-agent-that-made-it/