How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

A New Developer Portal, Nine Data Feeds, and an Agent-Ready Network

calendar_today May 1, 2026 person domain apis-io

The APIs.io developer portal has been rebuilt from the ground up. The old version documented two HTTP APIs — search and authentication — in a minimal UI that hadn’t changed since 2023. The new portal is organized around a different model: nine static JSON feeds that expose the full APIs.io network as consumable data, a design that matches the main apis.io site, and an agent-readiness layer baked into every subdomain in the network. Here is what changed and what it means for developers building on top of APIs.io. Nine Feeds, One Network The core of the new portal is nine feeds, each publishing a different slice of the APIs.io catalog as a flat JSON array at a well-known URL. Every feed uses the same compact schema (i, n, d, t, u) so a single fetch-and-index pattern works across all nine. No authentication required. CORS headers are set on every response. Providers — https://apis.io/search-index.json Every organization in the catalog: name, description, tags, API count, and capability count. Currently over 2,500 providers. The ac (API count) and cc (capability count) fields let you filter for providers with published capabilities without fetching their full profile. APIs — https://apis.io/search-index.json Individual API records across all providers. Over 10,000 entries. Each includes a provider slug so you can group APIs by provider client-side without a second request. Capabilities — https://capabilities.apis.io/search-index.json Naftiko capability specs — business workflow definitions that deploy as REST APIs or MCP servers from a single YAML file. Over 750 capabilities across hundreds of providers, spanning CRM, payments, storage, messaging, security, and 20+ other canonical categories. This is the feed to pull if you are building an agent that needs to discover what workflows are available across the catalog. Tags — https://apis.io/search-index.json Every tag used across providers and APIs, with counts for both. Pull this feed to build a live tag cloud, a filter sidebar, or to find which tags have the deepest coverage in the catalog. Schemas — https://apis.io/search-index.json JSON Schema definitions extracted from indexed APIs — over 43,000 schemas. The feed surfaces reusable data model definitions across the ecosystem, useful for tooling that needs to validate or generate code against common API shapes. AsyncAPI — https://apis.io/search-index.json AsyncAPI specifications indexed across providers: event-driven APIs, message channels, and async operations. Over 136 specs, growing as event-driven providers are profiled. JSON-LD — https://apis.io/search-index.json JSON-LD context documents and linked data definitions published by API providers. Over 2,800 documents. Useful for discovery tooling that needs to reason about data types and vocabulary alignment across providers. Rules — https://apis.io/search-index.json Spectral ruleset files for OpenAPI and AsyncAPI linting. Includes rulesets from over 600 providers plus the API Commons base rules — 1,568 rules in total spanning OpenAPI, APIs.json, and provider-specific conventions. Vocabularies — https://apis.io/search-index.json Controlled vocabularies and taxonomy definitions used by API providers for classification and semantic consistency across the catalog. Each feed page in the portal documents the response schema, an example curl request, and JavaScript, MiniSearch, and Python integration snippets. The feeds are also listed in the…

open_in_new Read original post