How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Explorium website screenshot

Explorium

Explorium is the B2B data layer for AI agents and go-to-market systems. Its AgentSource platform is one external-data and enrichment API plus a hosted MCP server, resolving, fetching, enriching and monitoring a company dataset and a people dataset aggregated from 100+ external sources. The REST API at https://api.explorium.ai publishes an anonymous OpenAPI 3.1 description covering 127 operations across two parallel surfaces - v1 (stable) and v2 (beta) - spanning entity matching, filtered fetch with cursor pagination, market-sizing statistics, autocomplete, seventeen company enrichment families and three people enrichment families (single, bulk to 50, and asynchronous to 10,000), AI-powered research, eighteen business and prospect event types delivered over HMAC-signed webhooks, and a shared prepaid credit pool that meters every call. Authentication is an api_key header on REST and OAuth 2.0 on MCP. Explorium is unusually agent-forward at the discovery layer, serving an RFC 9727 api-catalog, a conformant A2A agent card, an MCP server card, an ARD capability catalog, an agent-skills index and llms.txt from its own domain.

agent ready

Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.

Kin Score

API Evangelist profiles Explorium the way a machine reads it — 42 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Explorium scores 65.9/100 (strong), with a separate agent-readiness read of 60/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Composite quality — 65.9/100 · strong
Contract Quality 15.0 / 25
Access Clarity 20.0 / 20
Discoverability 7.6 / 10
Explorium Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Explorium's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/explorium/"
   title="Explorium on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/explorium.svg"
       alt="Explorium Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Explorium

Each block below is one kind of artifact we hold for Explorium. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 22

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Explorium AgentSource MCP Server

Native remote Model Context Protocol server exposing the AgentSource data as 11 agent tools - match-business, fetch-businesses, fetch-businesses- statistics, fetch-businesses-ev...

Explorium Businesses API

Match, fetch, stat, autocomplete, and event/enrollment operations over the Explorium business dataset (v1).

Explorium Credits API

Inspect the shared credit pool that meters all Explorium API usage, including the credit menu and consumption aggregation (v1).

Explorium Prospects API

Match, fetch, stat, autocomplete, and event/enrollment operations over the Explorium prospect dataset (v1).

Explorium Webhooks API

Register, retrieve, delete, and connectivity-test the webhook endpoints that receive Explorium business and prospect event notifications (v1).

Explorium Async Enrichment Jobs API

Submit any v2 company or people enrichment — plus AI research — as an asynchronous job over an uploaded entity-ID dataset.

Explorium Async Jobs API

List, poll, and cancel the asynchronous enrichment jobs that back batch runs of up to 10,000 records (v2).

Explorium Bulk Business Enrichments API

Bulk (multi-record) versions of every v1 company enrichment, processing up to 50 business IDs per request.

Explorium Business Enrichments API

Single-record company enrichments (v1): firmographics, technographics, webstack, website traffic and changes, financial indicators, funding and acquisition, workforce trends, co...

Explorium Custom Enrichments API

Run a customer-specific custom enrichment, single-record or in bulk, by custom enrichment ID.

Explorium Entity ID Datasets API

Upload an entity-ID dataset that asynchronous v2 enrichment jobs run against.

Explorium Healthcheck API

Liveness and payload-size health probes for the Explorium AgentSource service.

Explorium Prospects Bulk Enrichments API

Bulk (multi-record) versions of the v1 people enrichments, processing up to 50 prospect IDs per request.

Explorium Prospects Enrichments API

Single-record people enrichments (v1): contact information, professional profiles, and LinkedIn posts for a matched prospect.

Explorium V2 Autocomplete API

Resolve free-text input to the standardized filter values the v2 search API accepts.

Explorium V2 Business Enrichments API

Synchronous v2 company enrichments — the same seventeen attribute families as v1, on the unified v2 request shape.

Explorium V2 Businesses API

Match, fetch, and stat over the company dataset on the v2 (beta) surface, where bulk and single input share one endpoint.

Explorium V2 Credits API

Credit balance and consumption aggregation on the v2 (beta) surface.

Explorium V2 Prospect Enrichments API

Synchronous v2 people enrichments: contact information, professional profiles, and LinkedIn posts.

Explorium V2 Prospects API

Match, fetch, and stat over the people dataset on the v2 (beta) surface.

Explorium V2 Research API

Run a custom, AI-powered research task over a list of businesses or prospects using a natural-language query or prompt template, grounded in real-time web data (beta).

Explorium Version API

Report the deployed version of the Explorium AgentSource service.

Scroll within the panel for all 22 ·

Open Collections 9

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Scroll within the panel for all 9 ·

MCP Servers 2

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

Published pricing tiers and plan structures.

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Explorium Rate Limits

6 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.

Cost, billing, and metering signals for API financial operations.

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Explorium Authentication

apiKey · 1 scheme

SECURITY

Explorium Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Explorium Trust Center

SOC 2, ISO 27001, GDPR, CCPA

SECURITY

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Explorium Agentic Access

127 operations · 113 acting

127 operations · 113 acting

AGENTIC

Resources

Every other property we hold for Explorium — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Build 3

SDKs, sample code, and the tooling you integrate with

Operate 3

Status, limits, changes, and where to get help

Company 3

The organization behind the API

Other 3

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/explorium · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Explorium, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.