Artificial Intelligence (AI)

Salesforce Agent Registration: Outside AI Agents Will Need an Identity and Will Be Metered

An overhead studio photograph of a neat row of blank plastic ID badge holders on lanyards beside a brass mechanical tally counter on a dark slate surface, a visual for Salesforce agent registration, where each outside AI agent gets its own badge and every call it makes is counted

Salesforce agent registration is coming. Salesforce says outside AI agents will need their own registered identity. That covers Claude, ChatGPT or an agent you built. Once registered, every successful call they make will be counted against Flex Credits.

Salesforce laid this out in a help article, Understand AIforce Impact, published September 17, 2026. It says it is "targeting November" for new security controls, agent registration and a new billing model. As of mid-November, we have not seen Salesforce announce that the registration feature, called Agentic Identity, is available.

The short version: list every AI agent and tool that touches your Salesforce org. Find out which ones Salesforce will count as agents. Check your renewal date, because existing customers move to the new model at renewal. Plan a narrow permission set for each agent. Ask your account executive what a metered call will cost before the meter starts.

What Salesforce agent registration changes

Today, many teams connect an AI tool to Salesforce by signing it in as a person. The agent then acts with that person’s access. Salesforce wants to end that pattern for agents.

Under the new controls, admins register each agent on the platform. Salesforce says registration "carves out a discrete identity for each agent instead of letting it operate under the identity of the person it assists." Admins can also give that identity a narrower permission set than a human user has.

Salesforce’s own comparison is plain: registration is like "issuing the agent its own badge, rather than lending it an employee badge."

This is part of AIforce, the effort Salesforce first announced at TDX 2026 under the name Headless 360. The idea is that agents can work with Salesforce data from any screen, not only Salesforce’s own. We covered the Anthropic side in Claudeforce. There, Salesforce opened its data to Claude but kept the rules. Salesforce agent registration is the next step in the same direction. The rules, and now the billing, stay with Salesforce.

How the metering will work

Salesforce agent registration and billing are tied together. Salesforce says the registration step is what makes an agent’s activity "visible, governable, and billable."

Here is how Salesforce describes the billing side:

  • Once an agent is registered, its usage is tracked in Digital Wallet and draws down Flex Credits.

  • Every successful call a registered agent makes counts as a Headless Platform Interaction, or HPI. That applies "whether it arrives over Model Context Protocol (MCP) or direct API."

  • The cost of one HPI has not been set. The rate is listed as "TBA," and agent usage is not metered yet.

  • Salesforce says it will give "30 days’ notice" before a rate is added and metering begins.

  • Only active production orgs are metered. Sandboxes, scratch orgs and Developer Edition orgs are not.

  • Traditional integrations keep their current pricing and security options. Salesforce says the new model "addresses agentic traffic specifically."

If MCP is new to you, our guide to the Model Context Protocol explains how AI tools use it to reach other systems.

Salesforce agent registration deadlines, by customer type

Salesforce gives three different timelines. Which one applies depends on when you bought and what you connect.

  • Customers who buy on or after September 17, 2026: register all agents that use Salesforce APIs. The deadline is three months after Salesforce’s notice that Agentic Identity is available.

  • Existing customers using agents with APIs: register all agents and move those connections to the new billing model at renewal.

  • Anyone using a Salesforce MCP server: register within three months of that notice. Salesforce says, "This is for all customers."

The MCP line matters most for smaller teams. Salesforce offers hosted MCP servers so tools like Claude can connect without custom code. Its Headless 360 developer center describes "a quick start to securely connect Claude to Salesforce through hosted MCPs." The same page labels the Headless 360 MCP server as a beta. If your staff set one up, it falls under the three-month window no matter when you renew.

Who this reaches beyond the sales team

It is easy to read Salesforce agent registration as a sales-cloud story. It reaches further.

Many nonprofits run on Salesforce’s Nonprofit Cloud. Many associations run an association management system built on Salesforce. Nimble AMS, for example, describes itself as "built entirely on the Salesforce platform." If your member or donor records live there, an AI agent that reads them is calling Salesforce.

That includes tools your vendors add. An AMS vendor or an app from AppExchange may ship an AI feature that calls Salesforce on your behalf. Ask each vendor how their AI features connect. Ask whether Salesforce will count them as agents in your org.

What Salesforce admins should do now

Salesforce agent registration starts once Agentic Identity is available. You can prepare before then.

  1. List every agent and AI tool that touches your org. Include Claude or ChatGPT connectors, custom agents, scripts that call the API for AI work, and vendor AI features.

  2. Find the ones that sign in as a person. These are the connections registration is meant to replace. Note whose account each one uses today.

  3. Ask your account executive which connections count as agents. Salesforce says it will meter "agentic traffic" and leave traditional integrations alone. It classifies a connection as an agent once it uses the registered agent’s credentials. Get a clear answer for your setup.

  4. Check your renewal date. Existing customers move at renewal, so that date is your planning deadline.

  5. Check that your org can use Flex Credits. Salesforce says the first step is enabling Flex Credit billing. You can do that through Salesforce Foundations, "currently available at $0," or another SKU.

  6. Draft a permission set for each agent. Give each one only the objects and fields it needs. This is the part of registration that improves security, so plan it with care.

  7. Test in a sandbox. Sandbox calls are not metered, so build and test there.

  8. Plan for cost before the rate lands. Estimate how many calls each agent makes in a day. When Salesforce posts a rate on its Flex Credits rate card, you will have 30 days to adjust. Our post on API key controls at OpenAI covers the same habit on the model side. Know what each key or agent does, and cap it.

After Salesforce agent registration: what changes

Salesforce says the last step is to reconfigure each MCP client or agent. Each one must "present the new OAuth credentials associated with the registered agent." Then you reconnect. After that, "the agent works as it did before."

For staff, little should look different. For admins, a few things change:

  • Each agent shows up as its own identity. You can see what it did without digging through a person’s activity.

  • Each agent can have less access than the person it helps.

  • Each successful call costs credits in production, once metering starts.

That second point is a real gain. An agent that can only read the fields it needs is much safer than one that borrows a manager’s full access.

Our take

Salesforce agent registration fixes a real problem. Agents that act under a person’s login are hard to audit and often have too much access. A separate, narrower identity is the right design. It matches what we recommended in CMS and MCP agent permissions.

The billing is the open question. Salesforce has not said what an interaction costs, and an agent can make a lot of calls. Until the rate is posted, treat every outside agent as a future line item. Count its calls now, keep only the agents that earn their place, and get the cost in writing before your renewal.

Frequently Asked Questions

What is Salesforce agent registration?

It is a coming Salesforce feature, called Agentic Identity, that gives each outside AI agent its own identity on the platform. Admins register the agent and can give it a narrower permission set than a human user. It replaces the pattern of an agent signing in as a person.

When does Salesforce agent registration start?

Salesforce’s September 17, 2026 help article says it is “targeting November.” As of mid-November we had not seen an availability notice. Deadlines run from that notice: three months for new customers and for anyone using a Salesforce MCP server, and at renewal for existing customers.

Will Salesforce charge for calls from Claude or ChatGPT?

Once an agent is registered and Salesforce sets a rate, each successful call it makes in a production org counts as a Headless Platform Interaction and uses Flex Credits. The rate is listed as “TBA,” and Salesforce says it will give 30 days’ notice before metering begins.

Are sandboxes metered?

No. Salesforce says sandboxes, scratch orgs and Developer Edition orgs do not incur this metering, so teams can build and test without using Flex Credits.

Do regular integrations change?

Salesforce says pricing and security options for traditional integrations “stay exactly as they are today.” The new model covers agent traffic. Ask your account executive which of your connections count as agents.

Does this affect associations on a Salesforce-based AMS?

It can. Systems like Nimble AMS are built on Salesforce, so an AI agent that reads member records there calls Salesforce. Ask your AMS vendor how its AI features connect and whether they will need registration.

What do I need to enable first?

Salesforce says your org must be enabled for Flex Credit billing. That can be done through Salesforce Foundations, which it lists as “currently available at $0,” or another SKU that allows Flex Credit usage.

What should I do before registration opens?

List every AI agent and tool connected to your org, note which ones sign in as a person, check your renewal date, draft a narrow permission set for each agent, and ask your account executive for the cost of a metered call.

Digital Matters

Artificial Intelligence (AI) Desk