Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Spring Health website screenshot

Spring Health

Spring Health is a New York City-based digital mental health company that sells a comprehensive mental healthcare benefit to employers, health plans, brokers, channel partners, and healthcare providers. Its platform combines a clinically validated assessment, AI-driven matching, and a curated provider network to deliver therapy, medication management, coaching, an Employee Assistance Program (EAP), critical-incident response, work-life services, and self-guided digital exercises through a unified member experience branded Spring Life. For health plans and providers, Spring Health offers Springworks — its enterprise care-coordination and care-management offering — alongside a generative-AI member-facing assistant called Guide and clinician-facing AI tooling. Customers include General Mills, Hearst, and Moda Health, and the company publishes outcomes, research, and ROI evidence on long-term cost savings of mental health benefits. Spring Health operates as a B2B2C benefit: it does not expose a public developer portal, OpenAPI specification, SDK, or documented HTTP API. Integrations with HRIS, SSO, eligibility files, and health-plan partners are delivered through enterprise implementation rather than a self-service API, and its GitHub organization (github.com/SpringHealth) has no public repositories.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Spring 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 — Spring Health scores 17.8/100 (emerging), 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 17.8/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 0.4 / 20
Commercial Clarity 5.8 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Regulatory · Health 6.2 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Spring Health

Each block below is one kind of artifact we hold for Spring 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.

Spring Health Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Spring Health Trust Center

SOC 2, ISO 27001, ISO 27017, ISO 27018, HIPAA, FedRAMP, GDPR

SECURITY

Resources

Every other property we hold for Spring 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

Documentation 1

Reference material describing how the API behaves

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Operate 1

Status, limits, changes, and where to get help

← All providers · Data indexed from github.com/api-evangelist/spring-health · machine-readable index on apis.io