☰

Salesforce will start charging when your AI agents call it. Here's what small businesses should do now

By Intelligent Solutions LLC · · Updated · 4 min read

Salesforce will start charging when your AI agents call it. Here's what small businesses should do now

Connecting an AI assistant to your CRM has been one of the easiest AI wins for small teams this year. Ask Claude or ChatGPT to pull up an account, update a deal, or prep you for a meeting, and it just works.

That convenience is about to come with a meter. On September 22, Salesforce Ben reported that Salesforce is preparing to charge Flex Credits for calls that registered AI agents make into Salesforce. Here's what that means in plain English.

What's changing

Today, many outside AI tools reach Salesforce through MCP (Model Context Protocol, a standard way for AI tools to plug into business software) or through Salesforce's APIs (the connections software uses to talk to other software).

Under the new model, AI agents will need to be registered in Salesforce with their own login and permissions. Salesforce calls this Agentic Identity. Once an agent is registered, every successful call it makes to Salesforce, whether through MCP or directly through an API, counts as a "Headless Platform Interaction" and uses Flex Credits, Salesforce's pay-as-you-go currency for AI usage.

Usage will be tracked in Salesforce's Digital Wallet, its tool for monitoring consumption.

What isn't changing (yet)

Before anyone panics, a few important details:

  • Nothing is being billed yet. Salesforce has not published how many credits each interaction will cost, and it says customers will get 30 days' notice before metering starts.
  • Traditional integrations are not affected. Existing API integrations, like a standard sync with your accounting or marketing tool, keep their current pricing.
  • Testing environments are excluded. Metering applies only to active production orgs, not sandboxes, scratch orgs, or Developer Edition orgs.

Salesforce's own Headless 360 help article also lists new usage types for third-party agents, covering record operations (creating, reading, updating, or deleting records) and process invocations (triggering Flows or Apex), with multipliers still marked "TBA." The same article notes that basic MCP access is included in Enterprise Edition and above.

Why this matters for a small business

The security piece is good news. Giving each AI agent its own identity and permissions, rather than letting it act as whichever employee is logged in, means you can control exactly what that agent can see and do. Salesforce Ben's technical writer called it "a really good step in the right direction."

The cost piece is the one to watch. If your team pays for Claude or ChatGPT, you'll now potentially pay twice: once to the AI provider, and again in Flex Credits on the Salesforce side. And an agent that loops through dozens of records to answer one question could make a lot of calls.

This fits a bigger pattern. In Salesforce's latest earnings call, a company executive told analysts that half of bookings came from customers "refilling the tank" with more Flex Credits, according to The Register. The same report cites a Gartner warning that credit-based pricing can change at the vendor's discretion and that volume discounts need to be negotiated upfront.

Consumption pricing isn't bad. It can be cheaper than per-user licenses when usage is light. But it rewards the companies that know what they're running.

What to do this month

You have a window before metering starts. Use it:

  • Inventory your AI connections. List every AI tool that touches Salesforce: Claude, ChatGPT, Copilot, custom agents, AppExchange apps with "AI" in the name. You can't budget for what you can't see.
  • Separate agents from integrations. Figure out which connections are traditional integrations (unaffected) and which are AI agents acting on your data (likely to be metered).
  • Check your Digital Wallet. If you already use Flex Credits for Agentforce, get familiar with where usage appears now so new charges don't blend in unnoticed.
  • Tighten agent permissions. When you register agents under Agentic Identity, give each one only the objects and fields it needs. Fewer permissions means fewer surprises, on security and on cost.
  • Talk to your account executive before renewal. Ask what the multiplier will be, whether any credits are included in your edition, and what volume pricing looks like.

The bottom line

AI agents working inside your CRM are becoming normal, and Salesforce is building both the guardrails and the billing to match. The businesses that come out ahead will be the ones who know which agents they're running, what those agents are allowed to touch, and roughly what each one costs.

Not sure what's connected to your Salesforce org today? We'll map it for you. Book a free audit and we'll show you where AI is already touching your data, and how to keep it secure and cost-predictable.

Sources

Keep reading