HealthSherpa
HealthSherpa is the leading ACA (Affordable Care Act) health insurance quoting and enrollment platform, and was the first company to partner with CMS to offer Enhanced Direct Enrollment (EDE) for agents. Its developer surface, HealthSherpa ONE (one.healthsherpa.com), exposes a public OpenAPI 3.1 REST API for on- and off-exchange ACA plan quoting, county/issuer/provider reference lookups, agent and self-service enrollment sessions, and an approval-gated direct enrollment API covering the full off-exchange (ICHRA) application lifecycle — create, update, submit, cancel, terminate, supporting-document upload, and payment redirect. Authentication is a single x-api-key header; enrollment writes support Idempotency-Key with 24-hour retention. Separate ICHRA and Medicare Partner APIs provide QuoteConnect/EnrollConnect, deeplinked enrollment, and webhooks. HealthSherpa publishes first-party Agent Skills, an llms.txt, and vibe-coding prompts for agents.
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 HealthSherpa the way a machine reads it — 11 machine-readable artifacts across 5 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 — HealthSherpa scores 46.3/100 (developing), with a separate agent-readiness read of 80/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 HealthSherpa
Each block below is one kind of artifact we hold for HealthSherpa. 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 5
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.
HealthSherpa Enrollment Sessions API
The Enrollment Sessions API from HealthSherpa — 1 operation(s) for enrollment sessions.
HealthSherpa Enrollments API
The Enrollments API from HealthSherpa — 7 operation(s) for enrollments.
HealthSherpa Quotes API
The Quotes API from HealthSherpa — 1 operation(s) for quotes.
HealthSherpa Reference API
The Reference API from HealthSherpa — 3 operation(s) for reference.
HealthSherpa Utility API
The Utility API from HealthSherpa — 1 operation(s) for utility.
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.
healthsherpa-mcp.yml
MCP SERVERAgent Skills 1
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
ichra-platform-integration
AGENT SKILLEvent 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.
Healthsherpa Ichra Webhooks
ASYNCAPISecurity 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 HealthSherpa — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
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/healthsherpa · machine-readable index on apis.io