Salesforce will meter every call an outside AI agent makes

What happened

Salesforce posted a help article on September 17, 2026 that changes how outside AI agents reach its platform. Admins must register each agent that uses Salesforce APIs or MCP servers. Each registered agent gets its own identity. Every successful call that agent makes then counts as a Headless Platform Interaction and consumes Flex Credits. Salesforce lists the rate as “TBA” and promises 30 days’ notice before metering starts. Sandboxes and Developer Edition orgs are exempt, and traditional integrations keep today’s pricing.

What it means

You will pay twice for the same agent. The model vendor bills tokens, and Salesforce bills each call the agent makes into your records. Flex Credits list at $500 per 100,000, but the per-call multiplier is not published. Salesforce told SF Ben that the number of charged interactions depends on how the agent is built and prompted.

An agent that makes ten lookups where two are enough costs five times as much on the Salesforce side. Registration does carry a control benefit. The agent gets its own identity instead of borrowing an employee’s.

Why it matters to you

Systems of record now charge rent for agent access. For an AR team, an agent that pulls account history before a dunning email becomes a metered event. For a controller, agent access becomes a variable budget line with no unit price yet. Existing customers must register agents and migrate connections at renewal, so your renewal date sets your exposure. Other systems of record can copy this model.

What to watch

Salesforce lists the rate as “TBA” and promises 30 days’ notice before metering starts. That notice is the first date to watch. Watch for the per-call multiplier, which Salesforce has not published. Watch how renewals trigger the move to registered agents. Watch whether other systems of record start charging for agent access the same way.