Skip to content
    CalculateForce
    Pricing statuslast verified 25 Oct 2026 →
    • LiveFlex Credits$500 per 100K credits
    • LiveAgentforce action20 creditsvoice30
    • AnnouncedHeadless Platform InteractionmultiplierTBA

    Agentic access

    What will Salesforce charge for MCP and external agent calls?

    Independent analysis, not affiliated with or endorsed by Salesforce. Built on 10 Salesforce pages, each cited below and checked on 25 Oct 2026.

    Quick answer

    AnnouncedLast verified 25 Oct 2026

    No per-call charge yet. Salesforce will meter every successful call a registered external agent makes over Model Context Protocol (MCP) or API as a Headless Platform Interaction, paid in Flex Credits. The multiplier is TBA, metering isn't active, and Salesforce promises 30 days' notice. It will apply in production orgs only, and traditional integrations are unchanged.1,2

    In one pictureLast verified 25 Oct 2026
    How an external agent's call would reach your bill

    When the multiplier is published

    31 Aug 2026: Rate card: TBA (TBA); 17 Sep 2026: Notice promised (TBA); Not dated: Multiplier published (Live). Last verified 25 Oct 2026.
    DateEventStatus
    31 Aug 2026Rate card: TBATBA
    17 Sep 2026Notice promisedTBA
    Not datedMultiplier publishedLive

    Last verified 25 Oct 2026

    01What it means

    What a Headless Platform Interaction is

    A Headless Platform Interaction (HPI) is the meter Salesforce has announced for agentic traffic: every successful call a registered external agent makes to Salesforce, over MCP or direct API, paid in Flex Credits. Salesforce published the billing model in a Help article on 17 Sep 2026, and its rate card lists the usage type with the multiplier as TBA.1,2

    Registration will be what makes an agent billable: a registered agent gets its own identity and permissions, and the same step makes its activity visible, governable and billable. Today every hosted MCP call still runs as the signed-in user.1,3

    The meter will add to other charges rather than replace them. The rate card applies these usage types in addition to its other usage types, so a call that also runs an agent action or Data 360 processing could incur both. Salesforce has published no worked example of the two together.2

    The names have moved too: Headless 360 was renamed AIforce on 4 Sep 2026, and the functionality is called the Headless Toolkit.1

    02Price

    What is priced, and what isn't

    One number is missing: the credits per interaction. Everything an external agent touches today is priced by other meters.

    ItemPrice or ruleStatus
    Credits per Headless Platform Interaction2TBATBA
    A Flex Credit at list4$0.005 per creditLive
    Hosted MCP servers5TBAFlex Credits requiredTBA
    Agent identity licenses6TBATBA
    Data 360 MCP Server7Billed as Data 360 usage todayLive
    Agentforce calling external MCP tools8Billed as agent actionsLive
    Agent API9Billed per agent actionLive
    Traditional API calls1No Flex Credits · daily API allocationLive

    Source. Salesforce's rate cards, pricing pages and Help articles. The rate card lists the HPI multiplier as TBA. Cost per interaction will be the multiplier × your per-credit rate; the multiplier is unpublished.

    Last verified 25 Oct 2026

    The full agentic-access map

    03What gets metered

    Which calls cost what

    Status matters more than price here. Two rows are announced; four are billed today under other meters.

    1. 1. Registered agents calling over MCPAnnounced

      Each successful call becomes a Headless Platform Interaction once metering starts. Using any Salesforce MCP server will require agent registration within three months of Salesforce's notice.1

      Count your agent's calls

    2. 2. Registered agents calling the API directlyAnnounced

      The same meter covers direct API calls. Existing customers with API agents register them and move to the new billing model at renewal.1

      Count your agent's calls

    3. 3. The Data 360 MCP ServerLive

      Billed today as the Data 360 Connect API usage it triggers: Data 360 Queries, for example, cost 3 credits per 1M rows processed at the base tier.2,7

      Estimate Data 360 credits

    4. 4. Agentforce calling external MCP toolsLive

      An agent action like any other: 20 credits in text, 30 in voice. It is not a Headless Platform Interaction, which covers agents calling into Salesforce.2,8

      Price agent actions

    5. 5. The Agent APILive

      Billed per agent action under the normal Agentforce rules, with no separate per-call fee. Salesforce hasn't said whether a registered agent's Agent API calls will also count as Headless Platform Interactions.9

    6. 6. Traditional integrationsLive

      REST, SOAP and Bulk calls from integrations and people's apps draw on the daily API allocation, not Flex Credits, and Salesforce says their pricing stays exactly as it is.1

      The full agentic-access map
    04Who is affected

    Who registration and metering reach

    Any org an external AI agent works in, once registration ships. Salesforce is targeting November 2026: a target, not a commitment.1

    • Customers buying on or after 17 Sep 2026: register every agent that uses Salesforce APIs within three months of Salesforce's notice that registration is available.1
    • Existing customers with API agents: register them and migrate to the new billing model at renewal.1
    • Anyone using a Salesforce MCP server: registration within three months of the notice, for all customers.1
    • Production orgs only. Sandboxes, scratch orgs and Developer Edition orgs are excluded, though Agentforce actions an agent triggers there are still billed at sandbox rates.1
    • Max edition customers: Salesforce says Max will include an allocation of Headless 360 capacity in future. Its size and start date are TBA.10
    05Announced · Unknown

    What Salesforce has said, and what it hasn't

    Announced

    • The meter: Headless Platform Interaction, to be paid in Flex Credits.1
    • Notice: Salesforce promises 30 days before metering starts.1
    • Where: production orgs only, once metering starts.1
    • Traditional integrations: unchanged.1
    • Target: November 2026 for registration and the new billing model.1
    • Charges will add to other usage types rather than replace them.2
    • Hosted MCP servers: generally available since 29 Apr 2026, for orgs with Flex Credits; their billing is TBA.3,5

    Unknown

    • The multiplier: credits per interaction2

      Flex Credits Rate Card · TBA

    • When metering starts1

      Salesforce's 30-day notice

    • Agent identity licenses: SKU and price6

      Not published · TBA

    • Headless 360 capacity in Max10

      Size and start date TBA

    • Whether hosted MCP calls count against the daily API allocation5

      Not documented

    • What happens to agents left unregistered1

      Not stated by Salesforce
    06ExampleModeling scenario · not official Salesforce pricing

    One external agent, before the multiplier

    A sales team's own research agent, described in a sentence. Its calls can be counted today; their price can't.

    We know · We estimate · We need

    “An external AI agent researches an account before every AE meeting.”

    We know

    2.11M calls a year

    200 AEs × 4 requests a day × 12 Salesforce calls × 220 working days. Each call would be one Headless Platform Interaction.

    Calculatedfrom the scenario

    We estimate

    Unknown

    No estimate is possible yet: the multiplier is TBA. The calculator below prices placeholder multipliers, labelled as a modeling scenario.

    Unknownmultiplier TBA

    We need

    Flex Credits Rate Card · Headless Platform Interaction multiplier

    Salesforce lists it as TBA and promises 30 days' notice before metering starts.

    Unknownuntil published
    Count your own agent's calls

    How the sentence became four inputs

    • Who: AEs, from the sentence; 200 assumed — it gives no team size.
    • How often: 4 a day per AE, assumed from "before every AE meeting" (about 4 meetings a day).
    • Salesforce calls: 12 per request, assumed — account research reads the account, contacts, opportunities, activities, cases and notes.
    • Days: 220 working days a year, assumed.
    07CalculatorLast verified 25 Oct 2026

    Count your agent's Salesforce calls

    Agents, requests, calls and working days in; interactions a year out. Any cost is a modeling scenario, not official Salesforce pricing.

    people
    per person
    MCP or API calls
    days
    Requests a year
    176K

    200 people × 4 requests a day × 220 working days

    Salesforce interactions a year
    2.11M

    Each successful call would be one Headless Platform Interaction once metering starts.

    Modeling scenario· not official Salesforce pricing

    MultiplierTBA

    • If each interaction cost 1 credit2,110,000 modeled credits$10,600 modeled a year at list
    • If each interaction cost 10 credits21,100,000 modeled credits$106,000 modeled a year at list

    Placeholders, not Salesforce figures. Cost = interactions × multiplier × $0.005 per creditPublic priceWhen Salesforce publishes the multiplier (TBA today), this box becomes one public-price row.

    Known today

    $0Flex Credits for these calls todayCalculated

    As of 25 Oct 2026: traditional REST, SOAP and Bulk calls draw on the daily API allocation, not Flex Credits, and external-agent metering has not started. Once Salesforce publishes the multiplier (TBA) and gives 30 days' notice, a registered agent's calls are metered as Headless Platform Interactions — in production orgs only; sandboxes, scratch orgs and Developer Edition orgs are excluded.

    08Next action

    Alert me when the multiplier is published

    Salesforce has promised 30 days' notice before metering starts. Choose the topics you want to hear about when that changes.

    Model an external agent in full

    Pricing Alerts

    Notify me when Salesforce changes this.

    Topics

    Submitting stores your email and the topics you pick with CalculateForce and sends you a confirmation email.

    09SourcesLast verified 25 Oct 2026

    Where every line comes from

    Salesforce's own pages. Each superscript in the article points to one of them; the excerpts are verbatim.

    1. 01

      Understand AIforce Impact (Knowledge Article 005360285)

      Salesforce Help · 17 Sep 2026

      “Sandboxes, scratch orgs, and Developer Edition orgs don’t incur HPI metering through Digital Wallet, so admins and developers can build and test without drawing down Flex Credits.”

    2. 02

      Flex Credits Rate Card (updated as of August 31, 2026)

      Salesforce · 31 Aug 2026

      “Usage types apply to Headless 360 usage only which are in addition to other Usage Types as set forth in this Rate Card.”

    3. 03

      Salesforce Hosted MCP Servers Are Now Generally Available

      Salesforce Developers · 29 Apr 2026

      “is now a production-ready capability for every Enterprise Edition org and above.”

    4. 04

      Salesforce Introduces New Flexible Agentforce Pricing to Accelerate the Digital Labor Revolution

      Salesforce · 15 May 2025

      “Each of these actions consumes just 20 Flex Credits ($0.10 per action)”

    5. 05

      Get Started | Hosted MCP Servers

      Salesforce Developers · Accessed 25 Oct 2026

      “Salesforce Hosted MCP Servers are intended only for customers with Flex Credits and you may be billed for server usage.”

    1. 06

      Salesforce Headless 360 Datasheet

      Salesforce · Accessed 25 Oct 2026

      “Control agent identity and access with dedicated agent identity licenses, governing which agents can access the platform and what actions they are permitted to take.”

    2. 07

      Data 360 MCP Server | Hosted MCP Servers Reference

      Salesforce Developers · Accessed 25 Oct 2026

      “MCP server calls count as calls to the underlying Connect API endpoints for limits and Flex Credit usage.”

    3. 08

      Considerations for MCP for Agentforce

      Salesforce Help · Accessed 25 Oct 2026

      “Agent actions that reference MCP server actions (MCP tool actions) are billed at the same rate as other agent actions.”

    4. 09

      Agent API Considerations

      Salesforce Developers · Accessed 25 Oct 2026

      “Agent API usage impacts credit consumption as described in the following Salesforce help topic: Generative AI Usage and Billing.”

    5. 10

      New Salesforce Editions Bundle Everything Businesses Need for Agentic Transformation

      Salesforce · 3 Sep 2026

      “In the future, Max editions will also include an allocation for Headless 360 capacity, bringing Salesforce’s platform to every agent, app, and experience.”

    Last verified

    25 Oct 2026

    Every Salesforce price, rate and status on this page comes from CalculateForce's pricing registry, checked against the pages above on 25 Oct 2026. Salesforce changes its rate card several times a year; where a value is announced or TBA, the page says so.

    Independent. Not affiliated with or endorsed by Salesforce. Spotted a change? Tell us.

    10FAQ

    Frequently asked questions

    Does Salesforce charge for MCP today?

    Not per call. Headless Platform Interactions aren't metered yet: the multiplier is TBA, and Salesforce will give 30 days' notice before metering starts. Some MCP use already costs credits through other meters: the Data 360 MCP Server bills as Data 360 usage, and Agentforce calling external MCP tools bills as agent actions.1,2,7,8

    What is a Headless Platform Interaction?

    Salesforce's meter for agentic traffic: every successful call a registered external agent makes to Salesforce, over MCP or direct API. It will be paid in Flex Credits.1

    How much will a Headless Platform Interaction cost?

    Salesforce hasn't said. The rate card lists the multiplier as TBA. The cost per interaction will be the multiplier times your per-credit rate; at list, a credit is $0.005.2,4

    Will sandbox testing be charged?

    Not as Headless Platform Interactions: sandboxes, scratch orgs and Developer Edition orgs are excluded. Agentforce actions an agent triggers in a sandbox are still billed, at sandbox rates.1

    Do my existing API integrations change?

    Salesforce says the pricing and security options for traditional integrations stay exactly as they are; they keep drawing on the daily API allocation. An API connection that is really an AI agent must be registered and moved to the new model at renewal.1

    When does it start?

    Salesforce is targeting November 2026 for agent registration, new security controls and the billing model, a target rather than a commitment. Metering starts only after a multiplier is published, with 30 days' notice.1

    Keep reading