Ask three people what Agentforce costs and you'll get three different numbers, all of them technically published by Salesforce at some point. That's not because anyone is lying to you. It's because the pricing model has changed shape more than once since launch, and most of the articles ranking for "Agentforce pricing" were written under a model that no longer matches what your account executive will quote.
This post does two things. First, it explains the current pricing model in plain English so you can walk into a renewal conversation without getting steamrolled. Second, it makes an argument most Salesforce partners won't make: a meaningful share of the "we want AI in Salesforce" demand doesn't need Agentforce at all. It needs an assistant connected to your org — and that's a problem you can now solve with MCP for a fraction of the spend.
Why Agentforce pricing confuses buyers
Three reasons, and none of them are your fault.
The unit of pricing has moved. Agentforce launched with per-conversation pricing — a flat rate every time an agent held a session with a customer. Salesforce then shifted to a usage model built on Flex Credits, where you're billed per action an agent takes rather than per conversation. Both models still show up in articles, decks, and even in contracts signed at different times, so buyers end up comparing numbers that measure different things.
Usage pricing is culturally new for Salesforce buyers. Most Salesforce budgeting is per-seat: predictable, annual, easy to model. Consumption pricing asks you to forecast something you've never measured — how many discrete actions an AI agent will take on your behalf in a year. Nobody knows that number before they deploy, which makes procurement uncomfortable and makes pilots politically harder than they should be.
The add-on tiers blur the picture further. Alongside credits, Salesforce sells per-user editions that bundle Agentforce into Sales and Service Cloud at a premium seat price, plus a limited-usage tier included with some editions. So the honest answer to "what does Agentforce cost?" is: it depends on which of three doors you walk through, and the doors are not clearly labeled.
The pricing model in plain English
Here's the current shape of it, stripped of branding. One caveat up front: everything below is list or commonly reported pricing. Salesforce negotiates, bundles, and revises constantly — treat these numbers as a starting point for the conversation with your AE, not a quote.
- Flex Credits (the usage meter). Agents consume credits every time they take an action — retrieving records, invoking a Flow, calling Apex, executing a step in a topic. The commonly cited figure works out to roughly $0.10 per action, with credits sold in prepaid packs. A single customer conversation usually involves multiple actions, so the old per-conversation number and the new per-action number are not comparable one-to-one.
- Per-user editions (the enterprise bundle). The premium Sales and Service editions fold Agentforce into a higher-priced seat, with usage allowances attached. If your org is already at the top of the edition ladder, some agent capacity may effectively be in the bundle you're paying for.
- Included tiers (the on-ramp). Some editions include a limited amount of agent usage at no extra line item — enough to experiment, not enough to run production volume.
The practical consequence: your real cost is driven by agent design, not by the rate card. An agent that takes six actions to resolve what could be done in three costs you double, forever. This is why two companies with identical volume can have wildly different Agentforce bills.
What you actually get for it
To be fair to the product, the money buys real things — things that matter a great deal at enterprise scale.
- Native platform agents. Agents run inside Salesforce, reason over your objects, and execute your existing Flows and Apex. No middleware, no sync jobs, no second copy of your data.
- Governance and trust tooling. The Trust Layer, audit trails, topic and guardrail configuration, and testing tools exist so a security team can say yes with a straight face.
- Salesforce-managed operations. Model hosting, scaling, and uptime are Salesforce's problem, under the same contract and compliance posture you already have. For regulated buyers, one accountable vendor is worth real money.
When Agentforce is worth it
Three scenarios where the math genuinely works:
1. Autonomous, customer-facing service at volume. If you're deflecting thousands of cases or chats a month, compare per-action cost against your fully loaded cost per human-handled case. At real volume, even a modest deflection rate pays for a lot of credits — and this is the workload Agentforce was actually built for.
2. You're already deep in the platform. If your business logic lives in Flows and Apex and your data strategy runs through Data Cloud, agents that natively execute that logic under your sharing model beat anything you'd bolt on from outside. The marginal integration cost is near zero.
3. Procurement needs one accountable vendor. In regulated industries, the security review, the contractual posture, and the single throat to choke are the product. If that's your world, the premium is rational.
When a lighter path wins
Here's the part that gets skipped in most partner content: a large share of "we want AI in Salesforce" is not an autonomous-agent problem. It's an assistant problem. Reps who want to ask questions about pipeline in plain English. Ops people who want records updated, reports investigated, and data quality checked without clicking through fifteen screens. Admins who want to query, describe, and debug conversationally. There's a human in the loop for all of it.
That workload doesn't need a metered autonomous agent. It needs your existing AI assistant — Claude or ChatGPT — connected to your org with proper permissions. That's exactly what the Model Context Protocol does, and in 2026 you have two credible ways to get it.
Salesforce's hosted MCP server is included with supported editions and connects AI clients to your org under your existing security model. If your edition qualifies and your use case is simple, start there — it's already in your contract.
ApexGenius is our purpose-built Salesforce MCP for Claude and ChatGPT. It uses a flat product subscription rather than an ApexGenius fee for each tool call; current product pricinglives on the product site. That flat model is the point: when humans drive the usage, volume is human-scale, and nobody should be doing credit math to decide whether a rep is allowed to ask a question. It goes deeper than assistant chat, too — SOQL, schema exploration, record operations, and metadata deploys — which is why admins and developers are the heaviest users.
The dividing line is simple: metered pricing exists because autonomous agents act at machine scale. If a person triggers every action, you don't have a machine-scale problem, and you shouldn't pay machine-scale infrastructure prices to solve it.
An honest decision framework
| Your situation | Reasonable starting point | Why |
|---|---|---|
| High-volume autonomous case or chat deflection | Agentforce | Per-action economics beat cost-per-case at volume; native guardrails matter for customer-facing work |
| Sales, ops, or CS team wants an assistant in Claude/ChatGPT | MCP — hosted or ApexGenius | Human-in-the-loop usage; flat cost; live in days, not quarters |
| Admin/developer productivity — queries, debugging, deploys | ApexGenius | It's a tooling workload, not an agent workload; metering it makes no sense |
| Already paying for a premium per-user edition | Use the Agentforce you have | Capacity is in the bundle; your marginal cost is credits, not a new platform |
| Need to prove value before budget exists | MCP first, agents later | A packaged, flat subscription can make a small pilot easier to approve; what you learn scopes the agent build properly |
| Regulated industry, formal vendor accountability required | Agentforce, with a real security review | Trust Layer, audit posture, and contract terms are the product |
Notice these aren't mutually exclusive. The most sensible pattern we see in 2026 is both: MCP for the humans, Agentforce for the autonomous volume — each priced the way its usage actually behaves.
The real cost is implementation judgment
Whichever door you pick, the rate card is not where Agentforce projects go wrong. They go wrong when an agent ships with no owner, no test plan, vague topics, and no measurement — burning credits on actions nobody designed and deflecting nothing. And assistant rollouts go wrong the same way: connected with sysadmin permissions, no scoping, no guardrails. The expensive part of AI in Salesforce has always been judgment, not licensing.
So scope narrowly, measure honestly, and expand what works. If you're weighing an Agentforce build, our Agentforce consulting practice will tell you plainly if you don't need it yet. And if the assistant path fits, start with Claude + Salesforce — it's the fastest honest answer to "what would AI actually do for us?"