Salesforce plans to make outside AI agents register in November and bill their calls in Flex Credits, price unpublished

Salesforce wants every outside AI agent that touches its platform to have its own registered identity. It also plans to charge for the traffic.

The company's help article "Understand AIforce Impact," published September 17, 2026, says: "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 word is "targeting." Salesforce has given no exact launch date.

What changes for agents

Today, Salesforce's hosted MCP servers run an agent as the person it is helping. When those servers became generally available on April 29, 2026, Salesforce said every transaction "runs as the authenticated user, without anonymous service accounts or a new security model to learn."

The new model reverses that. Per the help article, "Registration carves out a discrete identity for each agent instead of letting it operate under the identity of the person it assists." Admins can give each registered agent a narrower set of permissions than a human user typically gets.

Salesforce says the registration step makes agent activity "visible, governable, and billable." The third word is the one customers are focused on.

MCP, the Model Context Protocol, is an open-source standard for connecting AI applications to external systems. It is how tools built on models like Claude or ChatGPT reach into business software.

Who has to register, and when

The deadlines depend on the customer:

• New customers who buy after September 17, 2026 must register external agents within three months of being notified that Agentic Identity is available.
• Existing customers with API-based agents must comply when their contracts come up for renewal.
• Anyone using Salesforce's MCP servers, new or existing, must register within three months of receiving notice.

The tooling is arriving ahead of the requirement. Salesforce's Winter 27 release, available since October 12, 2026, includes API Catalog features customers can use to register agents.

The billing side

Once registered, each successful MCP or direct API call by an outside agent is planned to count as a "Headless Platform Interaction" that consumes Flex Credits. Those interactions are tracked in Digital Wallet, where Salesforce shows Flex Credit consumption.

What is missing is the multiplier: how many credits each interaction burns. Salesforce has not published it. Customers are to get 30 days' notice before metering begins, and agent interactions will not be billed until Salesforce updates its Flex Credit rates.

Some limits are already stated. Metering applies only in active production orgs, so sandboxes, scratch orgs and Developer Edition orgs are exempt. Existing API integrations keep their current pricing.

A Salesforce spokesperson told Salesforce Ben the price per interaction is fixed, but how many interactions get charged depends on an agent's behavior and implementation. That makes the bill a function of how chatty an agent is. Two companies running similar agents could pay very different amounts.

Customers who bring tools such as Claude or ChatGPT into Salesforce will already be paying those providers, so Flex Credits would add a second cost on the Salesforce side. Unused Flex Credits do not roll over into subsequent subscription terms, so guessing wrong on the high side has a cost too.

The security case and the cost worry

Salesforce's stated rationale is control. An agent acting under a human's login inherits that person's full access, and the company's own language about making agents "governable" points at narrower, auditable permissions.

The broader industry problem is real. TechTarget has documented a case at PocketOS, a software company serving car rental businesses, where an AI coding agent deleted the company's production database and backups. Salesforce itself has tightened third-party access to Slack data, partly because private channel memberships change after an integration is approved, Slack's chief product officer told TechTarget.

The pricing is where customers are pushing back, at least in anticipation. The Information reports that Salesforce customers are bracing for new fees to use Claude in Salesforce's apps. Salesforce has not published a rate that would confirm or ease that concern.

Vendors in the integration business are already telling admins to get ready. Stacksync, which sells data-sync and MCP tooling, published an admin checklist on October 23 advising companies to inventory every agent, register each with a scoped permission set, move true system integrations onto dedicated integration users, and settle billing terms before metering starts. Stacksync sells products in this space, so treat its framing accordingly. The steps themselves are plain housekeeping.

What to watch

The sequence is the problem. Registration deadlines run on a three-month clock from notice, and metering needs 30 days' notice. Salesforce has not said whether the credit multiplier will be public before customers must register agents. Existing customers have a built-in checkpoint at renewal, where contract terms can be negotiated. The November target will show whether Salesforce publishes that number first.