Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-06-08 · source-backed
SaaStr built a tool that grades your API on how well an AI agent can drive it, ran it across a bunch of categories, and came back with a thesis that should worry anyone selling software: buyers are starting to choose tools based on how well agents operate them, not on feature lists.
The Agentic API grader, built on Claude, OpenAI, and Gemini, scored products on webhooks, rate limits, MCP support, and structured responses. The conclusion: Salesforce is winning against Marketo, Outreach, Salesloft, Gong, Atlassian, and Monday not on features but on agent-friendly plumbing. And in a lot of cases, agents skip the product entirely and just do the job. SaaStr calls it a new, quiet churn motion, you rebuild a workflow on a platform your agents can operate, then realize you're paying for three tools you no longer open.
This rhymes with the MCP-goes-mainstream data: server downloads jumped from 100K to 8M in five months, 10,000-plus active public servers, the protocol donated to the Linux Foundation. And it's got real revenue behind it on the incumbent side. ServiceNow's FY26 Q1 8-K shows Now Assist customers spending over $1M in ACV growing more than 130% year over year. Agent-readiness isn't theory, it's converting.
I'm partly skeptical here, because SaaStr sells to exactly the audience that wants to believe "agents change everything." The grader is their own methodology, not an independent standard. But strip the hype and the core mechanic holds. If an agent can't call your tool cleanly, the agent does the work without your tool, and you find out at renewal.
So the action item, whether you're building a product or just an internal API: make it agent-operable now. Stable webhooks, sane rate limits, an MCP server, structured responses that say what you can do, how to call it, and what comes back. This is the same discipline as good API design, with a new and unforgiving consumer. The agent doesn't read your marketing page. It reads your schema, and if the schema's bad it routes around you.
Each link below shares sources, entities, or timing with this story.
ServiceNow released Agentforce / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (ServiceNow released Agentforce); both cover ACV, Atlassian, SaaStr, Salesforce; reported by the same outlet (saastr.com).
Outreach supports Claude / Shared entities / Same source domain / What happened next / Tension
Linked by a graph relationship (Outreach supports Claude); both cover Atlassian, Claude, Gong, SaaStr; reported by the same outlet (saastr.com).
Outreach supports Claude / Shared entities / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Outreach supports Claude); both cover Claude, Gemini, Linux Foundation, MCP; overlapping topics (agent, server).
SaaStr uses OpenAI / Shared entities / Same source domain / Earlier coverage / Tension
Linked by a graph relationship (SaaStr uses OpenAI); both cover Monday, OpenAI, SaaStr, ServiceNow; reported by the same outlet (saastr.com).
Claude Cowork supports Outreach / Shared entities / What happened next
Linked by a graph relationship (Claude Cowork supports Outreach); both cover Agent, Claude, MCP, Salesforce; picks up the Agent thread on 2026-06-28.
Outreach supports Claude / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Outreach supports Claude); both cover CLAUDE, SaaStr, Salesforce; reported by the same outlet (saastr.com).
Outreach supports Claude / Shared entities / Same source domain / What happened next
Linked by a graph relationship (Outreach supports Claude); both cover Atlassian, CLAUDE, MCP, SaaStr; reported by the same outlet (saastr.com).
Linked by a graph relationship (Outreach supports Claude); both cover Claude, Marketo, SaaStr, ServiceNow; reported by the same outlet (saastr.com).