Fetching from the wire…
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.
This is the most consequential architecture decision in enterprise software since cloud versus on-prem, and it happened quietly across three vendor announcements. PYMNTS connected the dots first. SAP blocks. Its API Policy v4/2026, published in late April, prohibits using SAP...
ServiceNow launched Action Fabric with a generally available MCP Server included in every Now Assist and AI Native SKU. Claude Cowork connects directly for conversation-to-execution. Every action runs through AI Control Tower with identity verification, permission scoping, and...
Microsoft, Adobe, SAP, Salesforce, PayPal, ServiceNow. The three-protocol stack (A2A + MCP + WebMCP) is becoming standard enterprise plumbing. Google Cloud Blog
AAIF will govern MCP, Block's Goose, AGENTS.md, and Google's A2A under vendor-neutral open governance. AWS, Cisco, Google, Microsoft, Salesforce, SAP, and ServiceNow are participating. Both inter-agent communication and tool access protocols now have neutral stewardship. Linux...
If you wrote an MCP server before July, it's on a protocol shape the maintainers have already removed. Not deprecated-with-a-migration-window. Removed from the spec. MCP lead maintainers David Soria Parra and Den Delimarsky published an updated roadmap on August 22, and the re...
The help-center doc confirms models launching on or after August 2, 2026 weave an imperceptible watermark into generated text plus C2PA-signed provenance metadata on image files. Model-level means it's present across the API, Claude, Claude Code, Claude Cowork, and through AWS...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.