Fetching from the wire…
Top 5 · 2026-05-20 · source-backed
SaaStr published an expanded AI Agent API Report Card grading 144 B2B APIs across six dimensions: API design, events/streaming, auth/security, rate limits, SDKs/docs, and agent readiness. The average score was 71 out of 100. A C+.
The leaderboard tells a story. Stripe scored 95. Slack got 87. Adyen pulled 83. Linear hit 80. These are API-first companies that were built for programmatic access from day one. Now look at the bottom: Marketo at 50, Gainsight at 48, Workday at 38. Companies built around human UIs that bolted on APIs as an afterthought.
SaaStr's key finding: "API-first vendors gain share while legacy vendors with human-UI focus bleed out." That quote alone should be on a slide in every product review at every SaaS company this quarter.
What makes this particularly sharp is the timing. In the same 48-hour window, Google proposed WebMCP as an open web standard allowing developers to expose structured JavaScript functions directly to browser-based AI agents. It's being co-developed with Microsoft and incubated through the W3C. Booking.com, Expedia, Instacart, Shopify, and Redfin are already testing it in Chrome 149. And OpenCLI hit 22K GitHub stars by doing what WebMCP tries to standardize: turning any website into a CLI for AI agents, no API required.
The message is clear. If your product doesn't have agent-ready APIs, someone will build the agent interface anyway, and you won't control it. WebMCP gives you a standard way to do it right. OpenCLI shows what happens when you don't.
For builders choosing vendors: check the SaaStr scoreboard before signing annual contracts. If your CRM or analytics platform scores below 60, you're going to hit a wall when you try to wire it into agent workflows. And if you're building a B2B product: agent readiness isn't a feature anymore. It's table stakes. The scoreboard is public. Your customers can see your grade.
Each link below shares sources, entities, or timing with this story.
Chrome supports WebMCP / Shared entities / Same source / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Chrome supports WebMCP); both cover Chrome, JavaScript, W3C, WebMCP; cite the same source (WebMCP).
Google released WebMCP / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Google released WebMCP); both cover CLI, Google, Microsoft, SaaS; reported by the same outlet (github.com).
SaaStr benchmarked against Workday / Shared entities / Same source domain / Shared topic / What happened next / Tension / Downstream implication
Linked by a graph relationship (SaaStr benchmarked against Workday); both cover CRM, SaaS, SaaStr, Slack; reported by the same outlet (saastr.com).
SaaStr benchmarked against Workday / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (SaaStr benchmarked against Workday); both cover CRM, Marketo, SaaS, SaaStr; reported by the same outlet (saastr.com).
Chrome supports WebMCP / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Chrome supports WebMCP); both cover Chrome, Google, JavaScript, Microsoft; reported by the same outlet (developer.chrome.com).
Chrome supports WebMCP / Shared entities / Same source / Shared topic / Earlier coverage
Linked by a graph relationship (Chrome supports WebMCP); both cover Chrome, JavaScript, W3C, WebMCP; cite the same source (WebMCP).
Chrome supports WebMCP / Shared entities / Same source / Shared topic / What happened next
Linked by a graph relationship (Chrome supports WebMCP); both cover Chrome, CLI, GitHub, OpenCLI; cite the same source (OpenCLI).
SaaStr benchmarked against Workday / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr benchmarked against Workday); both cover APIs, CRM, SaaS, SaaStr; reported by the same outlet (saastr.com).