Ribbon Health
Ribbon Health (now part of H1) is a healthcare provider data platform offering a REST API for searching provider directories, verifying insurance networks, checking provider availability, and enriching clinical data. The H1 API provides comprehensive data on doctors, insurance plans, procedures, costs, and quality scores across the United States, enabling health plans, providers, and digital health solutions to build accurate provider directories and care navigation tools.
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 Ribbon Health the way a machine reads it — 85 machine-readable artifacts across 10 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 — Ribbon Health scores 54.2/100 (developing), with a separate agent-readiness read of 48/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Ribbon Health
Each block below is one kind of artifact we hold for Ribbon Health. 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 10
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.
Ribbon Health Cost Estimates API
The Cost Estimates API from Ribbon Health — 4 operation(s) for cost estimates.
Ribbon Health Filters API
The Filters API from Ribbon Health — 4 operation(s) for filters.
Ribbon Health Focus Area Endpoints API
The Focus Area Endpoints API from Ribbon Health — 6 operation(s) for focus area endpoints.
Ribbon Health Locations API
The Locations API from Ribbon Health — 5 operation(s) for locations.
Ribbon Health Networks API
The Networks API from Ribbon Health — 1 operation(s) for networks.
Ribbon Health Organizations API
The Organizations API from Ribbon Health — 2 operation(s) for organizations.
Ribbon Health Price Transparency API
The Price Transparency API from Ribbon Health — 8 operation(s) for price transparency.
Ribbon Health Providers API
The Providers API from Ribbon Health — 10 operation(s) for providers.
Ribbon Health Reference Endpoints API
The Reference Endpoints API from Ribbon Health — 13 operation(s) for reference endpoints.
Ribbon Health TINs API
The TINs API from Ribbon Health — 2 operation(s) for tins.
Scroll within the panel for all 10 ·
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.
Ribbon Health Location and Insurance Lookup
Find a practice location by address and name, read its detail record, then list the insurances accepted in that state.
ARAZZORibbon Health Provider Directory Management
Upsert a custom provider record, set its locations and specialties, then confirm the maintained directory entry.
ARAZZORibbon Health Provider Directory Search
Resolve an insurance carrier, find in-network providers by specialty and location, then read the matched provider's detail record.
ARAZZOPricing 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 six things the Kin Score reads for commercial clarity.
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.
Ribbon Health Rate Limits
RATE LIMITSFinOps 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.
Ribbon Health Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Ribbon Health Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Ribbon Health API Rules
SPECTRALJSON Schema 12
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
getConditions
JSON SCHEMAgetCustomLocation
JSON SCHEMAgetCustomLocations
JSON SCHEMAgetCustomProvider
JSON SCHEMAgetCustomProviders
JSON SCHEMAgetEligibility
JSON SCHEMAgetInsurances
JSON SCHEMAgetNetworkAnalysis
JSON SCHEMAgetOrganizations
JSON SCHEMAgetPricingProviders
JSON SCHEMAgetProcedureCostEstimate
JSON SCHEMAgetSpecialties
JSON SCHEMAScroll within the panel for all 12 ·
Examples 52
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Createcustomlocationfilter
EXAMPLECreatecustomproviderfilter
EXAMPLEEditcustomlocationfilter
EXAMPLEEditcustomproviderfilter
EXAMPLEGetclinicalarea
EXAMPLEGetclinicalareas
EXAMPLEGetcondition
EXAMPLEGetconditions
EXAMPLEGetcustominsurance
EXAMPLEGetcustomlocation
EXAMPLEGetcustomlocationtype
EXAMPLEGetcustomlocationtypes
EXAMPLEGetcustomprovider
EXAMPLEGetcustomprovidertype
EXAMPLEGetcustomprovidertypes
EXAMPLEGetcustomspecialty
EXAMPLEGeteligibility
EXAMPLEGetinsurances
EXAMPLEGetlanguages
EXAMPLEGetorganization
EXAMPLEGetpricingcarrier
EXAMPLEGetpricingcarriernames
EXAMPLEGetpricingversioncarrier
EXAMPLEGetprocedure
EXAMPLEGetprocedures
EXAMPLEGetspecialties
EXAMPLEGettreatment
EXAMPLEGettreatments
EXAMPLEPostcustominsurance
EXAMPLEPostcustomlocations
EXAMPLEPostcustomlocationtype
EXAMPLEPostcustomprovidertype
EXAMPLEPostcustomspecialty
EXAMPLEPutcustominsurance
EXAMPLEPutcustomlocation
EXAMPLEPutcustomlocationinsurances
EXAMPLEPutcustomlocationtype
EXAMPLEPutcustomprovider
EXAMPLEPutcustomproviderlocation
EXAMPLEPutcustomproviderlocations
EXAMPLEPutcustomproviderprocedures
EXAMPLEPutcustomproviderspecialties
EXAMPLEPutcustomprovidertype
EXAMPLEPutcustomspecialty
EXAMPLEScroll within the panel for all 52 ·
Security Posture 2
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 Ribbon Health — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
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/ribbon-health · machine-readable index on apis.io