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.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Ribbon Health the way a machine reads it — 97 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 — Ribbon Health scores 61.5/100 (strong), with a separate agent-readiness read of 32/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
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Ribbon Health'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/ribbon-health/"
title="Ribbon Health on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ribbon-health.svg"
alt="Ribbon Health Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/ribbon-health/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/ribbon-health/"
title="Ribbon Health on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/ribbon-health/card.svg"
alt="Ribbon Health Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
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 11
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.
Ribbon Health Price Transparency v2 API
The Price Transparency v2 API from H1 (Ribbon Health) — 7 location-first operations for negotiated-rate shopping. Prices are scoped to a facility rather than to a provider, carr...
Scroll within the panel for all 11 ·
Open Collections 11
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).
API Collection
OPEN COLLECTIONribbon-health Cost Estimates API
OPEN COLLECTIONribbon-health Cost Estimates Filters API
OPEN COLLECTIONribbon-health Cost Estimates Focus Area Endpoints API
OPEN COLLECTIONribbon-health Cost Estimates Locations API
OPEN COLLECTIONribbon-health Cost Estimates Networks API
OPEN COLLECTIONribbon-health Cost Estimates Organizations API
OPEN COLLECTIONribbon-health Cost Estimates Price Transparency API
OPEN COLLECTIONribbon-health Cost Estimates Providers API
OPEN COLLECTIONribbon-health Cost Estimates Reference Endpoints API
OPEN COLLECTIONribbon-health Cost Estimates TINs API
OPEN COLLECTIONScroll within the panel for all 11 ·
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 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.
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.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 2
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
This is an independent, third-party profile of Ribbon Health, 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.