What we’re working on and what’s coming next across the APIs.io network. Shipped items move to the Changelog. This is directional, not a commitment to dates.

## In progress - **Quality-aware search ranking** — blending the provider quality rating into search results so first-party, higher-quality APIs surface first. *(shipping — see the [changelog](/changelog/))*
## Next - **Expand brand-ownership coverage** — the first-party signal now prefers brand owners over third-party integrators (see the [changelog](/changelog/)); next is widening the curated parent-company map beyond the initial set of conglomerates and feeding it from the catalog. - **Search relevance tuning** — fold the ranking weights into a feedback loop driven by the zero-result and low-engagement queries we already log, and expand the curated synonym map from real demand data. - **Ranking transparency** — surface why a result ranked where it did (relevance vs. quality contribution) in the developer API response. - **A common support strategy across provider repos** — every listed provider has a repo under [api-evangelist](https://github.com/orgs/api-evangelist/repositories), and people increasingly find those repos and file there. Some of what arrives is for us, some is for the provider, and some is for an upstream open-source project we only catalog. Next is a shared README section on every provider repo that says what the repo is, what we can help with, and where to go for the things we can't — plus routing anything general to the [APIs.io Inbox](https://github.com/api-search/inbox). We would rather be the front line and point people the right way than have a good report go nowhere.
## Later - **Catalog quality lift** — raise more providers out of the Thin/Minimal bands by enriching specs, plans, and operational profiles. - **From declared to verified** — the rating credits what a provider publishes and, from v0.6, checks a growing share of it against the contract they serve. Next is confirming that declared artifacts actually resolve and match what they claim to be, then working toward attestation one artifact class at a time. See the planned dimensions on the [rating page](/rating/). - **Per-artifact search** — first-class relevance ranking within the OpenAPI, AsyncAPI, MCP, Skills, and collections surfaces, not just the unified catalog. - **Personalized / context-aware results** — let agents pass intent (industry, region, artifact type) to bias ranking without extra filtering round-trips.

This page covers APIs.io itself. Work across the wider API Evangelist network — the catalog, the Kin Score, and tooling — is tracked in the open at github.com/api-evangelist/roadmap, and the research that publishes on a cadence has its own production queue.

Want to weigh in on priorities? Open an issue at github.com/api-evangelist/roadmap or email info@apievangelist.com.