The Free Ride For Agents Is Ending
For two years, enterprises built AI agents on the comfortable assumption that if they paid for a seat in a SaaS platform, an agent acting on their behalf could reach that platform's data for free. That assumption is now collapsing. ServiceNow, SAP and Workday, three of the pillars of the enterprise software stack, are all moving to put a price and a gate on AI agent access to the systems of record they control. The shift is quiet but consequential, because it changes the fundamental economics of the agentic strategies that CIOs have spent the past year designing and funding.
The trigger is structural. Per-seat pricing worked when software was used by humans, because a human is a natural unit of consumption: one person, one login, a bounded amount of activity. Agents break that logic entirely. A single autonomous agent can trigger thousands of API calls a day without adding a seat, extracting enormous value while paying nothing incremental under the old model. Vendors have realized that unlimited agent access to their data, at seat prices, is a business they cannot sustain, and they are redrawing the meter before the agentic wave fully arrives.
ServiceNow Builds A Tollgate Called Action Fabric
ServiceNow has been the most explicit. Its Action Fabric is an integration layer that external AI agents must pass through to access data and execute workflows inside the platform, and the pricing is metered: customers pay according to how many operations an agent completes via the layer. Launch partner Anthropic's Claude connects directly into it. The design is a tollgate by any other name, and ServiceNow is not hiding the ambition. Jon Sigler, the company's executive vice president of AI Platform, framed the endgame plainly, describing a future in which "all of these systems are calling directly into our Action Fabric."
That vision is worth sitting with, because it is a claim on the center of the enterprise. ServiceNow is positioning Action Fabric not merely as a way to bill agents but as the mandatory router through which every agent, regardless of who built it, reaches the workflows and data ServiceNow governs. The accompanying AI Control Tower features, expected to reach general availability in August, wrap the tollgate in governance language: control, visibility, auditability. Buyers get real value from that control. They also get a new dependency, because the layer that governs their agents is also the layer that charges for them, and those two functions are now inseparable.
SAP Slams The Door, Then Faces The Backlash
SAP took a blunter approach and paid for it immediately. In April, the company restricted third-party AI agents from making autonomous API calls outside SAP-endorsed architectures, while its own Joule agents remained permitted. The message to the ecosystem was hard to misread: agents built by SAP get to act on SAP data, and agents built by anyone else do not, unless they route through channels SAP blesses. For a platform that sits at the transactional heart of thousands of large enterprises, that is a significant assertion of control over how customers can automate their own operations.
The backlash was swift. The DSAG user group and partners with existing connectors, including Microsoft Copilot and Salesforce Einstein, protested the change, arguing that it walls off data customers consider their own. Chief executive Christian Klein tried to defuse the tension, stating that customers would not be asked to pay to access their own data, though the underlying policy language reportedly remained unchanged. That gap between reassurance and policy is exactly what enterprises should scrutinize. When a vendor's public framing and its API terms disagree, the terms are what govern your agents, and the reassurance is worth only as much as the contract behind it.
Workday Confirms The Pattern Is Structural
Workday's contribution to the story is candor about motive. Chief executive Aneel Bhusri indicated that charging for agent access offered considerable financial upside for the company, signaling that Workday intends to pursue a similar tollgate approach to monetizing the flow of agents through its platform. Coming from a third major vendor, that admission removes any doubt that this is a coordinated direction of travel rather than one company's idiosyncratic pricing experiment. The enterprise software industry has collectively decided that agent access is a billable event, and it is saying so out loud.
We appreciate the honesty, because it lets buyers plan. The convergence across ServiceNow, SAP and Workday means agentic strategies can no longer be costed as if the underlying platforms are neutral, free pipes. Every agent that reads an HR record, updates an ERP entry, or triggers a workflow is about to carry a marginal cost, and at the volumes agents operate, those marginal costs aggregate into a serious line item. The organizations that modeled their automation business cases on free platform access are going to discover that the return on investment they promised leadership assumed a price of zero that no longer holds.
What CIOs Should Do Before The Bill Arrives
The immediate task for technology leaders is to re-underwrite their agentic roadmaps against a consumption-priced world. That means instrumenting how many operations a planned agent will actually perform against each platform, then pricing those operations at the vendor's metered rate before, not after, deployment. An agent that looks cheap in a pilot can become punishing at production volume, because the same autonomy that makes it useful is what multiplies its API calls. Cost governance, the kind platform engineering teams already apply to cloud spend, now has to extend to every agent that touches a system of record.
The deeper strategic move is to resist single-vendor lock-in at the agent layer. When the platform that governs your agents is also the one billing them, and the one that could restrict rival agents tomorrow as SAP did, concentration risk becomes acute. CIOs should push for portability, negotiate agent-access economics into contracts explicitly rather than accepting default metered rates, and treat governance layers like Action Fabric as powerful but not benign. The tollgate offers genuine control and auditability. It also hands the vendor a lever over your automation strategy, and the price of pulling that lever is now on the meter.
