Axena Health

Axena Health, Inc. is a Waltham, Massachusetts women's health medical device company whose flagship product is the Leva Pelvic Health System, an FDA-cleared prescription digital therapeutic that pairs a vaginal motion sensor with a mobile app to deliver supervised pelvic floor muscle training for stress, mixed and mild-to-moderate urgency urinary incontinence and chronic fecal incontinence. Leva is prescribed by clinicians, dispensed to patients through telehealth and specialty channels, and is reimbursed through commercial health plans and federal channels including the Veterans Health Administration. Axena Health ships software only as a regulated end-user product: as of this profile it operates no developer portal, no public API reference, no SDKs and no partner integration program. The only machine-readable surfaces reachable without credentials are the default WordPress REST API on its two marketing sites and an OAuth-protected WordPress MCP Adapter endpoint on levacares.com.

Axena Health is profiled on the APIs.io network. Tagged areas include Company, Health, Digital Health, Medical Devices, and Women’s Health.

Axena Health’s developer surface includes engineering blog, support, authentication, and 14 more developer resources.

🌐 Visit website 📡 Source on GitHub

22.1/100 emerging ▬ flat Agent 20/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0

0 APIs 1 MCP Servers

CompanyHealthDigital HealthMedical DevicesWomen's HealthDigital TherapeuticsPelvic HealthMedical SoftwareTelehealth

Kin Score

Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0

Composite quality — 22.1/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 4.4 / 17

Commercial Clarity 3.6 / 17

Operational Transparency 0.0 / 11

Governance 1.3 / 10

Discoverability 4.9 / 9

Regulatory Posture 7.9 / 15

Agent readiness — 20/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

MCP Server 12 / 12

Machine-Readable Auth 10 / 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

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.

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/. This rating is computed from github.com/api-evangelist/axena-health: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Scopes 1

OAuth scopes governing access to this provider's APIs.

Axena Health Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

MCPServer

MCPServer

LLMsTxt

LLMsTxt

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 2

Status, limits, changes, and where to get help

Support

Support

HelpCenter

HelpCenter

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 6

The organization behind the API

Website

ProductWebsite

About

Blog

BlogRSS

LinkedIn

Source (apis.yml)

aid: axena-health
name: Axena Health
description: 'Axena Health, Inc. is a Waltham, Massachusetts women''s health medical device company whose flagship product
  is the Leva Pelvic Health System, an FDA-cleared prescription digital therapeutic that pairs a vaginal motion sensor with
  a mobile app to deliver supervised pelvic floor muscle training for stress, mixed and mild-to-moderate urgency urinary incontinence
  and chronic fecal incontinence. Leva is prescribed by clinicians, dispensed to patients through telehealth and specialty
  channels, and is reimbursed through commercial health plans and federal channels including the Veterans Health Administration.
  Axena Health ships software only as a regulated end-user product: as of this profile it operates no developer portal, no
  public API reference, no SDKs and no partner integration program. The only machine-readable surfaces reachable without credentials
  are the default WordPress REST API on its two marketing sites and an OAuth-protected WordPress MCP Adapter endpoint on levacares.com.'
image: https://axenahealth.com/wp-content/uploads/cropped-AxenaSquare-e1713986234486.jpg
url: https://raw.githubusercontent.com/api-evangelist/axena-health/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-pass
specificationVersion: '0.20'
created: '2026-08-06'
modified: '2026-08-06'
tags:
- Company
- Health
- Digital Health
- Medical Devices
- Women's Health
- Digital Therapeutics
- Pelvic Health
- Medical Software
- Telehealth
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/axena-health-domain-security.yml
- type: Website
  url: https://axenahealth.com/
- type: ProductWebsite
  url: https://www.levacares.com/
- type: About
  url: https://axenahealth.com/about-us/
- type: Blog
  url: https://axenahealth.com/latest-blogs/
- type: BlogRSS
  url: https://axenahealth.com/feed/
- type: Support
  url: https://axenahealth.com/contact-us/
- type: HelpCenter
  url: https://levacares.com/faqs/
- type: TermsOfService
  url: https://axenahealth.com/terms-and-conditions/
- type: PrivacyPolicy
  url: https://axenahealth.com/privacy-policy/
- type: LinkedIn
  url: https://www.linkedin.com/company/axena-health/
- type: WellKnown
  url: well-known/axena-health-well-known.yml
- type: MCPServer
  url: mcp/axena-health-mcp.yml
- type: Authentication
  url: authentication/axena-health-authentication.yml
- type: OAuthScopes
  url: scopes/axena-health-scopes.yml
- type: Conformance
  url: conformance/axena-health-conformance.yml
- type: LLMsTxt
  url: llms/axena-health-llms.txt
x-enrichment:
  date: '2026-08-06'
  status: minimal
  artifacts_added: 10
  pass: local-v1
x-coverage:
  state: none
  reason: no-developer-program
  detail: Axena Health ships Leva only as an FDA-cleared prescription end-user product — there is no developer portal, no
    API reference, no SDK and no GitHub org; the only machine-readable surfaces on either host are the default WordPress REST
    API and a WordPress MCP Adapter on levacares.com that answers tools/list with 401 mcp_unauthorized.
  evidence:
  - url: https://axenahealth.com/openapi.json
    status: 404
  - url: https://levacares.com/wp-json/mcp/mcp-oauth-server
    status: 401
  - url: https://levacares.com/.well-known/oauth-authorization-server
    status: 200
  - url: https://api.github.com/orgs/axenahealth
    status: 404
  checked: '2026-08-06'