APIs.io is a federated, agent-friendly API discovery network. It indexes the public surface of API providers across the internet — their APIs, capabilities, schemas, event-driven specs, governance rules, vocabularies, and JSON-LD contexts — and exposes each slice of metadata at its own subdomain. Each site is a separate Jekyll deploy on GitHub Pages, all sharing the same upstream provider catalog.
| Site | Repo | What it indexes |
|---|---|---|
| apis.io | network | Search hub, blog, build pipeline |
| developer.apis.io | portal | Developer portal & feeds |
| providers.apis.io | providers | API provider profiles |
| apis.apis.io | apis | Individual API records |
| capabilities.apis.io | capabilities | Naftiko capability specs |
| schemas.apis.io | schemas | JSON Schemas |
| asyncapi.apis.io | asyncapi | AsyncAPI event-driven specs |
| json-ld.apis.io | json-ld | JSON-LD contexts |
| rules.apis.io | rules | Spectral governance rulesets |
| vocabularies.apis.io | vocabularies | Provider vocabularies |
| tags.apis.io | tags | API tag index |
| examples.apis.io | examples | API usage examples |
The network repo is the build hub. Its scripts/build.py reads from the api-evangelist provider repos — Git-versioned APIs.json profiles, one per provider — and emits Jekyll collections into every other site repo above. Each site then renders independently from its own collection.
Topical search nodes (e.g. payments-node, healthcare-node, weather-node, us-federal-government-node) are vertical slices of the same catalog, scoped to a domain.
A set of headless service repos backs the search and admin surfaces:
- apis-io-engine, apis-io-search, apis-io-publishing
- apis-io-ratings, apis-io-linter, apis-io-rules
- apis-io-properties, apis-io-tags
- apis-io-maintainers, apis-io-authentication
- APIs.json (github.com/apis-json) — the machine-readable specification this network is built on
- API Commons (github.com/api-commons) — the standard vocabulary of common API operational properties
- Naftiko — the open-source framework that runs capability specs as REST, MCP, and Agent Skill surfaces
- api-evangelist — the upstream provider profile repos this network is built from
APIs.io, APIs.json, and API Commons are projects led by Kin Lane and Steve Willmott — open infrastructure for the next generation of API discovery. Open issues on the relevant site repo for site-specific questions, on github.com/apis-json for spec questions, or email info@apievangelist.com.