Procurement teams budgeting for agentic rollouts are facing a specific, uncomfortable reality: the meter is going in, but the price is still a blank space. Salesforce has told customers it will soon charge for every call an agent makes to its platform, and for anyone trying to forecast what that costs, the newest row on the company’s rate card – the one that will meter external agent calls – reads “TBA.”
In a document published September 17, 2026, Salesforce set a November target for a new billing model under its Headless Toolkit. The mechanic is plain: every successful call a registered agent makes to Salesforce, whether it arrives over Model Context Protocol (MCP) or a direct API, is metered as one Headless Platform Interaction (HPI) and tracked through the company’s Digital Wallet.
Worth stating plainly: agentic usage is not metered today. The multipliers for this usage type have not been announced, and Salesforce says it will give 30 days’ notice when a numerical multiplier is added and metering begins. Traditional, non-agentic integration pricing stays exactly as it is – the model targets agentic traffic only, which is exactly why the registration step is the part to watch.
Registration is where the clocks start. Customers who purchase on or after September 17, 2026 must register all agents that use Salesforce APIs within three months’ notice from Salesforce that Agentic Identity is available; existing customers running agents on APIs register and migrate at renewal; and any use of a Salesforce MCP server requires registration within that same three-month notice window, for all customers. Each registered agent gets its own Platform identity with a narrower permission set – Salesforce’s own framing is issuing the agent its own badge rather than lending it an employee badge. The deadlines attach to a notice nobody has received yet.
When metering goes live, the cost lands in production first. Sandboxes, scratch orgs, and Developer Edition orgs incur no HPI metering, so teams can build and test without drawing down Flex Credits. The first bill arrives when those agents move into active production.
We tried to read the per-call number directly: the HPI usage-type row did not render on the Salesforce rate card when we fetched it, so the figure comes from the “TBA” status in Salesforce’s help documentation, not from a published price. That gap is named rather than smoothed.
The November change also lands on top of what our price-card audit found this week. In our published-price-card audit, four of the eight tracked enterprise agent platforms published no public enterprise-agent price at all – and Salesforce still carries the fullest card in the group, Flex Credits at $500 per 100,000 credits. The base rate is a real number; the multiplier that converts each HPI into credits is not. This is adjacent to, not the same as, the authorization question we published today: that piece argues who permits an agent to move money is the chargeable surface, while Salesforce’s Agentic Identity registration is a concrete case where registration gates metering itself.
So buyers are being asked to register agents now, at a price that has not been published. The Information reported on these registration and metering plans at month-level October – paywalled and blocked to our fetch, so it is named here rather than linked, with no day peg. What a procurement team can do today is inventory which of its integrations are agentic, register on the clocks above, and hold the only firm number available: the Flex Credit base rate. The cost of the calls themselves is still a blank space with a November target above it.