Lena Health

Lena Health is a Houston, Texas healthcare technology company founded in the Texas Medical Center that combines AI agents with human care navigators to deliver care coordination at scale. Its LenaConnect platform handles routine patient outreach calls, appointment scheduling and coordination, payer and provider hold times, automatic call documentation, EHR integration, and resource and referral management, so human navigators can focus on building trust with patients. Lena offers fully managed care navigation services covering Chronic Care Management (CCM), Transitional Care Management (TCM), rising-risk care management, and annual wellness visits, and works with health plans, accountable care organizations (ACOs), health systems, provider groups, care management providers, and community organizations. The company reports retrospective matched-cohort results of 29% fewer unplanned readmissions, 42% fewer ED visits, and $3,116 saved per patient within 180 days. Lena Health is HIPAA compliant and SOC 2 Type II certified, and publishes a trust center. Lena Health is a Techstars portfolio company. No public API, developer portal, or machine-readable API specification was found during enrichment; the platform is delivered as a managed service with EHR integration handled through engagements.

Lena Health is profiled on the APIs.io network. Tagged areas include Company, Healthcare, Health Care Coordination, Care Navigation, and Artificial Intelligence.

Lena Health’s developer surface includes support and 10 more developer resources.

🌐 Visit website 📡 Source on GitHub

18.3/100 emerging ▬ flat Agent 0/100 human only saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

0 APIs

Company HealthcareHealth Care CoordinationCare Navigation Artificial Intelligence Patient Engagement Chronic Care Management Health Plans Digital Health HIPAA

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 18.3/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 0.0 / 17

Access Clarity 7.4 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 4.9 / 9

Regulatory Posture 4.5 / 15

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

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

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/lena-health: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Lena Health Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Lena Health Trust Center

SOC 2 Type II, HIPAA

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Access & Security 3

Authentication, authorization, and security posture

TrustCenter

TrustCenter

Compliance

Compliance

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

About

About

Source (apis.yml)

aid: lena-health
name: Lena Health
description: Lena Health is a Houston, Texas healthcare technology company founded in the Texas Medical Center that combines
  AI agents with human care navigators to deliver care coordination at scale. Its LenaConnect platform handles routine patient
  outreach calls, appointment scheduling and coordination, payer and provider hold times, automatic call documentation, EHR
  integration, and resource and referral management, so human navigators can focus on building trust with patients. Lena offers
  fully managed care navigation services covering Chronic Care Management (CCM), Transitional Care Management (TCM), rising-risk
  care management, and annual wellness visits, and works with health plans, accountable care organizations (ACOs), health
  systems, provider groups, care management providers, and community organizations. The company reports retrospective matched-cohort
  results of 29% fewer unplanned readmissions, 42% fewer ED visits, and $3,116 saved per patient within 180 days. Lena Health
  is HIPAA compliant and SOC 2 Type II certified, and publishes a trust center. Lena Health is a Techstars portfolio company.
  No public API, developer portal, or machine-readable API specification was found during enrichment; the platform is delivered
  as a managed service with EHR integration handled through engagements.
url: https://raw.githubusercontent.com/api-evangelist/lena-health/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- techstars
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://lena.io/og/og-card.png
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Healthcare
- Health Care Coordination
- Care Navigation
- Artificial Intelligence
- Patient Engagement
- Chronic Care Management
- Health Plans
- Digital Health
- HIPAA
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: TrustCenter
  url: security/lena-health-trust-center.yml
- type: Website
  url: https://lena.io/
- type: About
  url: https://lena.io/about
- type: Login
  url: https://lenaconnect.com/auth/login
- type: Support
  url: https://lena.io/contact
- type: TermsOfService
  url: https://lena.io/terms
- type: PrivacyPolicy
  url: https://lena.io/privacy
- type: Compliance
  url: https://trust.lenaconnect.com/
- type: LLMsTxt
  url: llms/lena-health-llms.txt
- type: Conformance
  url: conformance/lena-health-conformance.yml
- type: DomainSecurity
  url: security/lena-health-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/lena-health"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/lena-health/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/lena-health/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.