What does an AI agent cost?
There is no single number, and any guide that gives you one is selling something. What there is, reliably, is a structure: build or license, run, and spend. The first two are quotable because a vendor or a contractor owns them. Licensed platforms bill on the models in the table below, custom agents bill on tokens and infrastructure, and a build project bills on engineering time. Those numbers vary by an order of magnitude across the market, which is why published ranges are close to useless for planning: a support deflection bot and a multi-agent procurement system are not the same purchase. What travels across every deployment is the shape of the bill, and the fact that the shape has three parts while most budget spreadsheets have two.
The three lines in an AI agent budget
Build or license is what you pay to have the agent exist: a platform subscription, a development project, or both when you license a framework and build on top of it. It is usually a one-time or annual number and it is the one everybody remembers. Run is what you pay for the agent to do work: model tokens, hosting, vector storage, observability, and the vendor's own metering, whether that is per action, per conversation or per outcome. It is variable, it scales with usage, and it is where most first-year overruns show up. Spend is what the agent pays out to third parties while doing its job. A procurement agent buys supplies. A travel agent books flights. An ad agent places media. A research agent calls metered APIs. That money leaves your account through a payment credential you issued, not through a vendor invoice, so it usually lands in a completely different part of the general ledger from the first two lines. Teams routinely discover it at month end.
AI agent pricing models and how vendors actually bill
Six models cover almost the entire market in 2026, and the industry has been drifting steadily from seats toward consumption. The useful research here is the Poyar State of B2B SaaS and AI Monetization survey of more than 230 companies, run in April and May 2026, which found hybrid pricing rising from 25% to 37% over twelve months. Worth flagging because the number gets misquoted constantly: a widely repeated "43% to 61%" figure does not appear in that research. The practical consequence of the drift is that your AI agent cost is increasingly a function of how much the agent works rather than how many people are on the account, which is better value when volume is low and considerably worse when an agent gets stuck in a retry loop. Read the models below for what each one does to your budget when things go wrong, not just when they go right.
What published AI agent pricing actually says
Most vendors in this category do not publish a rate card, so the honest table is short. Salesforce and Intercom do publish, and their numbers are worth knowing because they anchor the two dominant consumption models: per action and per outcome. Everything else in the market tends to be quoted per deployment. When a comparison article gives you precise pricing for a vendor that publishes none, that pricing was estimated, and you should treat it as such. We have deliberately left estimates out of the table below and marked the gaps as gaps. Verify anything here against your own order form before you build a budget on it, because rate cards in this category are moving quickly.
Building an AI agent cost per month you can defend
Work the three lines separately and resist the urge to produce one figure. For license, take the annual contract and divide. For run, estimate the unit of work the vendor meters, multiply by expected monthly volume, then multiply again by a retry factor, because agents fail and re-attempt in ways deterministic software does not. If your vendor meters actions, remember a single user request can be many actions: a plan, several tool calls, a summary. For spend, do not estimate at all. Set it. The agent's outbound spend is the only line of the three you can fix in advance by policy, so make it a decision rather than a forecast: this agent may spend up to this amount, at these merchants, this month. That converts your most volatile line into your most predictable one, which is the opposite of how most teams treat it.
Why are AI agents more expensive than the sticker price?
Three reasons, in rising order of how much damage they do. First, the unit is smaller than you think: per-action and per-token billing meter the agent's internal reasoning, not the user's request, so a single question can bill as a dozen events. Second, failure is billable. A retry, a bad plan and a tool call that returns nothing all cost the same as work that succeeded, and agents retry far more than traditional software. Third, and largest, the outbound spend is not in the comparison at all. A team that agonizes over a $0.10 per action rate will hand the same agent a payment credential with no ceiling on it, and the second decision is worth orders of magnitude more than the first. If an agent runs ten thousand actions in a month, that is a thousand dollars of platform cost. If the same agent makes one bad purchasing decision at scale, it can be more than the entire platform contract.
The third line is what your agent spends on your behalf
This is the part of AI agent cost that no pricing page covers, and it is structurally different from the other two. Your platform bill has a natural ceiling, because you signed a contract and the vendor cannot bill you for work you did not ask for. Your token bill has a soft ceiling, because rate limits and context windows bound it. Your agent's purchasing has no ceiling by default. It is bounded only by the credential you gave it and whatever the merchant will authorize. This matters more every quarter because the industry is actively removing the last human checkpoint: agentic checkout is designed to complete a purchase without anyone reading the total, and neither the ACP nor the UCP protocol carries a buyer budget. Scoped payment tokens cap one transaction, not a cumulative total, so an agent can place forty individually sensible orders that add up to a number nobody would have approved. The checkout screen used to be an informal budget control. It is being deleted on purpose.
How to cap the third line before it becomes the whole budget
Outbound spend has to be controlled at the payment instrument rather than in the prompt, because a prompt is a request and an authorization decline is an answer. In practice that means four controls. A funded wallet with a hard cap, so your worst case is a number you chose in advance rather than one you discover. A merchant and category allowlist, so an agent that finds a cheaper unapproved supplier simply fails the authorization instead of succeeding at the wrong thing. An approval threshold, above which the payment pauses and a named person gets a one-tap approve or deny, which puts a human back exactly where the money justifies the latency and nowhere else. And an audit trail that ties every authorization to the agent, its human owner, the task and the policy verdict, because reconciling agent spend after the fact is genuinely hard when there was no browser session and no expense report. That is what AgentsPay does across card rails and stablecoins from one control plane. You can see the surfaces on agent spend controls, human approvals and the agent audit trail, and the console at the top of this page runs the same policy engine.
Are AI agents worth it?
Often, but the comparison most teams run is the wrong one. Measuring platform cost against a salary flatters the agent, because the salary is fully loaded and the agent cost is not. A fair comparison puts all three lines against the human total, including the purchases a person would have made anyway, and then adds the cost of the controls and review the agent needs and the person did not. Agents win decisively on volume, on tasks that are tedious and countable, and on work that has to happen at three in the morning. They win less clearly on judgment-heavy work with expensive failure modes, which is precisely the category where uncapped outbound spend does damage. We work through that comparison properly in AI agent cost vs salary. If you are on the other side of this question and trying to price an agent you built rather than budget for one you bought, AI agent monetization covers that, and what agent payment infrastructure costs covers the rail fees specifically.