Agentforce Headless MCP Pricing: Flex Credits Status Is TBA

When third-party agents call Salesforce over MCP or API, which Flex Credit line hits our Order Form, and what do we do while the multiplier is still TBA?

Third-party agents already cost inference dollars. Salesforce is adding a second meter for the Salesforce side of those calls. The Order Form line is named. The unit price is not.

What Salesforce publishes

Customer 360 Platform / Headless Platform Interaction (HPI) is the Usage Type. The Flex Credits Rate Card (08.31.2026) lists Category "Customer 360 Platform" and Usage Type "Headless Platform Interaction" with multiplier TBA. Footnote: these usage types apply to Headless 360 usage only, in addition to other Usage Types on the Rate Card. Learn more: sfdc.co/usage_headless (Salesforce Help article 005360285). Flex Credits Rate Card 08.31.2026

Registered agents get Agentic Identity. Agents interacting with Salesforce register on the platform and receive their own credentials and permissions instead of riding a human user identity. Successful MCP or direct API calls by those registered agents in active production count as Headless Platform Interactions and consume Flex Credits once metering is on.

Multiplier unpublished. Not metered today. 30 days notice before billing. Salesforce has not published the Flex Credit multiplier for HPI. Agentic MCP/API usage is not currently metered. Customers get 30 days notice before numerical multiplier / billing starts.

Sandboxes, scratch orgs, and Developer Edition are excluded. Metering applies in active production orgs only. Traditional non-agentic API integrations stay on existing pricing and security arrangements; they are not moved onto the HPI Flex Credit line.

What demand and competitor pages say

Salesforce Ben (Sep 24, 2026) reports Salesforce will charge Flex Credits for agentic MCP and API calls once agents are registered under Agentic Identity, with HPI as the consumption unit, multiplier still unpublished, 30 days notice before metering, production-only, and traditional API left on current pricing. Salesforce Ben

That coverage also surfaces the dual-spend reality buyers already feel: pay the model provider for inference, then expect Salesforce Flex Credits on the Salesforce side when the agent is registered and calling MCP or agentic API in production. It is unpublished unit economics plus two meters, not a Salesforce-tax frame.

Salesforce's Headless Toolkit claim set (via spokesperson in the same Ben piece) lists Traceability and Observability, Security and Governance, Cost Optimization (smart search tools to reduce token consumption), Capability Expansion, and future headless APIs/MCP servers under the same tracking. Vendor claim score /5: Cost Optimization / Headless Toolkit vs TBA unit price + variable agent call volume. The toolkit may reduce tokens. It does not publish the HPI multiplier or cap how many interactions a chatty harness burns.

Confidence block (what is true today)

1. Metered now? No. Agentic MCP/direct API HPI usage is not currently metered.
2. Before a numerical multiplier bills: Salesforce says 30 days notice.
3. Not metered: sandboxes, scratch orgs, Developer Edition.
4. Traditional non-agentic API: stays on existing pricing (not the HPI Flex Credit line).

Decision rule for Director+ teams

1. Name the Order Form line correctly. Ask for Customer 360 Platform / Headless Platform Interaction (HPI) on Usage Details. Do not invent a $/call or a multiplier. Sibling two-meter / wait-or-buy context: Flex Credits buying models
2. Budget dual spend explicitly. Line A: third-party inference $. Line B: Salesforce HPI Flex Credits x TBA. Until B has a number, flag B as unknown unit economics in the forecast, not zero.
3. Treat pre-prod as free for this meter. Build and test MCP/agentic API in sandbox, scratch, or Dev Edition without HPI Flex Credit burn under current rules.
4. Keep traditional integrations labeled. If traffic is non-agentic API under existing integrations, it stays on current pricing. Do not let an AE roll it into HPI without a written reclassification.
5. Register Agentic Identity on purpose. Registration unlocks Headless Toolkit controls and also puts successful production MCP/API calls on the HPI meter once billing starts. Security win and commercial fork in the same step.
6. Use the 30-day notice as runway, not as a reason to ignore Wallet. When notice lands, RevOps updates the Flex Credit forecast; Finance locks the usage type on the Order Form; nobody signs a volume bet without the written multiplier. Sibling audit: Who audits the agent meter and Usage data model vs Digital Wallet
7. Do not confuse HPI with AWU. AWU is not a published Order Form Usage Type. HPI is. Sibling: Are Agentic Work Units billable

Eight-Seat Read (lite): who refuses what until the multiplier is written

1. RevOps: refuses a hard Flex Credit forecast / Wallet alert threshold for agentic MCP volume until HPI multiplier is numeric.
2. Finance / procurement: refuses to treat HPI as a priced usage type on the Order Form until Usage Details shows a multiplier (not TBA).
3. Security / IT: refuses broad production Agentic Identity + OAuth cutover for third-party agents until scope, revoke path, and commercial notice timing are written beside the identity model.
4. CRO: refuses margin models on agent volume that assume Salesforce-side call cost is free or covered in the seat while HPI remains TBA.

Quick compare

1. Headless Platform Interaction (HPI): Customer 360 Platform Usage Type for successful MCP / agentic API by registered agents in production. Multiplier: TBA. On Order Form Usage Details as a named line; not billable at a published rate today.
2. Traditional non-agentic API: existing integrations. Stays on current pricing. Not the HPI Flex Credit line.
3. Sandbox / scratch / Dev Edition agentic calls: excluded from this metering under current rules. Build here while TBA lasts.
4. Third-party inference $: paid to the model / agent host. Separate from Salesforce Flex Credits. Always in the dual-meter model.
5. AWU: platform / disclosure metric, not this Order Form line. See AWU decoder sibling.

Why we might be wrong

1. The HPI multiplier lands low enough that dual spend is noise next to inference.
2. Thirty days notice is enough runway for RevOps and Finance to reforecast before any bill.
3. Traditional API stays cleanly out of HPI in practice, not only on the slide.
4. Pre-prod (sandbox / scratch / Dev Edition) remains free for this meter through your build window.

Sources

1. Salesforce Ben, Salesforce Will Charge Flex Credits for Agentic MCP and API Calls (Sep 24, 2026): Salesforce Ben
2. Flex Credits Rate Card (08.31.2026), Customer 360 Platform / Headless Platform Interaction = TBA: Rate card PDF
3. Salesforce Help / Headless usage (005360285) via sfdc.co/usage_headless

Soft CTA

If you want the next Agentforce decoder and the weekly receipts before the AE call, subscribe