areas.apis.io organises the APIs.io network by subject area. Each page is a curated collection of the specifications, tools, and documentation behind a topic — schema design, data modeling, cloud, cybersecurity standards, and more — and cross-links the API providers on the network working in that area.
Areas are the topical knowledge base of the network. They are distinct from providers (who ships an API), industries (who buys an API), and categories (what an API does).
Live site: https://apis.io/areas/
_areas/— one Markdown file per area, generated from thekind: topicrepos in the api-evangelist organization. Front matter carries the curated resource list, tags, and tag-matched related providers.index.html,_layouts/,_includes/,assets/— the browse and detail pages_config.yml— Jekyll site configuration
This collection is regenerated by network/scripts/build_areas.py (invoked from build.py), which scans every kind: topic repo under the API Evangelist source, renders its curated resources, and cross-links network providers by tag overlap. Those same topic repos are excluded from the provider catalog so they no longer appear as bogus providers on providers.apis.io. The site itself is a Jekyll build deployed via the apis.io CloudFront origin.
| Site | Repo | What it indexes |
|---|---|---|
| apis.io | network | Search hub, blog, build pipeline |
| providers.apis.io | providers | API provider profiles |
| apis.apis.io | apis | Individual API records |
| industries.apis.io | industries | Providers by industry vertical |
| regions.apis.io | regions | Providers by sales region |
| areas.apis.io | areas | Curated subject areas (topic repos) |
| tags.apis.io | tags | API tag index |
- APIs.json — the machine-readable spec each provider profile uses
- API Commons — the standard vocabulary of common operational properties
- api-evangelist — upstream source repos this network is built from