Understand AIforce Impact

AIforce, originally announced at TDX 2026 as “Headless 360,” decouples the Salesforce platform from the browser, allowing agents to build, act, and deliver on any surface. While AIforce is the concept of bringing all your Salesforce context to the interface where you work, Headless Toolkit provides the functionality to make it a reality. With AIforce and Headless Toolkit functionality, there will be new license and billing considerations, and customers will be required to register agents that interact with Salesforce.

What’s Changing

Targeting November, Salesforce will be releasing a new set of security controls, agentic registration, and a new billing model as part of the Headless Toolkit. The two are connected: the same registration step that gives an external agent its own identity on the Platform is what makes that agent's activity visible, governable, and billable.

Agent Registration

Under these controls, Salesforce admins register agents directly on the Platform. Registration carves out a discrete identity for each agent instead of letting it operate under the identity of the person it assists. Additionally, admins can grant a narrower, reduced permission set to the agentic identity, over that of a human user. Think of it as issuing the agent its own badge, rather than lending it an employee badge.

Agent Billing 

Once an agent is registered, usage can be tracked in Digital Wallet and Flex Credits will be consumed. A new usage type has been added to the Customer 360 Platform category of the Flex Credits Rate Card. This usage type tracks calls that registered agents make to the Salesforce platform via AIforce and Headless Toolkit functionality. 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) and tracked through Digital Wallet. 

The multipliers for this usage type haven't been announced yet, so it is currently listed as “TBA” and agentic usage isn’t metered. Salesforce will provide 30 days’ notice when a numerical multiplier is added and metering begins. Refer to the Rate Card for the Flex Credit cost of a single Headless Platform Interaction. 

Customer Impact

Customers that purchase on or after the date of this publication, will be required to register all  agents that use Salesforce APIs within three (3) months’ of notice from Salesforce that Agentic Identity is available.  Existing customers using agents with APIs will be required to register all agents and migrate their connections to this new billing model upon renewal. Use of any Salesforce MCP server requires agent registration within three months’ notice from Salesforce. This is for all customers.  

Once an agent is registered, and the Flex Credit rate card is updated with numerical values, Flex Credits will only be consumed for HPIs occurring in active production orgs. Sandboxes, scratch orgs, and Developer Edition orgs don’t incur HPI metering through Digital Wallet, so admins and developers can build and test without drawing down Flex Credits. Credits seeded into the org cover deploying solutions to production and running tests in that environment.

The pricing and security options for traditional integrations stay exactly as they are today. This model addresses agentic traffic specifically and is intended to leave the rest of your integration footprint intact. For more information on how this might impact your account, contact your account executive.