Agentforce Pricing Explained: Credits, Licenses, and Total Cost

Almost every confused Agentforce pricing conversation comes from the same place: two people comparing numbers that describe different things. One is quoting an edition upgrade. The other is quoting a consumption meter. A third is quoting what the pilot cost before the meter turned on.

This page does not publish a price. Salesforce pricing for this product line has moved repeatedly, and an article that quotes a figure from last quarter is a liability rather than a resource. What this page does is show you the structure, so you can work out which number you are looking at and which question you still need answered.

The four lines that make up the cost

1. Edition and licenses. What your org already runs, and what the Agentforce capability requires it to run. An edition move is a separate commercial event from anything agent-specific.
2. Entitlement. What the purchase includes before any meter runs: which agent capabilities are switched on, and any allowance bundled with them.
3. Usage meter. The consumption line. This is where Flex Credits, conversation-based billing, and action-level metering sit, and it is the line that behaves least like a subscription.
4. Platform and data. Storage, Data Cloud consumption, integration work, and the internal hours to keep the whole thing running.

A quote that covers one of these is not wrong. It is incomplete, and the gap only becomes visible on an invoice.

Purchased units, included allowances, and the meter

Three things get conflated constantly. Purchased units are what you bought up front. An included allowance is what came with an edition or entitlement without a separate line item. The meter is what actually decrements as the product runs.

The questions that matter are mechanical. Which actions decrement the meter, and which do not? Does an allowance reset, roll over, or expire? Who else in the org draws from the same balance? What happens at zero: does work stop, or does it keep running and bill in arrears?

The decoder issues linked below work through those mechanics for specific parts of the product, including how the wallet behaves, what happens when Data 360 draws on the same balance, and how a pay-as-you-go arrangement differs from a pre-commitment.

Read the invoice before you model the business case

The usable discipline is to model the invoice, not the licence. Take the workflows you actually intend to run, estimate their monthly volume, and ask Salesforce in writing what each of them consumes. If the answer is an estimate, treat your model as an estimate too, and put a review date on it.

Then ask who owns that meter internally. Consumption pricing fails in revenue organizations for an organizational reason more often than a technical one: nobody sees the running total until finance does.

Which product are you actually evaluating?

Before any pricing conversation, pin down five things: the product name as it appears on the order form, the edition it requires, the entitlement attached, the meter that governs usage, and whether the capability is generally available or still in a pilot or beta program. A capability in pilot or beta may carry no published list price, and it can still consume the meter: Salesforce's own rate card states that pilot feature use may consume Flex Credits where the pilot terms say so. Ask for both the price basis and the consumption basis in writing, because treating a pilot arrangement as a price is how budgets get set wrong.

A procurement checklist

• Which exact SKU and edition does this quote cover, in writing?
• Which actions consume the meter, at what rate, and which are excluded?
• What is included in the entitlement before the meter runs?
• Does the allowance roll over, reset, or expire, and on what date?
• Which other products or teams draw on the same balance?
• What happens when the balance reaches zero: hard stop, soft stop, or overage billing?
• What is the overage rate, and is it capped?
• Which parts are generally available today, and which are pilot or beta?
• What does sandbox or non-production usage consume?
• What are the exit terms, and what happens to configuration and logs?

What Salesforce documents publicly, verified September 19, 2026

Everything in this section was read on the dates given from Salesforce's own pages. Rates and availability change, so treat the verification date as part of the fact.

• Three commercial models. Salesforce documents consumption pricing through Flex Credits or Conversations, alongside per-user licensing (Agentforce pricing, Salesforce, read September 19, 2026).
• Flex Credits list rate. The pricing page lists Flex Credits at $500 USD per 100,000 credits, and Conversations priced per conversation, with prices shown per currency and region (Agentforce pricing, Salesforce, read September 19, 2026). Regional pages show different currency lines, so confirm the currency your order form uses.
• Buying models. Pre-purchase is paid upfront and draws down. Pre-commit is a baseline commitment billed monthly in arrears with a true-up at term end if usage falls below the commitment. Pay-as-you-go has no commitment and bills monthly in arrears at list price (Flexible buying models, Salesforce, read September 19, 2026).
• What the meter counts. The published Flex Credits rate card sets multipliers per usage type: standard and custom Agentforce actions at 20 in production and 16 in a sandbox, voice actions at 30 and 24, prompt tiers from 2 to 16, Help Agent resolutions at 400, and Leads Worked at 400 and 320 (Flex Credits Rate Card, August 31, 2026, Salesforce, read September 19, 2026). The card states that rates may be updated from time to time, so read the version dated closest to your signature.
• Allowances do not roll over. The same rate card states that included Flex Credits must be used before the order end date shown on the order form, with no rollover permitted, and that the sandbox multiplier covers pre-production environments including scratch orgs (Flex Credits Rate Card, August 31, 2026, Salesforce, read September 19, 2026).
• Pilot features can consume credits. The rate card states that use of pilot features may consume Flex Credits where the pilot terms say so (Flex Credits Rate Card, August 31, 2026, Salesforce, read September 19, 2026). A beta or pilot arrangement is therefore not automatically free of metered usage.
• Consumption mechanics. Salesforce Help documents when Flex Credits are consumed for Agentforce, Service, and Speech Foundations (Agentforce and Generative AI Usage and Billing, Salesforce Help). Salesforce also publishes its own Flex Credit estimator (Agentforce pricing calculator, Salesforce).

What Salesforce does not publish per SKU is what your deployment will actually consume. Multipliers are public. Your volumes are not, and that is the half of the equation that decides the invoice.

Where the detail lives

Each of the following issues works through one mechanic in full, with the primary Salesforce source cited on the page. Read the one that matches your open question rather than all of them.

• Which SKU is billing you: Flex Credits or Einstein Requests
• How Flex Credits behave through a forecast and close cycle
• The Digital Wallet and the missing kill switch
• Pay as you go, pre-commit, or pre-purchase
• AELA and how it sits against Flex Credits
• The usage data model against the Digital Wallet
• When Flex Credits are shared with Data 360
• Coworker seats against Flex Credits
• Core, Advanced, and Max editions

Verify any figure against current Salesforce documentation before you put it in a business case. Pricing pages for this product line change, and no article on this site, including this one, is a substitute for the order form in front of you.