Salesforce will bill every agent call in Flex Credits: what to measure before the first invoice

What Salesforce announced

In a help article published on 17 September 2026 ("Understand AIforce Impact"), Salesforce introduced a new usage type: the Headless Platform Interaction, or HPI. Every successful call made by a registered AI agent to Salesforce, whether through an MCP server or directly through the API, will count as one HPI and consume Flex Credits, Salesforce's consumption currency. Usage will be tracked in the Digital Wallet.

What is known so far, according to Salesforce's published material:

• Who is counted. External agents, Claude, Copilot, in-house tools or others, once they are registered on the platform with their own identity. Registration is the same step that gives an agent its own credentials and permissions.
• The price. The multiplier is listed as TBA on the Flex Credits rate card. No cost per call can be calculated yet.
• When. Metering starts only after the multiplier is published, with 30 days' notice. Salesforce is targeting November for agent registration, the related security controls and the new billing model.
• Registration deadlines. Customers using a Salesforce MCP server will have three months to register their agents after Salesforce announces that Agentic Identity is available. Existing customers with API-based agents register at renewal.
• What is excluded. Sandboxes, scratch orgs and Developer Edition orgs are not metered. Traditional, non-agentic integrations keep their current pricing.

Why it matters

For a Salesforce customer, a new line is coming to the bill, with a unit price nobody knows yet, and it applies to any agent that talks to Salesforce, not only to Agentforce. Partners have voiced concerns: on 21 October, Salesforce Ben reported that Salesforce had opened discussions with several of them, led by architect and ISV founder Amnon Kruvi, about cost and predictability. No official Salesforce statement on changes has been published.

The grey zone is the classification itself. Salesforce distinguishes "agentic" traffic from traditional integrations, but published material does not settle every case, for example a middleware flow triggered by an agent. Those cases are worth clarifying with your account executive, in writing, before the count starts.

What to do this month

1. Inventory every agent and integration that calls Salesforce through MCP or the API, and flag the ones likely to be classified as agentic.
2. Measure their daily volume of successful calls now, per agent. Without this baseline, the first invoice will be a surprise.
3. Look for loops and retries. An agent that repeats calls after an error costs nothing today. Once calls are metered, it can multiply the bill.
4. Check the Digital Wallet and who in your company receives Salesforce's 30-day notice.
5. Set a ceiling and an alert per agent, as you would for cloud consumption.

This is typical work for a senior Salesforce architect: mapping agent traffic, reducing unnecessary calls, and redesigning integrations so they stay out of the meter when they do not need to be in it. The number of calls also becomes an indicator to follow over time, alongside costs and reliability.

The danger	The advice
You will discover the volume of your agents' calls on the first invoice.	Count successful MCP and API calls per agent from now on, before metering starts.
An agent that retries in a loop costs nothing today and could multiply the bill tomorrow.	Track errors and retries per agent, and set a ceiling with an alert.
Nobody knows which integrations Salesforce will classify as agentic.	List borderline cases and get Salesforce's answer in writing before the 30-day notice.