Topograph
Topograph is a KYB (Know Your Business) data platform that connects directly to official European and international business registers (35+ countries) for real-time company verification. It provides company data and official documents with source-traceable provenance, ownership-graph analysis across shareholders, ultimate beneficial owners and subsidiaries, cross-border entity resolution, and continuous change monitoring delivered over webhooks. Built for fintechs, neobanks and compliance software vendors, Topograph is exposed as a REST API (x-api-key) with a published MCP server, an x402 agentic-commerce surface, and pay-per-request pricing, backed by SOC 2 Type 2 and ISO 27001:2022 certifications.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Topograph the way a machine reads it — 17 machine-readable artifacts across 7 APIs, 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 — Topograph scores 56.8/100 (developing), with a separate agent-readiness read of 84/100 (agent native). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Topograph
Each block below is one kind of artifact we hold for Topograph. 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 7
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.
Topograph Billing API
The Billing API from Topograph — 1 operation(s) for billing.
Topograph Billing Notifications API
The Billing Notifications API from Topograph — 3 operation(s) for billing notifications.
Topograph Data API
The Data API from Topograph — 3 operation(s) for data.
Topograph Monitors API
The Monitors API from Topograph — 3 operation(s) for monitors.
Topograph Pricing API
The Pricing API from Topograph — 1 operation(s) for pricing.
Topograph Search API
The Search API from Topograph — 1 operation(s) for search.
Topograph Workspaces API
The Workspaces API from Topograph — 3 operation(s) for workspaces.
Scroll within the panel for all 7 ·
Arazzo Workflows 3
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOMonitor a company for register changes
Start monitoring a company, review its change logs, then stop monitoring.
ARAZZOResolve a company and retrieve KYB data
Search for a company, request its data and documents, then poll for the result.
ARAZZOMCP Servers 1
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.
topograph-mcp.yml
MCP SERVEREvent 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.
Topograph Monitoring Webhooks
ASYNCAPISecurity Posture 3
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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.
Resources
Every other property we hold for Topograph — 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.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 9
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 9 ·
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/topograph · machine-readable index on apis.io