The meter exists and the rate does not

Salesforce's Flex Credits Rate Card, updated as of August 31, 2026, carries a usage type named Headless Platform Interaction under the Customer 360 Platform category. The multiplier column next to it reads TBA. Anyone designing an integration or an agent that reaches Salesforce through its APIs can now see that those calls will draw on Flex Credits, and cannot work out what they will cost.

The change reached the trade press through reporting by Thomas Morgan at Salesforce Ben on September 24. Salesforce Ben is a second-tier source, a community trade site rather than the vendor, so our desk read both rate cards instead. The usage type sits on Salesforce's own published card, whose footer reads "Updated as of August 31, 2026. Technical restrictions may apply."

Nothing was announced during the week of September 23. The change is dated August 31 and has sat in a published document for close to four weeks while the reporting caught up. A footnote scopes these usage types to headless usage and says they "are in addition to other Usage Types as set forth in this Rate Card". These credits add to the existing meters rather than replacing them.

The definition already moved once

The June 17, 2026 version of the same card described this differently. Under the same category it listed two rows, one named for a Salesforce record operation with CRUD spelled out in the row name, the other for a Salesforce process invocation naming flows and Apex. Both were priced TBA. By August 31 the two had been collapsed into a single Headless Platform Interaction row.

Neither version carried a price, so the change is about scope rather than money. Two narrow rows told an architect what was being counted. A record write counted. A flow run counted. One broad row covering headless platform interaction draws that line nowhere, and a scope you cannot bound is harder to estimate than a rate that is merely missing.

Ten weeks separate the two cards. A definition that widened once can widen again, and the card says as much in plain language: "Usage types, tiers, and associated multipliers may be updated from time to time."

The advice everyone followed now has a meter

Publishing a placeholder is not deceptive. A vendor has to name a usage type before it can price one, and naming it on a public card gives more warning than a quiet switch-on would. The no-rollover clause, which says Flex Credits "must be used before the Order End Date set forth in the Usage Details table on the Order Form, and no rollover will be permitted", is ordinary commercial language for prepaid consumption, and so is the line about updates from time to time. Our checklist for reading a licensing change treats both as routine.

The narrower concern is the one to state exactly. For the past two years the standard architectural advice has been to push integration and machine access off the user interface and onto APIs. Build against the API, keep the screens for people. That advice was sound, and it was given when those calls were not separately metered. Teams that followed it now run an architecture whose running cost depends on a number Salesforce has not published.

We reported on September 21 that buyer research on headless Salesforce access found roughly 90% of respondents already reach the platform from outside its screens or plan to, and that three quarters of those who had modelled the money expected spending to rise rather than fall. Headless Platform Interaction is the mechanism that turns that expectation into an invoice line.

One column and no sandbox split

One detail separates this row from its neighbours. The Agentforce rows carry separate multipliers for production and sandbox use. The Headless Platform Interaction row carries a single multiplier column with no such split. On a card where adjacent rows make that distinction, the absence here is a question to raise rather than a conclusion to draw.

The Salesforce Ben report says customers will get 30 days of notice before metering starts, and that sandboxes, scratch orgs and Developer Edition are excluded. Both are the report's claims rather than Salesforce statements. The help page cited for them could not be retrieved from our side, and neither appears on the rate card we read. Confirm both with an account team before planning around them.

A figure of ten cents per action is circulating on aggregator sites alongside this story. That rate belongs to the Agentforce Standard Action row and has no connection to Headless Platform Interaction, which remains unpriced. We have written before about how agentic work gets counted and priced, and borrowing one row's number for a different row is how bad forecasts get built.

Count your headless calls before someone prices them

The useful preparation is measurable today. Pull current API call volume by consumer, covering integration users, middleware, MCP and agent endpoints, and partner applications. Split it between calls that read or write records and calls that start a flow or Apex, since the June card separated those and the August card does not. Whatever multiplier eventually lands, your volume is the number it multiplies.

Tim Combridge, a technical content writer at Salesforce Ben, framed the planning problem in that report. Organizations, he wrote, will need to "estimate the cost of running them before they can make a decision on whether or not to proceed." He writes for a trade publication rather than for Salesforce, and no executive comment on this exists. His point holds anyway, though that estimate cannot be produced for headless calls until the multiplier arrives.

Put one question to your account executive and ask for the answer in writing. When Headless Platform Interaction gets a multiplier, will it apply to the API volume the current contract already covers, or only to calls made through the newer agent paths? The answer changes what your renewal is worth, and our guide to negotiating a multi-year SaaS renewal is a reasonable place to take it next.