The developer-tooling surface on apis.io is one of the most agent-relevant verticals in the catalog. Almost every autonomous-coding agent (Claude Code, Cursor, Aider, Devin, Codex) talks to some combination of these APIs to read code, open PRs, run pipelines, file issues, and watch deploys. Walking the catalog by dev-tools capability is the cleanest way to see what an agent’s tool surface actually looks like in 2026.
The pipeline-shaped catalog
Sorted by where they sit in the developer pipeline:
| Stage | Examples on apis.io |
|---|---|
| Source control | GitHub, GitLab, Bitbucket, Gerrit, Sourcehut |
| CI/CD | CircleCI, Buildkite, GitHub Actions, GitLab CI, Jenkins, Drone |
| Project / issue tracking | Linear, Jira, Asana, Notion, Height, Shortcut |
| Code review / quality | Codecov, SonarCloud, Reviewpad, GitGuardian |
| Package and artifact | npm, PyPI, Maven Central, Docker Hub, Quay, Artifactory |
| Container / runtime | Docker, Kubernetes, Helm, Crossplane, Pulumi, Terraform |
| Deploy / hosting | Render, Fly, Vercel, Netlify, Railway, Cloudflare, Heroku |
| Observability | Datadog, Grafana, Sentry, Honeycomb, Lightstep, New Relic |
| Secrets and config | HashiCorp Vault, Doppler, 1Password, Infisical |
This list is incomplete and that’s fine — the catalog has many more in each row. The point is the shape: a coding agent that touches one row will reliably touch three or four. Catalog browsing by row is more useful than catalog browsing by provider name.
What’s shifted in the cohort
Three patterns from the last six months:
- MCP servers are showing up everywhere. GitHub ships an official MCP server. Linear has community MCPs. Notion ships one. Atlassian ships one. The MCP surface is becoming the agent-native entry point for dev-tool integration, sitting alongside the REST/GraphQL API rather than replacing it.
- GraphQL-first new entrants. Linear, Hashnode, modern Shopify, GitHub’s GraphQL API. The pattern is becoming the default for any tool where the data model has rich relationships and clients want flexible queries.
- AsyncAPI for webhooks. Linear’s webhook surface is documented as AsyncAPI. GitHub’s webhook taxonomy is well-structured enough that it could be. The shift from “prose webhook docs” to “AsyncAPI webhook contracts” is happening in this cohort first, and it makes catalog ingestion dramatically cleaner.
Where to start
If you’re building or operating in this space and want apis.io entry points:
- CI/CD category — pipelines and build infrastructure.
- Collaboration category — project tracking, code review, docs.
- Container Orchestration category — runtime / k8s surface.
- Linear and GitHub — the two cleanest profile examples of modern catalog-friendly dev-tool surfaces.
For agent builders specifically: walking the capabilities.apis.io listing by verb — “open a pull request”, “merge a PR”, “trigger a workflow”, “find an issue” — surfaces the right per-task API contracts across vendors. That’s the right level of abstraction for tool-routing agents.
The takeaway
Developer tooling is the vertical where agent infrastructure is being built fastest, because the agents themselves are developer tools that operate other developer tools. Every new MCP server, every new AsyncAPI webhook surface, every new GraphQL-first SaaS in this cohort makes the catalog more useful and the agent stack more composable.
The provider list keeps growing. The capability list is where the answer to “what tool does this agent need next?” actually lives.