Incumbent Pricing Responses: ServiceNow's Action Fabric and SAP's AI API Ban

Updated

Incumbent Pricing Responses: ServiceNow's Action Fabric and SAP's AI API Ban

As third-party autonomous AI agents threaten to erode the traditional per-seat licensing model (where a single agent can execute workflows that previously required dozens of human seats), enterprise software incumbents are erecting technical and financial "tollgates" to protect their revenues and lock in customer data.

ServiceNow's Action Fabric: A Metered "Tax" on Outside Agents

At its Knowledge 2026 conference in May 2026, ServiceNow unveiled Action Fabric, a new integration layer that external AI agents must pass through to access data and execute workflows inside its platform. Rather than charging per user, ServiceNow is metering this usage and charging customers based on how many operations/actions an external agent completes.1

JPMorgan analyst Mark Murphy described this pricing model as effectively a "tax" or a tollgate on customers using outside AI systems to interact with data they already store in ServiceNow's applications.

SAP's Restrictive API Policy: Outlawing Third-Party Agent Logic

SAP has taken an even more aggressive, protective stance. In April 2026, the ERP giant quietly updated its API policy (v4/2026) to explicitly prohibit third-party autonomous or generative AI systems from interacting with its systems outside of SAP-endorsed architectures. The policy states:

"except through and within the limits of SAP-endorsed architectures, data services, or service-specific pathways expressly identified and intended for such purposes, SAP prohibits API use for: (a) interaction or integration with (semi-) autonomous or generative AI systems that plan, select, or execute sequences of API calls, and (b) scraping, harvesting, or systematic and/or large-scale data extraction or replication."

This policy effectively forces enterprises to route agentic workflows through SAP’s own native assistant, Joule Agents, or face potential throttling and compliance disputes. The policy has drawn immediate pushback from partners, consultants, and the German-speaking user group DSAG. DSAG Board Chairman Jens Hungershausen noted that the policy's ambiguity creates a "huge amount of uncertainty" that could deter customers from adopting third-party AI innovations that connect to SAP.

Workday's Flex Credits and Standalone Agent Fees

Workday is heading down a similar path. CEO Aneel Bhusri noted that charging for agent access offers considerable financial upside. Workday has introduced Workday Flex Credits to provide flexible consumption-based pricing, while also offering standalone agents (such as recruiting, talent, and manager agents) priced at $12 to $38 per Full-Time Equivalent (FSE) per month, per agent.

What This Means for Founders and Buyers

For AI-native founders selling into enterprises, these incumbent maneuvers mean that "just integration" is no longer a simple technical task. Incumbents are actively weaponizing their data ownership to enforce lock-in, either by taxing external API calls (ServiceNow) or flatly banning autonomous sequence execution (SAP). Founders must:

  1. Architect for Data Gravity: Expect that connecting an external agent to an enterprise's system of record will incur unbudgeted "data tolls" or compliance audits for the buyer.
  2. Build Non-Disruptive Integration Patterns: Design integrations that comply with "endorsed architectures" or prepare to help buyers navigate and negotiate these restrictive vendor policies.

  1. An instance of AI is turning software companies into heavy utility businesses — ServiceNow is replacing its traditional user-based subscription with a usage model that bills clients for the exact number of actions an AI agent performs. This illustrates a major software provider abandoning human seat licenses to charge directly for automated work. ↩︎

Part of

This finding is an example of a pattern recurring across your work:

Revision history

  • Updated without a stated reason.
    · by migration
  • Updated without a stated reason.
    · by migration
  • Updated without a stated reason.
    · by migration
  • Updated without a stated reason.
    · by migration
  • Updated without a stated reason.
    · by migration
  • Updated without a stated reason.
    · by migration