One entry for every API, with a source for every fact.

Providers, versions, specifications, and authentication are organized in one entry, with who said what and when clearly stated.

Visit REZICS

Several pale blue sheets overlap on warm white paper. Neat rows of round holes line their edges, with a dark blue sheet underneath.

Six pages

Find an API and follow every version.

Every filter uses a sourced fact from the entry.

Filter by authentication, specifications, version status, and linked MCP servers and skills. Combine supported conditions and browse through every result.

View the directory

Five pale blue sheets stand in a row like gates. A dark slate blue strip passes through a cut in each one.

APIs change versions, names, and availability. Each entry records every change and who reported it.

Eight parts

One API entry, built from eight parts.

Identity always comes first. API Hub selects the other seven from the fifteen shared parts, the same set used for books and anime.

Identity
Renaming an API or changing its identifier does not create a new entry. Older names remain searchable.
Editions
Each version has its own record of what was actually released at the time.
Specifications
Authentication methods, API specifications, and measurement results each include a source and date.
Credits
Providers and maintainers are listed by role, each with their own page.
Ratings
Each rating names the version it covers and the question it answers.
Discussion
Discussions attach to the API as a whole or to a specific version.
Follow
Updates about new versions and withdrawals follow the notification level you choose.
Lists
A list can include APIs, software, and skills, with a note for each item.

Connections

Connect everything built on an API.

Client libraries, MCP servers that wrap an API, skills that use it, and the provider organization each have their own identity. Relationships connect them in both directions.

View connections