Do Agentforce Token Counts Equal Flex Credit Bills?

Salesforce published "Close the Agentforce Usage Visibility Gap With the AI Usage Data Model" on August 18, 2026. It gives RevOps something the Digital Wallet screen does not: queryable, near-real-time usage records you can join to your own objects. It also states plainly that those records are token counts, not Flex Credits. Source: salesforce.com/blog/agentforce-usage-data-model.

That distinction is the whole page. Teams are already building burn dashboards on the data model and treating the output as the bill. It is not the bill. Salesforce names Digital Wallet as the single source of truth for exact Flex Credit consumption, billing verification, and contractual overage calculations. Same URL.

This is a Proof Gap problem: the fast number and the billable number are different numbers, and the fast one is the one on the screen every morning.

01. What the AI Usage Data Model actually stores

Salesforce's post describes the AiAgentGenerativeAiUsage DMO as the record of generative AI usage, available for query and joins in Data Cloud, with near-real-time visibility rather than the delayed, aggregated view operators were working from. Source: salesforce.com/blog/agentforce-usage-data-model.

• Token counts per generative AI usage record, queryable rather than screenshot-only.
• Joinable to your own data, which is what makes per-team and per-use-case attribution possible at all.
• Near real time, so you see divergence in days rather than at invoice.

That is a real gain. Digital Wallet reports at the org level, which is why business unit chargeback has needed a manual model: BU chargeback.

02. Tokens are not credits

Salesforce's language is explicit: the DMO provides token counts, not Flex Credits directly, and token-to-credit conversion is a close approximation appropriate for trend analysis. Close approximation is not billing. Same URL.

Operating consequence: a token dashboard is directionally right and contractually wrong. If you use it in an overage dispute, the vendor will point at Digital Wallet, and Digital Wallet will be the number that stands.

03. Flat-rate actions versus prompt token blocks

The same post separates two metering behaviors, and this is where token dashboards drift from the invoice most.

1. Standard Agentforce actions bill flat. A standard action is 20 Flex Credits regardless of how many tokens the model consumed. Sources: Salesforce usage data model post and salesforce.com/agentforce/pricing.
2. Prompt-template invocations use a token-block formula: CEIL(tokens / 2000) multiplied by the model tier rate. Source: Salesforce usage data model post.

So a chatty action and a terse action cost the same 20 credits, while two prompt invocations with the same intent can land in different token blocks. Averaging tokens across both and converting once produces a number that is wrong in both directions at the same time.

Rate card multipliers for the action lines sit in the published rate card: Flex Credits Rate Card 08.31.2026. Voice is listed at 30 Flex Credits on the pricing page: salesforce.com/agentforce/pricing.

04. What Digital Wallet is for

Digital Wallet is Salesforce's consumption monitoring surface for credit balances and burn: salesforce.com/agentforce/digital-wallet. The usage data model post names it as the source of truth for exact Flex Credit consumption, billing verification, and contractual overage calculations.

Practically, three jobs belong to Digital Wallet and nowhere else: the monthly consumption number Finance books, the verification pass before an invoice or true-up conversation, and the overage calculation in any contractual dispute. The dashboard supports the argument. The Wallet is the argument.

Forecasting mechanics when overages bill in arrears: Forecast and close.

05. Threshold alerts do not stop spend

Salesforce describes threshold alerts at 75, 90, and 100 percent, and states Digital Wallet does not block usage when credits run out. Source: salesforce.com/blog/agentforce-usage-data-model.

An alert is a notification, not a kill switch. Someone has to decide and act. That gap is the whole argument of Digital Wallet has no kill switch, and it is why the alert owner needs a named runbook rather than an inbox rule.

06. The RevOps checklist

1. Build the AI Usage Data Model dashboard for trend, per-team attribution, and anomaly detection. Label it directional on the dashboard itself.
2. Run a monthly reconciliation of dashboard-converted credits against Digital Wallet. Log the variance percentage as a tracked metric, not a footnote.
3. Model prompt-template usage with the CEIL(tokens / 2000) block formula separately from flat-rate actions. Do not blend them into one conversion.
4. Confirm which SKU you are actually on before any of this means anything: SKU decoder.
5. Name the alert owner for 75, 90, and 100 percent, and write what they do at each threshold, since nothing stops automatically.
6. Keep one independent count of agent activity so you are not auditing the vendor with the vendor's own meter: Who audits the agent meter.

What this page is not

• Not a claim that the AI Usage Data Model is inaccurate. Salesforce calls the conversion a close approximation for trend analysis, and that is how we treat it.
• Not a price list. List figures here come from the pricing page and the published rate card. Your Order Form wins.
• Not the buying-model worksheet or the breakeven model. Those live in the sibling decoders.

More on the meter set: Digital Wallet · Forecast and close · BU chargeback · Who audits the agent meter · SKU decoder · AI pricing and contracts

Every Reality Check lands in the weekly issue. Subscribe at therevenueaireport.com/subscribe.