Salesforce / Headless 360
Headless 360 pricing. What to expect in 2026.
There is no public Headless 360 production price yet. Here are the anchors you can trust, the line items still undisclosed, and how to budget before a price list exists.
There is no public Headless 360 production price yet. Here are the anchors you can trust, the line items still undisclosed, and how to budget before a price list exists.
Salesforce Headless 360 has no public production price as of July 2026, so expect the real cost to run through Agentforce Flex Credits and per user add ons. This guide covers the anchors you can trust, the line items still undisclosed, and how to budget before a price list exists.
Buyers ask a simple question about Headless 360. What will it cost. The honest answer in July 2026 is that Salesforce has not posted a headless price, so you budget from the meters underneath it.
Expect Headless 360 to bill through Flex Credits and per user add ons rather than a new headline price. The Agentforce pricing page is the closest published anchor. Salesforce framed the shift in its newsroom.
Agent work bills in Flex Credits at about 500 dollars per 100,000, half a cent each. An action costs 20 credits, near 10 cents, and a Voice action costs 30.
The supervising and building seats bill as a per user add on near 125 dollars per month, or 150 dollars in regulated industries. This is separate from the agent traffic meter.
Four line items are usually blank in the first order form, and each is a place where cost can escape unnoticed. Pin every one as a named unit with a rate.
A placeholder rate is a future invoice you cannot forecast. Salesforce keeps the right to set it later, after your agents are in production and your leverage is gone.
Known anchors versus undisclosed line items
| Item | Status | Buyer action |
|---|---|---|
| Flex Credit rate | Published | Use as forecast base |
| Per user add on | Published | Count supervising seats |
| Production runtime | Undisclosed | Pin named capped rate |
| Completion pass through | Undisclosed | Require token rate |
The common advice is to wait for Salesforce to publish a price before you plan, because you cannot budget for what is not posted. We disagree. In our engagement work the buyers who waited lost the only window where they held leverage, which is before the build. The right move is to budget now from the published Flex Credit meter, treat the undisclosed lines as risks to cap, and negotiate a locked rate into the order form while Salesforce still wants the signature. Waiting hands the vendor the timing advantage and the pricing pen.
Source: Redress Compliance advisory engagement file, 2025 to 2026.
You do not need a published price to build a defensible budget. You need the meter, a realistic volume, and a rate you have locked.
Model the cost from a Flex Credit burn built on your own request and action volumes, then layer the per user add on seats on top. The meter, not a price list, is the base.
An agent at 5,000 requests a day and 4 actions each burns 400,000 credits daily, near 2,000 dollars before discount, most of it in actions and Data 360 lookups. Add the supervising seats for a defensible budget.
The strongest moves all happen before the build, while you still hold the signature. Once agents run in production, the meter has the leverage.
Negotiate a capped unit rate per action and per credit, locked for the term. This single move removes the vendor right to reprice after you commit.
Require the four undisclosed lines to be written as named units with rates. Read the wider Headless 360 licensing pillar for the full layer map, and the MCP tool call burn model for the metered unit. The Salesforce developer blog tracks the MCP tool surface.
Salesforce has not committed to a standalone Headless 360 production price list as of July 2026. Expect the cost to keep flowing through Agentforce Flex Credits and per user add ons rather than a single new headline SKU.
Rely on the published Flex Credit rate of about 500 dollars per 100,000 credits, the 20 credit cost of an Agentforce action, and the per user add on near 125 dollars per month. These anchors let you build a forecast without a headless price list.
The undisclosed line items are the production runtime rate for headless traffic, the MCP tool call unit, the model completion pass through, and the rate lock term. Each is usually blank in a first order form and each is where cost escapes.
Budget from a Flex Credit burn model built on realistic request and action volumes, then add the per user add on seats. Model peak days, not the average, because agent traffic is spiky and overage is where budgets break.
Negotiate a capped unit rate that is locked for the term. A locked rate is the one move that protected buyers most in our engagement data, because it removes the vendor right to reprice the meter after you have built on it.
The line items to pin, the Flex Credit burn model, and the buyer side levers before you go agent first. Independent. Buyer side.
Join procurement and IT asset leaders who get our benchmarks on Salesforce, SAP, Oracle, Microsoft, and Workday AI pricing. No vendor spin.
