The Tollgate Goes Up
A quiet but consequential repricing of enterprise software is underway, and ServiceNow has built the clearest example of it. At its Knowledge 2026 conference, the company unveiled Action Fabric, an integration layer that external AI agents must pass through to read data and execute workflows inside the platform. The pricing is action-based: customers pay according to how many operations an agent completes through the layer. Anthropic's Claude is the launch partner, with a connector that lets Claude plug directly into Action Fabric. The message to the market is unambiguous. If an autonomous agent wants to act inside ServiceNow, it pays at the gate, per action.
JPMorgan analyst Mark Murphy described the move in the bluntest possible terms, characterizing Action Fabric as effectively a tax on customers using outside AI agents. That is not a criticism so much as an accurate description of the business logic. ServiceNow, like its peers, watched the agentic wave threaten to turn its richly priced platform into a commodity backend that someone else's AI orchestrates for free. Action Fabric is the toll that reclaims the value. Whether customers experience it as fair monetization or as a captive-market levy will depend entirely on how the per-action meter is calibrated.
SAP Closes the Door, Workday Eyes the Upside
SAP took a more restrictive route to the same destination. In April it updated its API policy to prohibit third-party AI agents from autonomous interactions outside SAP-endorsed architectures, specifically restricting the use of APIs for systems that plan, select or execute sequences of API calls without official approval. SAP's own Joule agents remain permitted, and agents that want to reach SAP business rules must go through the company's Business Accelerator Hub, also metered by usage. The policy drew immediate pushback from user groups and partners, who read it, not unreasonably, as a fence around data the customer believed it owned.
Workday has been less aggressive in mechanism but equally clear in intent. CEO Aneel Bhusri has indicated that charging for agent access offers considerable financial upside, language that aligns the company with the same tollgate strategy ServiceNow is operationalizing. Across all three vendors the pattern rhymes: keep your own agents free or favored, make third-party agents pay or ask permission, and meter the connection either way. For CIOs, the strategic implication is that the choice of agent platform is no longer separable from the choice of system of record. The two are being deliberately welded together by pricing.
Why Per-Seat Pricing Broke
To understand why this is happening now, follow the unit economics. SaaS was built on per-seat subscriptions, a model that assumed a rough proportionality between users and value, and crucially between users and load. Agents shatter that assumption. A single autonomous agent can trigger thousands of API calls a day, consuming compute and data access at a scale no human user approaches, while adding exactly zero seats to the contract. From the vendor's side, that is value delivered and load incurred with no corresponding revenue. The per-seat meter simply stopped measuring the thing that now drives cost.
So the vendors are doing what utilities do: charging for consumption. As the PYMNTS analysis put it, enterprise software is replacing predictable per-seat billing with consumption models that behave less like subscriptions and more like utility invoices, leaving finance teams to manage spend that fluctuates with model activity rather than headcount. This is a profound shift in how technology is budgeted. A line item that was fixed and forecastable becomes variable and, in the worst case, runaway. The CFO who could plan SaaS spend a year out now faces a bill that moves with how busy the company's agents happen to be.
The Integrators and ISVs Caught in the Middle
The vendors are not the only ones affected by metered, gated agent access. A whole ecosystem of systems integrators and independent software vendors built businesses on top of open API access to these platforms, and the new tollgates change their economics overnight. An ISV whose product orchestrates actions across ServiceNow now faces a per-action cost it must either absorb or pass on, and an integrator designing an agentic workflow must architect around which vendor's agents are favored and which are taxed. SAP's restriction on autonomous third-party API sequences is, for some partners, an existential constraint dressed as a policy update.
For enterprise buyers, this reshapes the build-versus-buy calculus and the partner conversation alike. The agent that looked cheapest in a vendor demo may carry consumption costs that only surface at scale, and the integrator's elegant cross-platform automation may run straight into a tollgate that was not there when the statement of work was signed. We advise technology leaders to bring their integrators and key ISVs into the renewal discussion explicitly, to map where agent-access fees will land across the value chain, and to favor designs that keep optionality rather than betting the whole agentic strategy on one vendor's terms of passage.
What This Means for Technology Leaders
The governance challenge here is real and underappreciated. When every agent action carries a metered cost, an inefficient or looping agent is not just a reliability problem, it is a financial one that accrues silently until the invoice arrives. Enterprises will need FinOps-style discipline applied to agentic activity: visibility into which agents are calling which platforms how often, budget guardrails and alerting on consumption, and the ability to throttle or kill a runaway process before it runs up a five-figure surprise. The skills that emerged to control cloud spend are about to be redeployed against agent spend, and most organizations have not started building them.
There is a strategic question lurking beneath the operational one. By metering and gating third-party agents while privileging their own, ServiceNow, SAP and Workday are making a bid to own not just the system of record but the agentic layer on top of it. That is good for their margins and potentially bad for customer optionality. Our advice to technology leaders is to negotiate agent-access terms explicitly in renewals, to resist architectures that lock all agentic value inside one vendor's tollgate, and to price the consumption risk into every business case. The age of the predictable software bill is ending. The age of the metered agent has begun.
