Recuro Health
Recuro Health is an integrated digital health company operating a virtual-first care delivery platform — a "Digital Medical Home" — sold to employers, health plans, TPAs and diagnostics companies rather than to individual developers. Its configurable SaaS platform bundles core virtual care services (virtual primary care, virtual urgent care, virtual behavioral health) with supplemental benefits including on-demand counseling, pediatric behavioral health, health advocacy, prescription benefit, wellness programs and virtual MSK therapy, plus at-home lab and genomic diagnostics. Members reach care through the Recuro Care iOS/Android apps and the member.recurohealth.com web app, with identity handled by an Auth0-hosted OpenID Connect authorization server at auth.recurohealth.com. Recuro Health is HITRUST certified and absorbed WellVia Solutions. The company markets platform integration (SSO, APIs, eligibility and reporting) to its enterprise clients, but publishes no public developer program: its documentation host requires a GitHub login and its ReadMe developer hub is not publicly served.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Recuro Health the way a machine reads it — 5 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 — Recuro Health scores 29.5/100 (thin), with a separate agent-readiness read of 13/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Recuro Health runs a real but entirely private developer surface — docs.recurohealth.com is a GitHub Pages site that 302s to a GitHub login, developer.recurohealth.com is CNAMEd to a ReadMe hub that returns 404, and api.recurohealth.com answers every path with a zero-length 404 — so the only machine-readable contract reachable without credentials is the Auth0 OpenID Connect discovery document at auth.recurohealth.com.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Recuro Health's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://docs.recurohealth.com/→ HTTP 302https://developer.recurohealth.com/→ HTTP 404https://api.recurohealth.com/openapi.json→ HTTP 404https://auth.recurohealth.com/.well-known/openid-configuration→ HTTP 200
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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Recuro 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/recuro-health/"
title="Recuro Health on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/recuro-health.svg"
alt="Recuro Health Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/recuro-health/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/recuro-health/"
title="Recuro Health on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/recuro-health/card.svg"
alt="Recuro 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 Recuro Health
Each block below is one kind of artifact we hold for Recuro 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 1
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.
Recuro Health Identity (OpenID Connect)
Recuro Health's member and provider identity surface, an Auth0-hosted OpenID Connect / OAuth 2.0 authorization server. The OIDC discovery document, the RFC 8414 authorization-se...
Security 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.
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.
Resources
Every other property we hold for Recuro 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 2
Portal, sign-up, and the first successful call
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
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 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/recuro-health · machine-readable index on apis.io
This is an independent, third-party profile of Recuro 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.