Yuzu Health
Yuzu Health is a technology platform for building and operating custom, self-funded health plans end to end - plan design, member enrollment and eligibility, in-house medical and pharmacy claims adjudication, benefit accumulators, EOBs, ID cards, and payments - without legacy TPA systems. Its public REST API (bearer-JWT API keys, URL-prefix versioning v1/v2/v3, cursor pagination) exposes 76 operations across members, sponsors, groups/policies, coverages, claims, enrollment, benefits, care events, and accumulators, plus a white-label portal. Yuzu is backed by General Catalyst and Menlo Ventures.
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 Yuzu Health the way a machine reads it — 15 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 — Yuzu Health scores 51.8/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 Yuzu Health
Each block below is one kind of artifact we hold for Yuzu 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.
Yuzu Health Accumulator (Experimental) API
The Accumulator (Experimental) API from Yuzu Health — 2 operation(s) for accumulator (experimental).
Yuzu Health Benefits API
The Benefits API from Yuzu Health — 2 operation(s) for benefits.
Yuzu Health Coverage API
The Coverage API from Yuzu Health — 3 operation(s) for coverage.
Yuzu Health Enrollment API
The Enrollment API from Yuzu Health — 3 operation(s) for enrollment.
Yuzu Health EOB (Experimental) API
The EOB (Experimental) API from Yuzu Health — 1 operation(s) for eob (experimental).
Yuzu Health Group Policy API
The Group Policy API from Yuzu Health — 2 operation(s) for group policy.
Yuzu Health Member API
The Member API from Yuzu Health — 3 operation(s) for member.
Yuzu Health PublicApiV1 API
The PublicApiV1 API from Yuzu Health — 34 operation(s) for publicapiv1.
Yuzu Health PublicApiV2 API
The PublicApiV2 API from Yuzu Health — 14 operation(s) for publicapiv2.
Yuzu Health Sponsor API
The Sponsor API from Yuzu Health — 1 operation(s) for sponsor.
Scroll within the panel for all 10 ·
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.
yuzu-health-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 Yuzu 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 4
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
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
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
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/yuzu-health · machine-readable index on apis.io