io.apis/apis-io
io.apis/apis-ioRead-only MCP server over the APIs.io catalog — discover APIs, providers, tags & artifacts.
Tools · 133
START HERE. Federated overview of the APIs.io catalog for a query: the top matching APIs, providers, AND tags in one call, each with its total match count. Filter by tags, artifact types, industry, re…
Curated APIs that are SAFE TO EXPERIMENT WITH — no key (or an instant, free, self-serve key), no cost, and no real-world side effects. Free, and deliberately so: this is where you start if you are new…
Paginated, sortable list of APIs across providers — filter by tag, provider, artifact type, industry, region, or rating band. Use apis_io_search first for a cross-type overview.
Full detail for one API by aid (provider:api-slug); set include=["content"] to inline artifact bodies. Results carry `next`: the sub-resources that exist for this entity and the exact tool call that r…
Paginated, sortable list of providers — filter by text, tag, artifact type, industry, region, rating band, access model (pricing/onboarding/try_now/public), or DIRECTION (accepts_writes/min_acting — w…
Full detail for one provider: profile, rating, and the APIs it publishes. The heavy `collections` and `common` sections are omitted by default (their counts are still reported) — pass view=full for th…
Paginated, sortable list of tags in the taxonomy. Filter by `axis` to separate MARKETS (a business someone is in) from CAPABILITIES (the name of a resource in somebody's OpenAPI) — the single most use…
One tag: its metadata, neighbor tags, and a top sample of its providers and APIs (with totals). `provider_count` counts companies that classify THEMSELVES here; `api_provider_count` counts the ones re…
Browse industry verticals; sort by provider/API count.
One industry: metadata + a top sample of its member providers (ranked, with the total). Use find_providers?industry=slug for the full list, or view=full here. Results carry `next`: the sub-resources t…
Browse geographic regions; sort by provider/API count.
One region: metadata + a top sample of its member providers (ranked, with the total). Use find_providers?region=slug for the full list, or view=full here. Results carry `next`: the sub-resources that …
Browse the country dimension — the finest of the four place taxonomies, and the one a buyer usually names ("who is in Germany"). Peer to find_industries / find_regions / find_areas. Search by text; so…
One country: metadata, counts, and a top sample of member providers (with the total). Use find_providers?country=slug for the full ranked list, or view=full here.
Browse the API Evangelist areas taxonomy (authentication, webhooks, payments, …) — curated, scored provider indexes. Search by text; sort by provider count.
One area: metadata, its dedicated site link, and a top sample of member providers (with the total). Use find_providers?area=slug for the full list, or view=full here. Results carry `next`: the sub-res…
Browse every OpenAPI `x-` specification extension harvested across the catalog, with the provenance the OpenAPI Initiative registry does not carry: who publishes it, in how many documents, where in th…
One OpenAPI specification extension: its publishers, occurrence and document counts, where it appears, and the value shapes observed. CHECK is_api_evangelist BEFORE treating a key as provider-originat…
Ranked ratings leaderboard — filter by band, score range, trend, or facet threshold. Sort by composite (default), delta (biggest gainers), or any quality facet (governance, security, …) to rank provid…
One provider's full rating breakdown (composite, band, trend, six facets).
START HERE for market-level questions. Every scored population of providers in the catalog — tags, industries, regions, areas and VC portfolios — as one browsable index. Filter by kind, minimum popula…
One cohort: its identity, its population, and the full member roster with each provider's Kin Score and agent readiness. Understanding plan. The analysis parts (stats/rankings/scores/capabilities) nee…
START HERE for capability-map questions. The 1,500+ tag groups the catalog computes — sets of tags that demonstrably travel together across providers (Cards, Logistics, Wealth Management, Observabilit…
One tag group: its member tags and the full provider roster resolved from the catalog, each with Kin Score and agent readiness. Filter the roster by industry, region, country or area. Free; the DISTRI…
The member tags of one tag group, each joined to its catalog record — provider count, api count, tag quality band and composite. Use it to see what a group is actually made of before trusting the grou…
UNDERSTANDING — the DISTRIBUTION for a whole market: Kin Score mean/median/min/max/stdev, agent-readiness spread, band split, per-facet averages, and artifact adoption rates. This is the market-stats …
UNDERSTANDING — the leaderboard for a market, on TWO axes: rank by Kin Score composite AND rank by agent readiness. The two orders differ, and the gap between a provider's two ranks is usually the sto…
UNDERSTANDING — facet-level scores for every member of a cohort, each with the cohort average and the delta against it. A 60 in governance means nothing until you know the market sits at 45; this is t…
UNDERSTANDING — CATALOG-WIDE operation search: which providers expose a path matching your terms. "Who has a POST /refunds" had no answer before this — tags are what a company says about itself, a pat…
UNDERSTANDING — every provider publishing at least one operation marked deprecated in its own OpenAPI, ranked by how many. The lifecycle view of the catalog: 8,297 deprecated operations across 681 pro…
UNDERSTANDING — the SET-LEVEL time series: how a whole market's Kin Score and agent readiness moved, build by build. There was a per-provider series and a whole-dataset licence and nothing between the…
UNDERSTANDING — what a whole market gets WRONG: the agent-readiness checks its members most commonly fail, ranked by what fixing each would move the cohort mean. The inverse of gap_analysis, which say…
UNDERSTANDING — what every member of a cohort actually publishes: artifact counts by type plus the agent-readiness dimensions each one satisfies. The capability matrix behind a market report. Large co…
UNDERSTANDING — two markets side by side on one rubric: "is US payments further along than UK banking?" Returns both distributions plus the deltas on score, agent readiness, every facet and every adop…
Every operation a provider exposes, across all of its OpenAPIs — method, path, operationId, summary, which API it belongs to, and whether it is deprecated. The shortcut for "what can I actually call h…
Every MCP tool a provider ships, with the operation each one wraps and its auth. Reports provenance per tool: `first-party` means the provider publishes that server, `derived` means API Evangelist gen…
Every JSON Schema a provider publishes — the data shapes their API works in, in one list, without walking their artifacts. Free.
UNDERSTANDING — one provider's score broken into its facets (discoverability, contract quality, governance, operational transparency, developer ergonomics, commercial clarity) plus any regulatory regi…
EXPLORE — the agent-readiness dimensions and standalone score for ONE provider (spec presence, MCP server, auth clarity, idempotency, error semantics, rate-limit signal, well-known catalog, consent id…
UNDERSTANDING — the agent-readiness leaderboard across the whole catalog. Rank providers by agent readiness, and filter to those that DO satisfy (has) or do NOT satisfy (missing) specific dimensions —…
UNDERSTANDING — diffusion: for each agent-readiness dimension, how many scored providers satisfy it, out of how many, as a share. The denominator every "the agent web is/is not here yet" claim needs a…
START HERE for "what can a business do with these APIs". The business-capability model — 333 top-level capabilities across 28 industries — with how many catalog providers reach each one. Defaults to c…
One business capability: its definition, its sub-capabilities, the external authorities it cites, and WHICH catalog providers reach it with their ratings. Accepts a slug or a BC id (e.g. "payments-car…
UNDERSTANDING — the evidence behind a capability. Every edge that lands on it: the provider, the tag, the exact OpenAPI file, a calibrated confidence, and the QUOTED FRAGMENT OF THE PROVIDER'S OWN CON…
UNDERSTANDING — what ONE vendor's published APIs let a business DO, rolled up by capability, with the tag-level evidence under each. Answers "what is this vendor actually for" from its own contracts r…
What one provider publishes, counted by artifact type, with the agent dimensions it satisfies. Free — it is a fact about their own public surface. NOTE: this is artifact counts, NOT business capabilit…
How a provider's score was established, part by part: first-party (they published it), verified (we fetched and confirmed it), or derived (we inferred it). Free — the basis for a claim should never si…
UNDERSTANDING — the rubric: bands, facet weights, trend thresholds, so an agent can interpret any score. Moved behind the paywall with the ratings data on 2026-08-31.
Find artifacts of ANY one type across the catalog — the cross-type entry point. Each type also has a dedicated find_<type> tool (find_mcp, find_rules, find_scopes, …) with sorts and filters unique to …
UNDERSTANDING — Compare 2+ providers side by side: composite/band, per-facet leaders, and an artifact-coverage matrix.
UNDERSTANDING — For each provider: high-value artifacts it lacks (MCP, Arazzo, Rules, Skills…), what its peers commonly publish but it lacks, and its score vs the peer median — plus stack-level gaps a…
UNDERSTANDING — What changed in the catalog since a date: providers added/updated, plus rating movement measured FROM THAT DATE — each provider's current score against its score at the first scored sn…
Design an API stack — the best-rated catalog provider per capability, assembled into a stack. The Understanding preview is the top pick per capability; the full answer adds alternatives, per-pick arti…
Every API one provider publishes, as a page you can filter — the provider's own catalog rather than the whole network's. Prefer this over find_apis with a `providers` filter when you already know the …
Every artifact a provider publishes — provider-level (MCP, security, scopes, rules, agentic-access) and per-API (OpenAPI, Arazzo, overlays, reference docs) — grouped by type with counts. by_type_count…
One API's artifacts grouped by type (by_type_counts is the full summary); pass `type` to scope the list to one type (synonym-aware: MCP matches MCPServer), include=["content"] to inline the bodies.
An API's primary OpenAPI reference (url) — the top agent intent; set include=["content"] to inline the spec body.
A getting-started view for a provider — website, portal, signup, docs, authentication, base URLs, and first steps assembled from its registered links.
Providers similar to a given one (alternatives) by shared tags, industry, region, and artifact coverage.
APIs similar to a given one ("more like this") by shared tags.
UNDERSTANDING — Top-rated providers in an industry vertical.
UNDERSTANDING — Top-rated providers in a region.
UNDERSTANDING — Top-rated providers in one country. Membership is derived and partial, so read the ranking as "the best of what we have placed there", not a national league table.
UNDERSTANDING — Top-rated providers in a curated API Evangelist area.
UNDERSTANDING — A provider's REAL score time series: one point per scored build (composite + agent readiness on each date), plus a summary of the movement over the window — first/last, net change, dir…
UNDERSTANDING — The biggest rating movers (up and down) since the previous scoring build.
OWNER — The weekly "what's worth writing" rollup: ranked story leads from the demand map crossed with rating movement — unmet demand (searched, no result), risers/fallers, and hot-but-thin capabilitie…
INFLUENCE — the ranked, costed, gated punch list for one provider you own. Every agent-readiness check with points still on the table (exact — these are real per-check results, each with what satisfie…
INFLUENCE — what blocks the next agent-readiness band, GATES BEFORE POINTS. Some bands are unreachable on score alone: agent-native requires idempotency AND a stable error envelope regardless of how m…
INFLUENCE — project a set of fixes onto a provider's agent-readiness score and band before doing the work. Re-applies the band gate to the PROJECTED state, so it will tell you when buying points still…
INFLUENCE — ask to claim a listing as yours. Returns 202 with a token and the hosts it will be checked against: publish it as a DNS TXT record, or as a file at /.well-known/apis-io-challenge, and leav…
INFLUENCE — REQUEST an artifact you are being marked down for not having: apis-json, agent-card, mcp (one tool per operation you already publish), arazzo, rules (a Spectral ruleset scoped to your own …
INFLUENCE — tell us about an artifact you publish, rather than waiting for us to find it. Returns 202; a person fetches it, checks it and re-runs the pipeline against it. Track it with check_status.
INFLUENCE — propose corrections to what we say about you: name, description, url, industries, tags. Returns 202 and is applied by a person — an API that let an owner rewrite their own description unre…
INFLUENCE — "you say we lack X, here it is." Send the claim in words and a URL that evidences it. Returns 202; a person fetches your evidence, checks it against what we hold, and emails you either way…
INFLUENCE — ask to be shown less, or not at all. `restricted` keeps a name, a description and a link to your own site, unrated and out of every ranked view; `delisted` removes you entirely. Returns 20…
INFLUENCE — be told when a listing you care about moves: score changes, band changes, or a check closing. Registration only — the scoring pipeline sends the mail, this records what you want to hear ab…
INFLUENCE — the listings you are watching, with the events registered for each and when you started. The read half of watch_listing: call it before registering another, so you neither duplicate a watc…
INFLUENCE — stop watching a listing. Takes effect immediately and removes the registration outright; there is no paused state. Removing a watch that was never registered is not an error.
INFLUENCE — ask APIs.io to (re)check something. Use it when a listing is wrong or stale, when a score looks incorrect, or to get a company profiled that is not in the catalog yet. A check can target a…
INFLUENCE — the status of a check request by id: queued, in_review, running, done, rejected or needs_info, with any notes shared by the reviewer. The id identifies the request, but the Influence plan …
FREE, no account — tell the catalog what you looked for and could not find. The consumer door (roadmap#166): a gap report is how the catalog learns what to add next, and a person reads the queue. One …
INFLUENCE — the check requests you filed, newest first. Requires a key or login — an anonymous caller has no identity to scope a list to, and should read a single request with check_status instead.
LICENCE (sold on the Influence plan) — the WHOLE dataset, not a 100-row page: `ratings` (every rated provider with facets, trend, rubric + provenance), `providers` (the catalog with coverage + score),…
UNDERSTANDING — Valuable artifact types (MCP, Arazzo, Rules, Skills…) commonly missing across a whole industry — where the vertical is under-served.
UNDERSTANDING — Export a designed capability stack as an adoptable APIs.json document (with an Arazzo hint) the team can commit.
UNDERSTANDING — the Insights root: how many companies are profiled, over how many quarters, and the top investment dimensions across the whole set. Read this FIRST — it tells you the size and vintage …
Browse profiled companies (Fortune 1000) by name or industry; ranked by overall technology-readiness signal. `industry` takes an insights industry NAME from insights_industries (e.g. "Industrial") — a…
Cross-section ranking of the 40 tracked investment dimensions (AI, cloud, governance, security, …) by how many profiled companies show signal. Understanding plan.
Services, tools, or standards ranked by how many companies adopt them across the profiled set. Understanding plan.
UNDERSTANDING — the demand-side industry rollup: the sectors the profiled companies fall into. Each row carries TWO counts and they answer different questions: `company_count` is the research roster, …
UNDERSTANDING — Full demand-side profile for one company: 40-dimension readiness scores, adopted stack, and per-quarter history.
UNDERSTANDING — A company's weakest investment dimensions — where it is thin and a vendor could sell in.
UNDERSTANDING — The supply↔demand join: apis.io providers whose product appears in a company's adopted stack, ranked by rating.
UNDERSTANDING — Find venture-capital firms by name, thesis tags, or category. Each carries a network-matched, rated portfolio graph. Sort by portfolio_on_network (default), portfolio_total, portfolio_…
UNDERSTANDING — One VC firm: identity, fund facts, and portfolio summary (totals, band distribution, average rating). Pass view=full to inline the whole portfolio. Understanding plan.
UNDERSTANDING — A VC firm's portfolio companies, each matched to the network and rated. Filter publishes_api=true (companies that actually ship an API — about 37% of any book), in_network=true, band, …
UNDERSTANDING — The reverse portfolio edge: which VC firms in the network back a given provider/company (by slug). The investor COUNT is free; the named firms need Understanding.
Resolve ANY identifier — website URL, domain (stripe.com), or GitHub org (github.com/stripe) — to the apis.io provider it belongs to. Use this when you have a URL, not a slug. Understanding plan.
One call, pick your field groups — resolves a slug OR any identifier and returns exactly the groups you ask for, instead of chaining get_provider + get_provider_rating + get_provider_artifacts + get_p…
UNDERSTANDING — Persist the current search criteria as a named saved search you own, so you can re-run it and get net-new results later. Criteria use the same filters as apis_io_search. Requires an ap…
UNDERSTANDING — the workspace root: which plan you are on, how many saved searches and lists you hold, and where each lives. Answers "what do I have here and what can I afford" in one call, so an agen…
UNDERSTANDING — List the saved searches you own (name, criteria, when last run, how many matches are tracked).
UNDERSTANDING — Re-run one of your saved searches against the live catalog and return current matching providers.
UNDERSTANDING — What is NEW for a saved search since you last checked: providers that newly match your criteria. Advances the delta cursor, so each call reports only what changed since the previous ca…
UNDERSTANDING — Delete a saved search you own.
UNDERSTANDING — Create a named, persistent list (a shortlist / stack you own) of providers or APIs. Requires an apis.io API key.
UNDERSTANDING — List the lists/shortlists you own.
UNDERSTANDING — Get a list you own, with each member resolved to its current name, band, and score.
UNDERSTANDING — Add providers/APIs (by slug or aid) to one of your lists.
UNDERSTANDING — Delete a list you own.
OpenAPI specifications across the catalog. The REST contract. get_openapi returns one API's primary spec with optional inlined body. Filter by q / tags / providers; include=["content"] inlines bodies.…
AsyncAPI (event-driven) specifications across the catalog. Event/streaming APIs. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
AsyncAPI event channels across the catalog. Individual event channels (topics/streams). Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
GraphQL schemas across the catalog. GraphQL type systems. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
Arazzo workflows across the catalog. Multi-step API workflows chaining operations. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
MCP servers across the catalog. Model Context Protocol servers a provider offers to agents. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search…
Agent Skills across the catalog. Packaged agent skills. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
Spectral governance rulesets across the catalog. API design/linting rulesets. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
OAuth scope catalogs across the catalog. The OAuth scopes an API defines. Understanding plan. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type sear…
Security artifacts across the catalog. Authentication, domain security, VDP, trust center. Understanding plan. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts fo…
Pricing plans across the catalog. An API's pricing tiers. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
Rate-limit policies across the catalog. Declared throttling policies. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
FinOps / billing models across the catalog. How usage is metered and billed. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
Postman / Open collections across the catalog. Runnable request collections. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
JSON-LD contexts across the catalog. Linked-data vocabularies. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
JSON Schemas across the catalog. Standalone data schemas. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
JSON Structures across the catalog. Data structures behind an API. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
Example payloads across the catalog. Real request/response examples. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
Postman collections across the catalog. Postman-format collections (by reference). Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
APIs.json indexes across the catalog. The APIs.json discovery documents themselves. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
Report something wrong with a result: wrong data, a filter that did not filter, a ranking that put off-topic results first, a number you could not reproduce, or an answer that was useless for your tas…
Report that the catalog has a provider WRONG — a wrong website, a wrong logo, APIs that are not theirs, a count that does not match what they ship, a score computed from any of those. Free, always: co…
Resources · 7
Service root — network-wide artifact counts.
apis://catalog
The scoring rubric — bands, facet weights, trend thresholds — so an agent can interpret any provider score.
apis://ratings/rubric
The apis.io llms.txt index — a machine-readable map of the network for grounding.
apis://llms.txt
UNDERSTANDING — Recent catalog changes (last 30 days): providers added/updated plus rating movement, as an attachable feed.
apis://changes
The agent-readiness vocabulary — every dimension id, what it measures and what it is worth. Attach it before reading any readiness score, so the dimension ids in the answer mean something and can be p…
apis://agent-readiness/dimensions
UNDERSTANDING — Operations providers across the catalog have marked deprecated, grouped by provider. Worth holding while designing an integration: the point of the roll-up is the providers you had no …
apis://deprecations
UNDERSTANDING — Your workspace root: plan, saved-search and list counts, and where each lives. Requires an apis.io API key — a keyless read returns the auth error rather than an empty workspace, which…
apis://workspace
Prompts · 36
Find an API for a task or use case, ranked with links.
Explain one API artifact (OpenAPI, AsyncAPI, Arazzo, rules, …) and how to use it.
Summarize what one provider offers — their APIs, artifacts, and links.
Explore a tag — what it covers, its scored neighbors, and its strongest providers.
UNDERSTANDING — Find every provider whose API actually exposes a given operation, by path rather than by tag.
UNDERSTANDING — Check what you depend on for deprecated operations, before a provider retires one under you.
UNDERSTANDING — Read a set of vendors as BUSINESS CAPABILITIES: what this stack lets the business actually do, evidenced from each vendor's own contracts, and where the holes are.
UNDERSTANDING — Design a recommended API stack for a team, domain, or company: a scored provider per capability, exportable as APIs.json.
UNDERSTANDING — Build a scored vendor shortlist for one capability, with tradeoffs.
Onboard a provider end-to-end: pull its OpenAPI + onboarding, then produce first-integration steps.
Assess whether an API is ready to adopt — artifacts present, rating, and what is missing.
INFLUENCE — Inventory, score, and gap a set of providers: what they publish, how they rate, and what they lack.
INFLUENCE — Find and compare alternatives to a provider for a migration decision.
UNDERSTANDING — Assemble the providers, MCP tools, and skills an agent needs for a job.
UNDERSTANDING — Monitor a chosen set of providers for catalog and rating movement.
INFLUENCE — Assess a company's technology readiness from the demand-side data: where it invests, where it is thin, and which apis.io providers are already in its stack.
Find the best-in-class APIs for an artifact quality — the most governed, the most MCP-ready, the most granular OAuth, and so on.
Read your provider rating and turn it into a ranked, do-this-next punch list.
Check whether an API/provider is ready for AI agents — MCP, Skills, llms.txt, OpenAPI, auth clarity.
INFLUENCE — For a provider you own: your rating, the gap, and the ranked plan to close it.
INFLUENCE — Run a listing you own end to end: claim it, see the gates, get artifacts drafted, submit what you publish, and watch the score.
INFLUENCE — Find which Fortune-1000 companies to approach for your API, and where they are thin.
INFLUENCE — Benchmark a provider against its closest peers, facet by facet.
INFLUENCE — Read a whole population: how it scores, how it has moved, and the specific checks it fails.
INFLUENCE — Scaffold a data-report on the state of a category: ratings, movement, and demand.
UNDERSTANDING — A narrative briefing on the biggest rating movements, with the why behind each.
Map where the market is investing — the demand-side landscape for a topic.
UNDERSTANDING — The ranked quality leaderboard for one industry, region, area, tag, or vc portfolio.
OWNER — What is worth writing about this week: rising demand x thin coverage x rating movement.
UNDERSTANDING — What moved across the catalog and why it matters.
Find where demand outruns catalog coverage — the gaps worth filling.
Explore an industry vertical — its providers, leaders, and coverage.
Explore an API Evangelist topic area and its member providers.
Explore a geographic region — its providers, leaders, and coverage.
UNDERSTANDING — What you have saved here, what is new since you last looked, and what to do next.
Explain how apis.io scores an API — so you can cite or defend a rating.
Similar MCP servers embedding-nearest
How to use
Add to your Claude Desktop / Cursor / Cline MCP config:
{
"mcpServers": {
"io.apis/apis-io": {
"url": "https://apis.io/mcp",
"transport": "streamable-http"
}
}
}