September 26, 2026. On September 17 Salesforce published a Help article, Understand AIforce Impact, that changes the economics of connecting any AI agent to a Salesforce org. Targeting November, agents that talk to Salesforce over the Model Context Protocol or the API will have to be registered with their own Agentic Identity, and once registered, "every successful call a registered agent makes to Salesforce, whether it arrives over Model Context Protocol (MCP) or direct API, is metered as a Headless Platform Interaction (HPI)" that consumes Flex Credits. The rate is listed as "TBA" and metering is off until Salesforce gives 30 days' notice. For a small insurance agency or lender that connected Claude, ChatGPT or a custom calling agent to its CRM this year, the consequence is simple: the day the number is published, every read and write that agent makes has a price. Salesforce Ben reported the change on September 24.
What Salesforce published
- Registration first. Admins register each agent directly on the platform, which "carves out a discrete identity for each agent instead of letting it operate under the identity of the person it assists," with a narrower permission set than a human user.
- Then billing. A registered agent's usage is tracked in Digital Wallet under a new usage type in the Customer 360 Platform category of the Flex Credits Rate Card. Every successful MCP or direct API call is one Headless Platform Interaction.
- No rate yet. The multiplier "hasn't been announced yet, so it is currently listed as TBA and agentic usage isn't metered." Salesforce will give 30 days' notice before metering begins.
- Who must register, and when. Customers buying on or after September 17 must register all agents that use Salesforce APIs within three months of notice that Agentic Identity is available; existing customers register and migrate at renewal; any use of a Salesforce MCP server requires registration within three months of notice, for all customers.
- Production only. Sandboxes, scratch orgs and Developer Edition orgs do not incur HPI metering, so building and testing stays free of the meter.
- Traditional integrations are untouched. "The pricing and security options for traditional integrations stay exactly as they are today." The model is aimed at agentic traffic only.
- The prerequisites. Flex Credit billing needs Salesforce Foundations, "currently available at $0"; then register the agent, point MCP clients and API agents at the registered agent's OAuth credentials, and reconnect.
- What a credit costs today. Salesforce's Agentforce pricing page sells Flex Credits at $500 per 100,000, half a cent each; its worked examples price a standard action at 20 credits (10 cents), an order-status request at 40, a support case at 60, an appointment booking at 100 and a voice reservation call at 120 credits, or 60 cents.
What it means for operators
The number you can act on before the rate lands is the call count. An intake agent that looks up a contact, checks open cases, writes a call note and updates a stage field makes four calls per conversation; a nightly enrichment agent touching 5,000 records makes at least 5,000. Count those now, per task, and you can price the meter the afternoon the multiplier is published. Salesforce has not said how composite or bulk requests are counted; ask your account executive in writing.
Architecture matters more than it did. Agents that re-read the same account on every turn will pay twice for what a cached read achieves. The pattern that survives a metered CRM is the same one that survives a metered model: gather once, decide, write once. For an AI calling agent for insurance agencies, where every completed call ends in a CRM write, that write is now a line item to be designed, not an afterthought.
One part is good news. Agentic Identity gives each agent scoped permissions and a full audit trail, and nothing is billed until the rate exists and the notice period has run. Teams building with a dedicated AI engineer should use the window to instrument call counts and keep bulk data movement on the traditional integration credentials Salesforce says are not changing. See also what HubSpot charges per agent action in credits.
Frequently Asked Questions
It is Salesforce's new billable unit for agentic access, defined in the September 17, 2026 Help article Understand AIforce Impact. Every successful call a registered AI agent makes to Salesforce, over MCP or the direct API, is metered as one Headless Platform Interaction and consumes Flex Credits from the org's Digital Wallet.
Salesforce has not published the multiplier; the rate card lists the usage type as TBA and no agentic usage is metered yet. Salesforce says it will give 30 days' notice before metering begins. Flex Credits themselves cost $500 per 100,000, half a cent each, and Salesforce's own examples price a standard Agentforce action at 20 credits.
Yes, on a schedule. Customers who purchase on or after September 17, 2026 must register all agents that use Salesforce APIs within three months of notice that Agentic Identity is available; existing customers must register and migrate at renewal; and any use of a Salesforce MCP server requires registration within three months of notice for all customers.
No. Salesforce says Flex Credits are only consumed for Headless Platform Interactions in active production orgs. Sandboxes, scratch orgs and Developer Edition orgs do not incur HPI metering, so building and testing agents does not draw down credits.