Axena Health website screenshot

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.

18.8/100 emerging ▬ flat Agent 6/100 agent aware Front door AI 1/6 silent Heartbeat 25/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
0 APIs 1 MCP Servers
CompanyHealthDigital HealthMedical DevicesWomen's HealthDigital TherapeuticsPelvic HealthMedical SoftwareTelehealth

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
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/.
Show this score on your site. Kin Score badge preview for Axena Health It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/axena-health/"><img src="https://apis.io/badge/axena-health/card.svg" alt="Axena Health on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
  • Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
11 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
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 the provider profile at artifacts.apis.io/axena-health/apis.yml: open an issue on github.com/api-evangelist/axena-health to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

MarketPositionDepthRegistered MCP serverDeclares compatibility
Digital Therapeutics (regulated, reimbursed digital health apps) undeclared - - -

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (documented)

MCP Servers 1

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

Leva Pelvic Health System — WordPress MCP Adapter

levacares.com — the Leva Pelvic Health System product site operated by Axena Health — runs the WordPress MCP Adapter and exposes two live Model Context Protocol endpoints under ...

MCP SERVER

Security Posture 2

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

Axena Health Authentication

2 schemes

SECURITY

Axena Health Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Axena Health Scopes

1 scope

1 scopes

SCOPES

Resources

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

Source (apis.yml)

apis.yml Raw ↑
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.'
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
  probe_state: none
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
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.23'
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'

Axena Health API — frequently asked questions

How do I authenticate with the Axena Health API?

Axena Health uses bearer-token authentication (2 schemes). The details are profiled on APIs.io as Axena Health Authentication.

Does Axena Health have an MCP server?

Yes. APIs.io lists 1 MCP server for Axena Health: levacares.com — the Leva Pelvic Health System product site operated by Axena Health — runs the WordPress MCP Adapter and exposes two live Model Context Protocol endpoints under the `mcp` REST namespac

Is the Axena Health API ready for AI agents?

Axena Health has a Kin Score of 18.8 out of 100 (emerging) and an Agent Readiness score of 6.0 (agent-aware), scored by API Evangelist on 2026-11-06.

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/axena-health"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/axena-health/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/axena-health/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

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