This is the running log of everything we ship across the APIs.io network — the search ranking, the provider catalog and ratings, the API and MCP server, and the network sites. Newest first. What’s planned next lives on the Roadmap.
Stack — build a watchlist, export it as apis.yml
New top-level Stack page. Type-ahead your way through the catalog, add the providers you actually depend on, and watch them in one table: Kin Score and band, week-over-week movement, how far each has moved since you added it, agent readiness, API count, published resources, and access model — plus a rollup with the stack average and its weakest link.
Export the whole stack as an APIs.json 0.21 apis.yml (or JSON, or
straight to the clipboard). Every provider carries its rating and agent-readiness blocks, its
published resources — OpenAPI, MCP server, agent skills, rules, scopes, security, changelog — and an
include pointer to the provider's own apis.yml. Upload one back to restore
a stack on another machine; a single provider's own apis.yml works as an import too.
There is no account and nothing is sent to APIs.io: the stack lives in one first-party cookie in
your browser, holding only provider slugs. Clear your cookies and it's gone — which is why the
apis.yml download is the durable copy. About and Add API moved from the
top nav down to the footer to make room.
First-party (brand-owner) ranking signal
Quality rating was standing in for ownership; now search knows who owns a brand. A provider is the canonical owner of its own name plus any sub-brands it operates (e.g. Meta owns WhatsApp, Instagram, Messenger; Microsoft owns GitHub). When your search names a brand, that owner's first-party API gets an explicit bonus over third-party integrators — so "whatsapp" leads with the official WhatsApp APIs, not the dozens of tools that merely connect to WhatsApp. Non-brand queries (payments, weather) are unaffected.
Quality- and ownership-aware search ranking
Search results were ordered by text relevance alone, so a query like "send WhatsApp message" buried the first-party WhatsApp Business API under a pile of lower-quality third-party matches. Ranking now blends relevance with the provider quality rating:
- Field boosting — a match in an API's name or tags now outweighs a passing mention in its description, so the API actually named after what you searched rises to the top.
- Quality-weighted ordering — among the APIs that match, the composite quality rating (Exemplar → Minimal) decides the order, so higher-quality, first-party APIs surface first. "send WhatsApp message" now returns the WhatsApp Business API at #1.
- Strict matches still rank ahead of synonym-broadened recall, and all weights are tunable without a code change.
Public changelog and roadmap
Added this changelog and a public roadmap, both linked from the site footer, so changes and what's coming next are tracked in the open.
Have a request or noticed something off? Open an issue at github.com/api-evangelist/roadmap or email info@apievangelist.com.