Clever Care
Clever Care Health Plan is a California Medicare Advantage (HMO and HMO C-SNP) plan headquartered in Huntington Beach, CA, that blends the healing therapies of Eastern medicine with the innovative practices of Western medicine to serve Los Angeles, Orange, San Diego, Riverside, and San Bernardino counties. In compliance with the CMS Interoperability and Patient Access rule (CMS-9115-F), Clever Care operates a secure, standards-based HL7 FHIR R4 API surface (WSO2 gateway) spanning 13 published resource APIs across three domains: Patient Access (CARIN Blue Button), Provider Directory (Da Vinci PDex Plan-Net), and Drug Formulary (Da Vinci US Drug Formulary). Patient Access resources are secured with SMART on FHIR OAuth 2.0 / OpenID Connect; directory and formulary resources are public and rate-limited. Provider Access, Payer-to-Payer, and Prior Authorization APIs are planned for January 1, 2027.
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 Clever Care the way a machine reads it — 18 machine-readable artifacts across 13 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 — Clever Care scores 47.7/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 Clever Care
Each block below is one kind of artifact we hold for Clever Care. 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 13
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.
Clever Care Coverage API
The Coverage API from Clever Care — 2 operation(s) for coverage.
Clever Care Endpoint API
The Endpoint API from Clever Care — 2 operation(s) for endpoint.
Clever Care ExplanationOfBenefit API
The ExplanationOfBenefit API from Clever Care — 2 operation(s) for explanationofbenefit.
Clever Care HealthcareService API
The HealthcareService API from Clever Care — 2 operation(s) for healthcareservice.
Clever Care InsurancePlan API
The InsurancePlan API from Clever Care — 2 operation(s) for insuranceplan.
Clever Care List API
The List API from Clever Care — 2 operation(s) for list.
Clever Care Location API
The Location API from Clever Care — 2 operation(s) for location.
Clever Care MedicationKnowledge API
The MedicationKnowledge API from Clever Care — 2 operation(s) for medicationknowledge.
Clever Care Organization API
The Organization API from Clever Care — 2 operation(s) for organization.
Clever Care OrganizationAffiliation API
The OrganizationAffiliation API from Clever Care — 2 operation(s) for organizationaffiliation.
Clever Care Patient API
The Patient API from Clever Care — 2 operation(s) for patient.
Clever Care Practitioner API
The Practitioner API from Clever Care — 2 operation(s) for practitioner.
Clever Care PractitionerRole API
The PractitionerRole API from Clever Care — 2 operation(s) for practitionerrole.
Scroll within the panel for all 13 ·
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.
clever-care-mcp.yml
MCP SERVERSecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Clever Care — 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 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
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/clever-care · machine-readable index on apis.io