Lyra Health
Lyra Health is a Burlingame, California enterprise mental health benefits company founded in 2015 that provides employer-sponsored behavioral health care to more than 20 million members across a network of 30,000+ providers in over 200 countries and territories. The platform combines preventive self-care resources, coaching, evidence-based therapy, medication management, family and pediatric services, and specialized acute care delivered through a benefits-administration model sold to large employers and health plans rather than directly to consumers. Lyra's product surface includes the Lyra App for members, the Lyra Empower AI-powered care platform launched in 2025, Centers of Excellence for pediatric mental health and neurodiversity, a manager coaching program, and a clinical-grade AI guide. Customers include Salesforce, Lululemon, Morgan Stanley, Genentech, Starbucks, JE Dunn, VCA, and the School District of Philadelphia, and in March 2026 the company became Workday Wellness's preferred mental health partner. Lyra acquired pediatric and family mental health provider Bend Health in July 2025. Lyra is led by CEO Jennifer Schulz, with Jenny Gonsalves as Chief Product & Technology Officer, Alethea Varra as Chief Clinical Officer, and co-founder Bob Kocher, MD on the board. The company's revenue model is per-member-per- month employer contracts plus utilization-based clinical billing; Lyra does not publish a public developer portal, OpenAPI specification, SDK, CLI, or self-service API, and its only public GitHub repository is an internal fork of an unrelated infrastructure module. All employer, member, HRIS/eligibility, SSO, and EHR integrations are negotiated and delivered through the Lyra customer success and implementation teams rather than through a self-serve developer surface.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Lyra Health the way a machine reads it — 2 machine-readable artifacts, 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 — Lyra Health scores 12.8/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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 Lyra Health
Each block below is one kind of artifact we hold for Lyra 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.
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.
Resources
Every other property we hold for Lyra 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 1
Portal, sign-up, and the first successful call
Build 2
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
Commercial 1
Pricing, plans, and the legal terms of use
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lyra-health · machine-readable index on apis.io