API Hub
Every score says which version it covers.
A rating for an API states the question and version. Counts and distributions appear beside the score. Discussion, lists, and communities also center on the same entry.
Ratings
Five details define a score.
Example: “Are the docs clear?” on a five-point scale, for version three, rated by everyone on the site.
Question
What is being rated. Scores for different questions are never combined.
Scale
The scale and what each score means are stated in advance.
Subject
Which version is being rated. Its score does not count toward another version.
Group
The group that rated it is named beside the score.
Count and distribution
Every score includes the number of ratings and their distribution. When there are too few ratings, no average is calculated.
Discuss integration issues under the version where they occurred. When a version changes, its discussion stays with the old version.
Lists
Put everything a project uses on one list.
Lists can mix kinds. Group APIs, client libraries, MCP servers, and skills, with a note for each item. Set the list’s visibility, arrange it, and export it.
- API
Weather data API
Source of forecast data
- API
Map tiles API
Base map for the display
- Software
Client library
Call the weather data API from code
- MCP server
Weather MCP server
Let an AI agent check the weather
- Skill
Trip planning skill
Adjust each day’s plan to the weather
Example: Example list for a fictional project. Names are illustrative.
Realm and Zone
Build a Zone for a kind of API.
A community can start a Realm, set its own rules, and interpret facts in entries its own way. It can also build a Zone as a dedicated API directory site using the same graph of data.
Every rating and discussion names its subject.
Use one account to find APIs, follow version changes, and share integration experience with others.