Pays for itself · SaaS costs
Will Salesforce charge for AI agents on its API or MCP?
Short answer: Yes. Salesforce has announced that AI agents built outside its platform must be registered under a program called Agentic Identity, and that their calls to Salesforce over the API or MCP will be metered as "Headless Platform Interactions" and paid with Flex Credits.
As of October 27, 2026, the price per call has not been published, and metering starts no earlier than 30 days after Salesforce publishes it. That leaves a short window to find your agents, separate them from human logins, measure how many calls each workflow makes, and set terms for your next renewal.
11:59 helps organizations do this as part of a License Posture report, and builds agents in a layer the client owns that are registered properly and designed to make fewer calls.
What Salesforce has announced
| When | What | What it means for you |
|---|---|---|
| September 17, 2026 | Salesforce published how the billing model for agent calls will work | Customers buying on or after this date must register API-based agents within three months of notice |
| October 12, 2026 | Winter '27 release, with API Catalog features used to register agents | The tools to register agents are arriving now |
| November 2026 (targeted) | Agentic Identity: agent registration, security controls and the billing model | Anyone using a Salesforce MCP server must register agents within three months of notice |
| Your next renewal | Existing customers with API-based agents register and move to the new billing model | Renewal is where the terms for agent calls get set |
| Not yet announced | The Flex Credit rate per agent call | Metering starts no earlier than 30 days after the rate is published |
These dates come from Salesforce's help documentation as reported by industry analysts. Confirm them against Salesforce's current documentation and your own order form.
What gets metered, and what doesn't
| Type of traffic | Metered? |
|---|---|
| A registered AI agent calling Salesforce through a Salesforce MCP server | Yes, per successful call |
| A registered AI agent calling Salesforce APIs directly | Yes, per successful call |
| Traditional system integrations that are not agents | No; current pricing continues, according to reports |
| Sandboxes, scratch orgs and Developer Edition orgs | No, according to reports |
| A shared integration user that serves both agents and scheduled jobs | Not yet defined; this is the gray zone to clean up first |
Can't we just run the agent under a user's login?
Technically, Salesforce may not be able to tell from the traffic alone whether a person or an agent is behind a login. That is not where the risk sits. Registration becomes part of your contract terms, user licenses are for named people, and sharing a person's credentials with an agent is the kind of finding that surfaces in a license review or audit.
For a commercial firm that is a contract risk. For a State of California department it is an audit finding and a vendor dispute the CIO would have to explain to oversight. The safer course is to register agents as agents, give each one only the access it needs, and control cost by making fewer, better calls.
What to do before metering starts
- Inventory every agent and MCP client that touches Salesforce: owner, connected app, sign-in method, the user it runs as, the objects it reads and writes, and the workflow it supports.
- Separate agent identities from people and integrations. Give each agent its own registered identity and narrow permissions, keep system integrations on dedicated users, and retire agents running on personal credentials.
- Measure calls per workflow. Once the rate is published, cost is calls per outcome × outcomes × credits per call × your contracted credit price. You can know three of the four today.
- Design for fewer calls. Batch reads, cache reference data and avoid agents that poll. Every unnecessary call becomes a line item.
- Set terms at renewal. Ask for a named rate per agent call, a cap or committed volume, usage visibility, and rate protection for the term.
How this changes the license math
Until now, work done by an agent inside Salesforce cost nothing beyond the seats you already paid for. Once metering starts, it has a price. Any plan to reduce seats by moving work onto agents has to subtract the cost of the calls those agents make. That makes the case for owning your agent layer stronger, not weaker: in a layer you own, you decide which system does the work, you can see every call, and you can route work to licenses you already pay for.
Salesforce is not alone. SAP's 2026 API policy goes further and bars outside AI agents from calling its APIs directly, while ServiceNow has kept direct access open. Expect every large platform to settle on rules and prices for agent access over the next few renewal cycles.
Who helps with this: 11:59
11:59 is a Sacramento AI and cloud managed services firm with 23+ years of delivery, an AWS Advanced Tier Partner with the AWS Generative AI Competency. California agencies contract through CMAS 3-24-01-1044 and TDDC MSA #5-22-70-25-189.
Common questions
Will Salesforce charge for AI agents that use its API or MCP?
Yes. Salesforce plans to register outside AI agents under Agentic Identity and meter their API and MCP calls as Headless Platform Interactions, paid with Flex Credits. The per-call rate had not been published as of October 27, 2026.
When does metering start?
No earlier than 30 days after Salesforce publishes the Flex Credit rate per agent call. Registration deadlines fall within three months of notice for MCP users and new customers, and at renewal for existing customers with API-based agents.
Are our existing integrations affected?
Traditional integrations that are not agents are reported to keep their current pricing. Shared integration users that also serve agents are the gray area to separate first.
Can we avoid the charge by running agents under a user's login?
It may be hard for Salesforce to detect, but registration is a contract obligation and user licenses are for named people. For a State of California department in particular, it is an audit risk, not a savings plan.
What should we do now?
Inventory agents and MCP clients, separate agent identities from people and integrations, measure calls per workflow, design agents to make fewer calls, and set rate, cap and visibility terms at renewal.
Does this affect California departments?
Yes, at renewal for existing contracts. Departments with Salesforce maintenance and operations renewals coming up should inventory their agents and model the cost before negotiating.
Start here
Start with a License Posture report on your Salesforce estate. It covers seats and agent access together, and it is scoped to the estate and quoted before we start.
Schedule an AI Rapid ScanRead the Reduce Your SaaS Costs sales sheet · Can AI agents reduce SaaS license costs?
Sources
Crypto Briefing: Salesforce plans to make external AI agents register · Vantage Point: Salesforce will meter agentic MCP and API calls · Stacksync: Salesforce MCP pricing, Flex Credits and HPI · Wisevoter: Salesforce requires registration for external AI agents · Techzine: SAP blocks external AI agents; Salesforce and ServiceNow don't