Verato
Verato is a healthcare identity company whose Universal Identity Platform (MDM Cloud) resolves and matches records for people, providers, and organizations against a proprietary nationwide referential database to create and maintain a single source of truth (golden record). Verato publishes a developer portal with three RESTful JSON web-service APIs — the Person API (patient/consumer identity, demographics search, linking, merging, households, relationships), the Organization API, and the Provider API (Practitioner Type-1 and Health Facility Type-2 identities) — used for enterprise master data management, patient matching, provider data management, identity resolution, and downstream data enrichment. APIs authenticate with HTTP basic credentials over mutual TLS, with keys provisioned per tenant by a Customer Success Manager.
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 Verato the way a machine reads it — 25 machine-readable artifacts across 20 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 — Verato scores 50.4/100 (developing), with a separate agent-readiness read of 69/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 Verato
Each block below is one kind of artifact we hold for Verato. 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 20
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.
Verato AddRelationshipService API
The AddRelationshipService API from Verato — 1 operation(s) for addrelationshipservice.
Verato CreateDataSource API
The CreateDataSource API from Verato — 1 operation(s) for createdatasource.
Verato DeactivateSourceWs API
The DeactivateSourceWs API from Verato — 1 operation(s) for deactivatesourcews.
Verato DeleteRelationshipService API
The DeleteRelationshipService API from Verato — 1 operation(s) for deleterelationshipservice.
Verato DeleteSourceIdentity API
The DeleteSourceIdentity API from Verato — 1 operation(s) for deletesourceidentity.
Verato DemographicsQuery API
The DemographicsQuery API from Verato — 2 operation(s) for demographicsquery.
Verato DemographicsSearch API
The DemographicsSearch API from Verato — 2 operation(s) for demographicssearch.
Verato HouseholdQuery API
The HouseholdQuery API from Verato — 1 operation(s) for householdquery.
Verato IdentityIdQuery API
The IdentityIdQuery API from Verato — 2 operation(s) for identityidquery.
Verato LinkIdentities API
The LinkIdentities API from Verato — 1 operation(s) for linkidentities.
Verato MergeIdentities API
The MergeIdentities API from Verato — 1 operation(s) for mergeidentities.
Verato NativeIdQuery API
The NativeIdQuery API from Verato — 2 operation(s) for nativeidquery.
Verato PostIdentity API
The PostIdentity API from Verato — 2 operation(s) for postidentity.
Verato ReactivateSourceWs API
The ReactivateSourceWs API from Verato — 1 operation(s) for reactivatesourcews.
Verato RestoreSource API
The RestoreSource API from Verato — 1 operation(s) for restoresource.
Verato SearchNotifications API
The SearchNotifications API from Verato — 1 operation(s) for searchnotifications.
Verato SearchRelationshipsService API
The SearchRelationshipsService API from Verato — 1 operation(s) for searchrelationshipsservice.
Verato SoftDeleteSource API
The SoftDeleteSource API from Verato — 1 operation(s) for softdeletesource.
Verato UnlinkIdentities API
The UnlinkIdentities API from Verato — 1 operation(s) for unlinkidentities.
Verato UnmergeIdentities API
The UnmergeIdentities API from Verato — 1 operation(s) for unmergeidentities.
Scroll within the panel for all 20 ·
MCP 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.
verato-mcp.yml
MCP SERVERSecurity 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.
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 Verato — 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 2
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 5
Pagination, idempotency, versioning, errors, and events
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/verato · machine-readable index on apis.io