Making the case for Self-Serve APIs
My recent integration work has got me thinking.
The first vendor was Google Ads. I never spoke to anyone — signed up with an email, ran their quickstart, hit a snag in the OAuth flow, found the fix three sentences into their auth doc, and was making real requests inside an hour. The second vendor I also never spoke to. Signup form to working integration in roughly the same window. The third was different. I went looking for it — knew the category, knew the company name, walked in with intent. Their docs page redirected me to a “book a demo” form. Within days I’d shipped against a competitor.
Different vendors. Different categories. Different price points.
Same dynamic.
Two of them got onto my integration shortlist without ever knowing I was a prospect. One of them lost the deal before they knew there was one. The agent did the shopping — the synthesis tool I’d been pasting their docs into all afternoon, the assistant I asked to compare authentication flows, the model I ran the rate-limit math through. The vendor’s funnel still assumed a human knocked on the door. The buyer’s funnel didn’t have a human in it.
That’s when I started thinking about this less as a developer-experience question and more as a distribution one.
The Buyer’s Funnel Doesn’t Have a Human In It
Let me be specific about what I mean. The dominant story in B2B leadership rooms right now is that public docs and self-serve APIs are a developer-experience investment you fund post-Series-B. Sales-led growth funded the company. AEs scope integrations. Demos generate pipeline. Custom implementation work preserves margin. The motion converts; why diversify surface area now?
It’s a rational default. It built most of the enterprise software economy we have today.
Here’s the context that often gets left out. 94% of B2B buyers now use LLMs during their purchase journey, primarily as synthesis tools mid-funnel — comparing offerings, evaluating proposals, summarizing what they’ve gathered. Two-thirds say they’d prefer to buy without engaging a sales rep at all. Gartner forecasts that by 2028, 90% of B2B buying will be agent-intermediated, pushing roughly $15 trillion through agent-driven exchanges.
The so-what doesn’t depend on the forecast. The present-tense data already says the buyer’s funnel doesn’t have a human in it. The vendor’s still does. That’s the gap that gets you cut from the consideration set before you knew there was a deal.
There’s a Discipline That Already Speaks This Language
This isn’t a marketing story. It’s a distribution one — and there’s a mature discipline with the vocabulary for it.
Retail merchandising. Specifically, shelf-space economics: the body of practice that governs how products get found, picked up, and bought when the buyer is making a hundred adjacent comparisons in a finite window. Shelf, placement, planogram, end-cap, category captain, slotting fee. These aren’t metaphors. The dynamics are identical. An agent shopping the API landscape is doing exactly what a buyer does walking down an aisle: scanning labels, evaluating fit on a small set of legible signals, putting one item in the cart.
Once you have the vocabulary, the maturity arc falls out.
Stage 1 is being on the shelf at all. There is a public schema. There is a quickstart that runs without a human in the loop. A developer — or an agent acting on a developer’s behalf — can find your endpoint, evaluate your auth flow, and ship a first request without speaking to anyone at the company. If you’re not at Stage 1, you’re not in the consideration set. You don’t lose the deal. You don’t get evaluated.
Stage 2 is earning placement. Your docs are clean. Your error messages explain themselves. Your rate limits are honest. Your idempotency is documented. Your examples compile on first paste. You’re the API the agent reaches for first because the friction of integrating you is lower than anyone else in the category. Stage 2 is where competitive advantage actually lives in 2026 through 2028.
Stage 3 is becoming the category captain. Your name is in the prompt. Developers and the agents working for them say “Stripe” when they mean payments, “Twilio” when they mean messaging, “Plaid” when they mean bank connections. You’re the default that other names get compared to. Category captains in agentic-discovery markets get set by who reaches Stage 2 first and compounds longest.
Public docs are how you exist. Tool quality is how you win.
Three Stages, Four Examples
The three integrations I started with were each at a different stage. The two that made my shortlist were Stage 2 — clean public quickstarts, OAuth that worked first try, docs doing the selling. The one I’d hunted by name had slipped backward into a sales-call gate. Category captaincy slipping in real time.
Stage 0 has two flavors, and I’ve shipped against both.
Bloomberg actually publishes its API documentation. The BLPAPI Developer’s Guide is a public PDF. The HTTP API has a public GitHub repo. What’s gated is access, not docs. To use the API you need either a Terminal subscription — roughly $30,000 per seat per year — or an enterprise data contract negotiated through a sales conversation. There’s no developer signup. The shelf is real, the labels are pristine, and the buyer can’t reach it.
The same dynamic shows up smaller. An equestrian streaming platform we work with: IP-whitelisted API, server-side only, documentation that arrives by email after you ask. Different scale, same gate.
Then there’s Substack. I publish on it, and when I wanted programmatic access for an automation, the only path was a cookie-auth shim against an undocumented surface — no published schema for the publishing surface. The shelf isn’t gated; the labels just aren’t there. Two flavors of Stage 0: docs published but access locked, or access available but nothing to read.
The pre-agent precedent for Stage 3 is Stripe, Twilio, and AWS. Stripe didn’t outcompete Braintree on processing economics. They outcompeted on a signup that worked in seven lines of code while competitors were still running multi-day merchant-account approvals, and on documentation a developer could actually read. Twilio’s 2016 S-1 said the same thing in SEC language: revenue depended on self-service adoption by developers, and over a million developer accounts had registered by IPO. AWS got there earlier — S3 launched in March 2006 on an email address and a credit card, with enterprise sales infrastructure built years later on a developer base AWS had already won. All shelf-space plays, a decade before agents made the play structural. None of these are stories about devrel as a cost center. They’re stories about distribution as the moat.
The present-tense version is at the protocol layer. Anthropic released the Model Context Protocol in November 2024, betting that whoever published the standard for tool schemas would shape the ecosystem. Twelve months later, Anthropic donated MCP to the Agentic AI Foundation, a new directed fund under the Linux Foundation co-founded with Block and OpenAI — each contributing a project of their own. Platinum members include AWS, Bloomberg, Cloudflare, Google, and Microsoft. Textbook captaincy graduation: a vendor protocol becoming open infrastructure. Publishing the interface didn’t dilute the position; it locked it in.
The Sales-Led Argument Deserves a Real Answer
There’s an honest objection worth taking seriously. Sales-led GTM has built most of the enterprise software companies that matter. Custom implementation preserves margin self-serve can’t. AE-driven scoping protects deal velocity in real enterprise sales — procurement, security review, six-stakeholder buying committee. Diversifying surface area too early dilutes focus and creates support cost the company isn’t ready to absorb. Every one of those points is real.
But here’s what’s worth noticing. None of those arguments contradicts the shelf-space frame. They argue for keeping the sales-led motion for the deals where it works — large, complex, multi-stakeholder enterprise contracts. The shelf-space play isn’t a replacement. It’s the play for the part of the buyer base that doesn’t behave like a procurement committee anymore: the engineer at a target account who’s been told to evaluate three vendors by Friday, who pastes your docs into an LLM after dinner and decides on Monday which one procurement should call. That engineer is the shortlist gatekeeper even for the deals that close through sales. Cutting yourself off from her upstream because the downstream contract still needs an AE doesn’t preserve the motion. It cedes the shortlist.
What This Actually Changes
For an operator weighing whether to fund this work, four things follow.
First, Stage 1 is overdue, not Series-B-funded. If your interface isn’t readable by an agent today, you’re not in the consideration set tomorrow. The budget conversation isn’t “should we fund developer experience?” It’s “should we be visible in the discovery layer agents are using now?” Asked that way, the answer is forced.
Second, Stage 2 is the durable bet. Within 18 to 24 months, every serious competitor will reach Stage 1. Shelf presence becomes table stakes. Differentiation moves to tool quality — schema clarity, error messages that diagnose themselves, idempotency, rate-limit honesty, examples that compile on first paste. That’s where engineering compounds.
Third, the first hire is DX engineering, not developer marketing. “Developer evangelist” is a 2018 job title. The 2026 version is the engineer who writes API docs, designs schemas an LLM can parse cleanly, and maintains examples that don’t rot. Senior engineering hire, not marketing.
Fourth, stop scoping integrations and start measuring picks. If your sales motion treats every integration as a custom implementation, you’re optimizing for the wrong unit. Measure how often agents pick you over the alternatives. That’s the leading indicator for the next 18 months of revenue. Instrument for it now.
None of that is rocket science. It’s just discipline — the discipline that separates a company that compounds for a decade from one that gets a great quarter and a soft landing.
Close
The pattern shows up everywhere the buyer is a developer or an agent acting on a developer’s behalf. Payments, messaging, identity, observability, ad-tech, analytics — anything where the integration is the product. The companies that publish their interfaces this year will define their categories. The ones that don’t will be footnotes in someone else’s quickstart guide.
The internal conversation isn’t “are we ready for devrel?” It’s “are we visible to the buyer the buyer has become?” One of those questions gets a budget. The other gets the category.
The vendors who exist tomorrow are the ones whose interfaces an agent can read today. The vendors who win are the ones whose interfaces an agent reaches for first.
The shelf is already there. The agents are already shopping.
Recent Comments