API Hub
One API connects everything built on it.
Client libraries, MCP servers that wrap an API, skills that use it, and its provider organization each have an identity on REZICS, linked by relationships.
Relationships
Relationships have names and direction.
Each relationship identifies its type and each party’s role. It appears on both the API page and the other entry’s page.
Client libraries
A library that calls this API is a software entry with its own versions and dependencies.
Wrapped as an MCP server
A project that wraps it as an MCP server has its own MCP Hub entry, with the project, package, and deployed endpoint recorded separately.
Skills that use it
A skill that uses this API has its own Skill Hub entry, linked back here by a relationship.
Other APIs from the provider
Find the provider’s other APIs from its page.
Find an MCP server from the API, and find the API from the server.
Providers
Providers have their own pages.
An organization or person that provides an API has a public identity, separate from any account. Its APIs, published software, and maintained MCP servers appear on its page by role.
Someone who writes novels, builds software, and maintains APIs has one identity on REZICS.
Related kinds
Three related kinds and the developer site.
Find the other side from either end.
Use one account to find APIs, follow version changes, and share integration experience with others.