Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-06-28 · source-backed
The agent business model showed up this week, and it's rent.
At Knowledge 2026, ServiceNow launched Action Fabric, a layer that every external AI agent must pass through to read data or run workflows inside the ServiceNow platform, metered on action-based pricing (ServiceNow Newsroom). JPMorgan analyst Mark Murphy called it what it is: effectively a tax on customers who use outside agents to touch data they already store in ServiceNow. Anthropic's Claude is a launch partner via a Claude Cowork connector, and an MCP Server now ships in every Now Assist / AI Native SKU. So the invitation is "bring your agents," and the fine print is "we meter every action they take."
This isn't one company being clever. ServiceNow, SAP, and Workday are independently converging on the same move: metering and charging for agent access to their systems of record (PYMNTS). Action-based or consumption-based fees on any agent, internal or third-party, that reads or writes your enterprise data. All three of the largest workflow platforms, at once. When your data is the system of record, you can tax every agent that needs it.
The piece that makes this stick is interoperability. A2A protocol 0.3 shipped with gRPC transport, cryptographically signed Agent Cards, and server-as-agent recursive composition, now backed by 150-plus organizations including Microsoft, AWS, Salesforce, SAP, ServiceNow, and Workday (Google Cloud). The "MCP for tools, A2A for agent coordination" stack is the enterprise default now. But the protocols being open doesn't make the data access free. The toll booth sits on top of the open road.
If you're building enterprise agents, price this in as a first-order constraint, not a footnote. Your agent's unit economics now include a per-action fee to the system of record it depends on, and that fee is set by a vendor with every incentive to defend its workflow moat. "We integrate via open protocols" is not the same as "this is cheap to run at scale." Model the metering before you promise a client a number.
Each link below shares sources, entities, or timing with this story.
Anthropic partners with Block / Shared entities / Same source / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Anthropic partners with Block); both cover A2A, Claude Cowork, JPMorgan, MCP; cite the same source (PYMNTS).
Anthropic supports Claude Cowork / Shared entities / Same source / Shared topic / Earlier coverage
Linked by a graph relationship (Anthropic supports Claude Cowork); both cover Action, Action Fabric, Agent, AI Native SKU; cite the same source (ServiceNow Newsroom).
SAP partners with Anthropic / Shared entities / Same source / Shared topic / Earlier coverage
Linked by a graph relationship (SAP partners with Anthropic); both cover A2A, MCP, Microsoft, Salesforce; cite the same source (Google Cloud).
AWS partners with Anthropic / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (AWS partners with Anthropic); both cover A2A, AWS, MCP, Microsoft; overlapping topics (access, agent).
AWS partners with Anthropic / Shared entities / Shared topic / What happened next
Linked by a graph relationship (AWS partners with Anthropic); both cover Anthropic, AWS, Claude, Claude Cowork; overlapping topics (claude, model).
Anthropic partners with Google / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Anthropic partners with Google); both cover Anthropic, MCP, Microsoft, Salesforce; overlapping topics (agent, enterprise, protocol, servicenow).
Linked by a graph relationship (Anthropic partners with Google); both cover Agent, AWS, Claude Cowork, MCP; overlapping topics (agent, claude, model).
AWS partners with Anthropic / Shared entities / Shared topic / What happened next
Linked by a graph relationship (AWS partners with Anthropic); both cover Agent, AWS, Google Cloud, MCP; overlapping topics (agent, claude).