Which AI tools ship an API

An API is the least glamorous thing an AI product can ship and one of the most revealing. It says the company expects to be part of someone else’s system rather than the whole of it. Across 6,225 live products where we know the answer, 60.1% ship one — and the ones that do are noticeably less likely to disappear.

Coverage and definition

“Ships an API” means a documented programmatic interface intended for third parties — not an internal endpoint, and not a webhook-only integration. 6,225 of 6,441 live products have a recorded answer; 216 do not and are excluded from every rate below rather than assumed to be false.

Finding one: an API goes with surviving

7.4% against 10.5%. This is one of the larger survival differences we have found between two groups defined by a single product property, and it is worth being careful about what it means.

We do not think shipping an API keeps a company alive. The likelier reading is that an API is a marker for two things that do: a technical buyer, and integration into a customer’s workflow. A product reached through code is a product someone has spent engineering time wiring in, and that time is a switching cost. A product reached only through its own interface can be abandoned in an afternoon.

There is also a survivorship caution attached. Building an API takes resources, so better-resourced companies are more likely to have one, and better-resourced companies survive more often for reasons that have nothing to do with the API. The honest claim is correlation with a plausible mechanism, not proof of cause.

Finding two: a six-fold spread by market

Security leads at 95.6%, because a security product that cannot be automated is not a security product — it has to run continuously against systems nobody is watching. AI Models (91.9%) is definitional: the API is the product.

Writing sits last at 14.5%, with Learning (17.6%) and Design (26.4%) just above. Those are markets where the output is consumed by a person, one piece at a time, and where there is no obvious system to plug into. It is also, precisely, the set of markets our wrapper-risk report identifies as thinnest — a product that is a prompt with an interface has little to expose programmatically that the underlying model does not already expose better.

Finding three: it is a funding question too

Series A (71.3%) and growth-stage (71.1%) companies ship APIs at essentially identical rates. Bootstrapped companies ship them at 26.9% — less than half. An API is real engineering that produces no visible product, which is exactly the kind of work an unfunded team defers.

Read alongside the survival data, that compounds a disadvantage the bootstrapping picture already describes: unfunded companies cluster in the most contested markets and are also least likely to build the thing most associated with staying embedded.

One caveat on that chart. Our pre-seed group has a known-answer population of just 92 products and shows 100%, which is a coverage artefact rather than a finding — for recently added companies we tend to record the API field only when we have positively confirmed it. Read the four large stages.

What shipping one looks like

The highest-opportunity products in the catalog that expose a public API.

Every market

Photo: Brett Sayles / Pexels. Colour-graded for Falcoscan.

← All reports