Hinge Health
Hinge Health is a San Francisco-based digital musculoskeletal (MSK) care company founded in 2014 by Daniel Perez and Gabriel Mecklenburg, delivering virtual physical therapy, pelvic health, and chronic pain care to enterprise health plans, employers, and their members. The platform combines on-demand exercise therapy with a multidisciplinary care team — physical therapists, health coaches, board-certified physicians, and orthopedic specialists — augmented by 3D motion tracking, computer vision, and an in-house AI Care Assistant. Hinge Health develops Enso, an FDA-cleared, drug-free wearable that delivers proprietary electrical stimulation waveforms for pain relief, and operates HingeConnect, an EMR/claims interoperability layer that ingests records from more than one million external providers across 120,000+ care sites to coordinate care, surface surgical and opioid risk, and feed real-time clinical context into the digital clinic. The company also runs HingeSelect, a national provider network for in-person MSK care, and contracts with all five major US national health plans plus employers including Boeing, Salesforce, and US Foods. Hinge Health raised more than $1 billion from Insight Partners, Tiger Global, Coatue, and Atomico before completing its IPO on the New York Stock Exchange under the ticker HNGE on May 22, 2025, pricing at $32/share and opening at $39.25 for an initial market capitalization above $3 billion. There is no public developer API, SDK, or open-source release for Hinge Health, Enso, or HingeConnect — the platform is sold as a managed clinical service to health plans and employers, and the HingeConnect interoperability surface is operated internally rather than exposed to third-party developers.
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 Hinge Health the way a machine reads it — 1 machine-readable artifact, 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 — Hinge Health scores 11.3/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 Hinge Health
Each block below is one kind of artifact we hold for Hinge 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 1
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 Hinge 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.
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 13
Properties that don't map to a standard resource type
Scroll within the panel for all 13 ·
← All providers · Data indexed from github.com/api-evangelist/hinge-health · machine-readable index on apis.io