Moxe Health

Moxe Health is a United States healthcare data interoperability company, headquartered in Madison, Wisconsin, that operates the Clinical Data Clearinghouse for secure clinical data exchange between health plans (payers) and health systems (providers). Moxe's API-first platform ingests release-of-information (ROI) requests, searches connected electronic health records (EHRs) to extract the minimum-necessary contextual clinical data for a specified patient and date range, and securely delivers that data to the partner's system. Its Chart Retrieval API supports risk adjustment, quality improvement, claim management, payment integrity, care management, and forecasting use cases. The public developer portal documents a REST (OpenAPI 3.0.1) Chart Retrieval API secured with OAuth2 client-credentials plus an x-api-key header; retrieved charts are returned to a predetermined location via SFTP. Moxe is HIPAA and SOC 2 Type 2 compliant and was named number 1 Best in KLAS for Payer-Provider Data Exchange. The documented API is REST/JSON rather than HL7 FHIR, and full access is granted through a partner onboarding agreement.

Moxe Health publishes 2 API contracts indexed on the APIs.io network: Claims API and Patient API. Tagged areas include Healthcare, United States, Interoperability, Clinical Data, and Payers.

The Moxe Health catalog on APIs.io includes 1 Spectral governance ruleset.

Moxe Health’s developer surface includes authentication, documentation, getting-started guide, API reference, signup flow, engineering blog, support, and 35 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

51.5/100 developing ▲ 6.3 Agent 26/100 agent aware Front door AI 1/6 silent Heartbeat 36/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

4 published contracts 2 Agent Skills

Healthcare United States Interoperability Clinical Data Payers Providers Electronic Health RecordsHealth Data ExchangeClaims Risk Adjustment

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Health Information Management

BC-2900

Patient

POST /v1/patient-chart-request

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 51.5/100 · developing

Contract Quality 9.0 / 19

Developer Ergonomics 8.8 / 15

Access Clarity 7.5 / 15

Operational Transparency 1.3 / 10

Contract Governance 2.9 / 9

Discoverability 5.9 / 8

Regulatory Posture 6.9 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 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

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

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

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/moxe-health/"><img src="https://apis.io/badge/moxe-health/card.svg" alt="Moxe 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):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
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)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 47.8 — up to +13.1 composite points
Operational Transparency scores 13.2 — up to +11.3 composite points
Access Clarity scores 50.0 — up to +10.0 composite points

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/moxe-health/apis.yml: open an issue on github.com/api-evangelist/moxe-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.

Market	Position	Depth	Registered MCP server	Declares compatibility
Payer Interoperability (CAQH CORE, X12, Da Vinci, WEDI)	standard	17.2 (thin)	-	-

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 2

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.

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Moxe Health Claims API

The Claims API from Moxe Health — 2 operation(s) for claims.

Moxe Health Patient API

The Patient API from Moxe Health — 2 operation(s) for patient.

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Chart Retrieval API

OPEN COLLECTION

Chart Retrieval API

OPEN COLLECTION

Chart Retrieval API

OPEN COLLECTION

Chart Retrieval API

OPEN COLLECTION

Arazzo Workflows 2

Multi-step API workflows described with the Arazzo specification.

Request a claim-supporting chart and poll for status

Initiate a claim-management request to retrieve the clinical chart supporting a specific claim, then poll the status endpoint with the returned moxeRequestId.

ARAZZO

Request a patient chart and poll for status

Initiate a release-of-information request for a patient's clinical chart, then poll the status endpoint with the returned moxeRequestId until Moxe delivers the chart via SFTP.

ARAZZO

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Request a claim-supporting chart from Moxe Health

AGENT SKILL

Request a patient chart from Moxe Health

AGENT SKILL

Moxe Health API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Moxe Health Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Moxe Health Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Moxe Health Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Moxe Health API Rules

54 rules · 52 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 4

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Moxe Health Chart Retrieval Initiate Overlay

2 actions · update · moxe-health-chart-retrieval-initiate-openapi.json

DERIVED

Moxe Health Chart Retrieval Status Overlay

2 actions · update · moxe-health-chart-retrieval-status-openapi.json

DERIVED

Moxe Health Claim Management Initiate Overlay

2 actions · update · moxe-health-claim-management-initiate-openapi.json

DERIVED

Moxe Health Claim Management Status Overlay

2 actions · update · moxe-health-claim-management-status-openapi.json

DERIVED

Security Posture 4

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

Moxe Health Authentication

oauth2/apiKey · 2 schemes

SECURITY

Moxe Health Domain Security

TLSv1.3 · DMARC

SECURITY

Moxe Health Vulnerability Disclosure

Bugcrowd · contact published

SECURITY

Moxe Health Trust Center

SOC 2, HIPAA, GDPR

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Moxe Health Scopes

4 scopes · clientCredentials

4 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Moxe Health Agentic Access

4 operations · 2 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Arazzo

Arazzo

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

ToolCrosswalk

ToolCrosswalk

Packages

Packages

GitHubOrganization

GitHubOrganization

Access & Security 8

Authentication, authorization, and security posture

TrustCenter

DomainSecurity

OAuthScopes

Authentication

Compliance

VulnerabilityDisclosure

VulnerabilityDisclosure

Authentication

Authentication

Security

Security

Scroll for all 8

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 4

The organization behind the API

BlogRSS

BlogRSS

Website

Website

LinkedIn

Blog

Blog

Other 5

Properties that don't map to a standard resource type

CapabilityMap

Overlay

Overlay

Overlay

Overlay

Source (apis.yml)

aid: moxe-health
url: https://raw.githubusercontent.com/api-evangelist/moxe-health/refs/heads/main/apis.yml
name: Moxe Health
kind: company
description: Moxe Health is a United States healthcare data interoperability company, headquartered in Madison, Wisconsin,
  that operates the Clinical Data Clearinghouse for secure clinical data exchange between health plans (payers) and health
  systems (providers). Moxe's API-first platform ingests release-of-information (ROI) requests, searches connected electronic
  health records (EHRs) to extract the minimum-necessary contextual clinical data for a specified patient and date range,
  and securely delivers that data to the partner's system. Its Chart Retrieval API supports risk adjustment, quality improvement,
  claim management, payment integrity, care management, and forecasting use cases. The public developer portal documents a
  REST (OpenAPI 3.0.1) Chart Retrieval API secured with OAuth2 client-credentials plus an x-api-key header; retrieved charts
  are returned to a predetermined location via SFTP. Moxe is HIPAA and SOC 2 Type 2 compliant and was named number 1 Best
  in KLAS for Payer-Provider Data Exchange. The documented API is REST/JSON rather than HL7 FHIR, and full access is granted
  through a partner onboarding agreement.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
tags:
- Healthcare
- United States
- Interoperability
- Clinical Data
- Payers
- Providers
- Electronic Health Records
- Health Data Exchange
- Claims
- Risk Adjustment
tags_raw:
- Healthcare
- United States
- Interoperability
- Clinical Data
- Payer
- Provider
- EHR
- Health Data Exchange
- Claims
- Risk Adjustment
created: '2026-07-24'
modified: '2026-10-06'
specificationVersion: '0.23'
apis:
- aid: moxe-health:moxe-health-claims-api
  name: Moxe Health Claims API
  description: The Claims API from Moxe Health — 2 operation(s) for claims.
  humanURL: https://developer.moxehealth.com/reference/overview
  baseURL: https://int-api.moxehealth.com/chart-retrieval
  tags:
  - Claims
  properties:
  - type: OpenAPI
    url: openapi/moxe-health-claims-api-openapi.yml
  - type: Documentation
    url: https://developer.moxehealth.com/reference/overview
  - type: APIReference
    url: https://developer.moxehealth.com/reference/initiatechartrequest
  - type: APIReference
    url: https://developer.moxehealth.com/reference/getchartrequeststatus
  - type: Documentation
    url: https://developer.moxehealth.com/reference/request-source-ids
  - type: Authentication
    url: https://developer.moxehealth.com/docs/authentication
  - type: APIReference
    url: https://developer.moxehealth.com/reference/initiateclaimmanagementrequest
  - type: APIReference
    url: https://developer.moxehealth.com/reference/getclaimmanagementrequeststatus
- aid: moxe-health:moxe-health-patient-api
  name: Moxe Health Patient API
  description: The Patient API from Moxe Health — 2 operation(s) for patient.
  humanURL: https://developer.moxehealth.com/reference/overview
  baseURL: https://int-api.moxehealth.com/chart-retrieval
  tags:
  - Patients
  tags_raw:
  - Patient
  properties:
  - type: OpenAPI
    url: openapi/moxe-health-patient-api-openapi.yml
  - type: Documentation
    url: https://developer.moxehealth.com/reference/overview
  - type: APIReference
    url: https://developer.moxehealth.com/reference/initiatechartrequest
  - type: APIReference
    url: https://developer.moxehealth.com/reference/getchartrequeststatus
  - type: Documentation
    url: https://developer.moxehealth.com/reference/request-source-ids
  - type: Authentication
    url: https://developer.moxehealth.com/docs/authentication
  - type: APIReference
    url: https://developer.moxehealth.com/reference/initiateclaimmanagementrequest
  - type: APIReference
    url: https://developer.moxehealth.com/reference/getclaimmanagementrequeststatus
common:
- url: https://moxehealth.com/feed/
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/moxe-health-capability-edges.yml
  name: Moxe Health Business Capability Map
- type: TrustCenter
  url: security/moxe-health-trust-center.yml
- type: DomainSecurity
  url: security/moxe-health-domain-security.yml
- type: AgenticAccess
  url: agentic-access/moxe-health-agentic-access.yml
- type: OAuthScopes
  url: scopes/moxe-health-scopes.yml
- type: Authentication
  url: authentication/moxe-health-authentication.yml
- type: Conventions
  url: conventions/moxe-health-conventions.yml
- type: ErrorCatalog
  url: errors/moxe-health-problem-types.yml
- type: Lifecycle
  url: lifecycle/moxe-health-lifecycle.yml
- type: Conformance
  url: conformance/moxe-health-conformance.yml
- type: Compliance
  url: https://moxehealth.com/security/
- type: DataModel
  url: data-model/moxe-health-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/moxe-health-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: ToolCrosswalk
  url: mcp/moxe-health-tool-crosswalk.yml
- type: VulnerabilityDisclosure
  url: security/moxe-health-vulnerability-disclosure.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Packages
  url: packages/moxe-health-packages.yml
- type: Plans
  url: plans/moxe-health-plans-pricing.yml
- type: RateLimits
  url: rate-limits/moxe-health-rate-limits.yml
- type: Arazzo
  name: Request a patient chart and poll for status
  url: arazzo/moxe-health-request-patient-chart.yml
- type: Arazzo
  name: Request a claim-supporting chart and poll for status
  url: arazzo/moxe-health-request-claim-chart.yml
- type: Overlay
  url: overlays/moxe-health-chart-retrieval-initiate-overlay.yaml
- type: Overlay
  url: overlays/moxe-health-chart-retrieval-status-overlay.yaml
- type: Overlay
  url: overlays/moxe-health-claim-management-initiate-overlay.yaml
- type: Overlay
  url: overlays/moxe-health-claim-management-status-overlay.yaml
- type: LLMsTxt
  url: llms/moxe-health-llms.txt
- type: Website
  url: https://moxehealth.com/
- type: DeveloperPortal
  url: https://developer.moxehealth.com/
- type: Documentation
  url: https://developer.moxehealth.com/docs/getting-started
- type: GettingStarted
  url: https://developer.moxehealth.com/docs/getting-started
- type: APIReference
  url: https://developer.moxehealth.com/reference/overview
- type: Authentication
  url: https://developer.moxehealth.com/docs/authentication
- type: SignUp
  url: https://developer.moxehealth.com/login
- type: GitHubOrganization
  url: https://github.com/moxehealth
- type: LinkedIn
  url: https://www.linkedin.com/company/moxe-health
- type: Blog
  url: https://moxehealth.com/insights
- type: Security
  url: https://moxehealth.com/security/
- type: PrivacyPolicy
  url: https://moxehealth.com/privacy-policy/
- type: TermsOfService
  url: https://moxehealth.com/moxe-technology-governing-agreement/
- type: Support
  url: https://moxehealth.com/contact/
- type: LLMsTxt
  url: https://developer.moxehealth.com/llms.txt
x-enrichment:
  date: '2026-08-14'
  status: enriched
  artifacts_added: 3
  pass: local-v1
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Moxe Health API — frequently asked questions

Does Moxe Health have an API?

Yes. APIs.io lists 2 APIs from Moxe Health, including Moxe Health Claims API and Moxe Health Patient API.

Is there an OpenAPI specification for the Moxe Health API?

Yes. APIs.io indexes 2 OpenAPI specifications for Moxe Health, each linked for download from this page.

How do I authenticate with the Moxe Health API?

Moxe Health documents its authentication (oauth2/apiKey · 2 schemes). The details are profiled on APIs.io as Moxe Health Authentication.

Is the Moxe Health API ready for AI agents?

Moxe Health has a Kin Score of 51.5 out of 100 (developing) and an Agent Readiness score of 25.9 (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/moxe-health"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/moxe-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.

GitHub Google LinkedIn

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