APIVerve

An agent-native API marketplace exposing 300+ (367+ enumerated) ready-made REST APIs behind a single API key with a uniform JSON envelope. Offers REST, an alpha GraphQL gateway, OpenAPI + Postman contracts, a self-hosted apis.json, an llms.txt, and a hosted remote MCP server that turns the whole catalog into agent tools.

APIVerve publishes 31 API contracts indexed on the APIs.io network, including AI/Computer Vision API, Astrology API, Calendar API, and 28 more. Tagged areas include API Marketplace, REST, JSON, GraphQL, and OpenAPI.

APIVerve’s developer surface includes authentication, documentation, API reference, getting-started guide, support, engineering blog, pricing, and 31 more developer resources.

🌐 Visit website 📡 Source on GitHub

60.8/100 strong ▬ flat Agent 50/100 agent ready Front door AI 2/6 trace Full breakdown ↓
scored 2026-10-09 · rubric v0.23.0

1 published contract 1 MCP Servers

API Marketplace REST JSON GraphQL OpenAPI Postman MCP llms-txt Agent-Native APIKeys IP Geolocation DNS WHOIS SSL Email Verification Phone Validation Exchange Ratesmetals pricesWeather Geocoding Text Processing Developer Tools

Kin Score

Kin Score How this is scored →
scored 2026-10-09 · rubric v0.23.0

Composite quality — 60.8/100 · strong

Contract Quality 9.9 / 19

Developer Ergonomics 12.8 / 15

Access Clarity 11.4 / 15

Operational Transparency 4.1 / 10

Contract Governance 0.4 / 9

Discoverability 5.6 / 8

Regulatory Posture 4.9 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 50/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/apiverve: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 6

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

DNS