Cloud & Developer Tools is the vertical with the largest raw API surface in the catalog — 616 providers across 3,911 APIs. It’s also the one quietly reinventing itself in 2026: the platforms developers already use to ship software are the same platforms now shipping the infrastructure agents run on. This is day-one, post two of our week walking the hottest six industries on apis.io.
The bands
| Band | What it does | Providers on apis.io |
|---|---|---|
| Edge & cloud platforms | Compute, networking, CDN, DNS | Cloudflare (54 APIs), Vercel (5), Netlify, Render |
| Source, CI & delivery | Repos, builds, registries | GitHub (65), Docker |
| Observability | Metrics, logs, traces, incidents | Datadog (85) |
| API management & gateways | Publish, govern, route APIs | Kong (10), Postman (17), Tyk, Gravitee |
| Backend & data platforms | DB, auth, GraphQL, functions | Supabase (6), Hasura (5), WunderGraph |
Datadog’s 85 APIs and GitHub’s 65 are the kind of multi-plane surfaces that only show up once a platform has matured past a single product.
What’s shifted in 2026
- Gateways grew an AI control plane. Kong AI Gateway now exposes 21 APIs — AI Proxy, Prompt Guard, Semantic Cache, RAG Injector, and model-armor plugins among them. Cloudflare AI Gateway ships a unified model router. The API-management category isn’t just proxying REST anymore; it’s governing model traffic.
- MCP servers are now table stakes. More than twenty platforms in this vertical publish a Model Context Protocol server — Cloudflare, Vercel, GitHub, Kong, Postman, Datadog, Supabase, Hasura, Fern, and more. The dev-tools industry was first to treat agent integration as a shipped product, not a demo.
- GraphQL, serverless, and AI are converging into single surfaces. Vercel pairs an AI Gateway with v0; Hasura adds PromptQL natural-language querying; WunderGraph federates with Cosmo. The lines between “API platform,” “data platform,” and “AI platform” are dissolving inside individual vendors.
Where to start
- The Cloud & Developer Tools industry page — the full cohort.
- The MCP server catalog — the agent-integration surface for these platforms.
- capabilities.apis.io — slice by capability across vendors.
- Agent skills — runnable skills for Apollo GraphQL, APIMatic, Harness, JFrog, and Dev Proxy.
The takeaway
This is the vertical where the catalog’s structure pays off twice: once for the humans evaluating platforms, and again for the agents that will operate them. When your CDN, your gateway, and your observability stack all ship MCP servers, “developer tooling” stops being a category an agent calls and becomes the environment it lives in. Walk it by capability, and watch the AI-gateway and MCP columns — that’s where 2026 is concentrated.