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.
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.
API Evangelist profiles Axena Health the way a machine reads it — 4 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 — Axena Health scores 22.1/100 (emerging), with a separate agent-readiness read of 20/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
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.
This is an honest zero, not a gap in our research. Axena Health does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://axenahealth.com/openapi.json→ HTTP 404https://levacares.com/wp-json/mcp/mcp-oauth-server→ HTTP 401https://levacares.com/.well-known/oauth-authorization-server→ HTTP 200https://api.github.com/orgs/axenahealth→ HTTP 404
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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Axena Health's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/axena-health/"
title="Axena Health on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/axena-health.svg"
alt="Axena Health Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/axena-health/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/axena-health/"
title="Axena Health on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/axena-health/card.svg"
alt="Axena Health Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Axena Health
Each block below is one kind of artifact we hold for Axena 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.
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
axena-health-mcp.yml
MCP SERVERSecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Axena 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.
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/axena-health · machine-readable index on apis.io
This is an independent, third-party profile of Axena Health, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.