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 APIs on the APIs.io network: Chart Retrieval API and Claim Management API. Tagged areas include Healthcare, United States, Interoperability, Clinical Data, and Payer.

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

52.6/100 developing ▬ flat Agent 65/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
2 APIs 1 MCP Servers
HealthcareUnited StatesInteroperabilityClinical DataPayerProviderEHRHealth Data ExchangeClaimsRisk Adjustment

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 52.6/100 · developing
Contract Quality 9.4 / 25
Developer Ergonomics 13.5 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 2.1 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 65/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
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/moxe-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 →

APIs 2

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

Moxe Health Chart Retrieval API

Initiate a patient chart request and check its status. The API ingests a release-of-information request with member and demographic identifiers, searches connected EHRs for the ...

Moxe Health Claim Management API

Initiate a claim management request and check its status. Retrieves the clinical chart supporting a specific claim by member and claim identifiers, then delivers the extracted d...

Arazzo Workflows 3

Multi-step API workflows described with the Arazzo specification.

_Index

ARAZZO

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

MCP Servers 1

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

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 · HSTS · 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

4 operations · 2 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 8

Authentication, authorization, and security posture

Scroll for all 8

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 4

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
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.
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Healthcare
- United States
- Interoperability
- Clinical Data
- Payer
- Provider
- EHR
- Health Data Exchange
- Claims
- Risk Adjustment
created: '2026-07-24'
modified: '2026-07-24T12:00:00Z'
specificationVersion: '0.19'
apis:
- aid: moxe-health:moxe-health-chart-retrieval-api
  name: Moxe Health Chart Retrieval API
  description: Initiate a patient chart request and check its status. The API ingests a release-of-information request with
    member and demographic identifiers, searches connected EHRs for the specified patient and date-of-service range, and delivers
    the extracted clinical data to a predetermined SFTP location. REST/JSON, OpenAPI 3.0.1, secured with OAuth2 client-credentials
    plus an x-api-key header.
  humanURL: https://developer.moxehealth.com/reference/overview
  baseURL: https://int-api.moxehealth.com/chart-retrieval
  tags:
  - Patient
  - Chart Retrieval
  - Clinical Data
  properties:
  - type: OpenAPI
    url: openapi/moxe-health-chart-retrieval-initiate-openapi.json
  - type: OpenAPI
    url: openapi/moxe-health-chart-retrieval-status-openapi.json
  - 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
- aid: moxe-health:moxe-health-claim-management-api
  name: Moxe Health Claim Management API
  description: Initiate a claim management request and check its status. Retrieves the clinical chart supporting a specific
    claim by member and claim identifiers, then delivers the extracted data to a predetermined location. REST/JSON, OpenAPI
    3.0.1, secured with OAuth2 client-credentials plus an x-api-key header.
  humanURL: https://developer.moxehealth.com/reference/overview
  baseURL: https://int-api.moxehealth.com/chart-retrieval
  tags:
  - Claims
  - Claim Management
  - Clinical Data
  properties:
  - type: OpenAPI
    url: openapi/moxe-health-claim-management-initiate-openapi.json
  - type: OpenAPI
    url: openapi/moxe-health-claim-management-status-openapi.json
  - type: Documentation
    url: https://developer.moxehealth.com/reference/overview
  - type: APIReference
    url: https://developer.moxehealth.com/reference/initiateclaimmanagementrequest
  - type: APIReference
    url: https://developer.moxehealth.com/reference/getclaimmanagementrequeststatus
  - type: Authentication
    url: https://developer.moxehealth.com/docs/authentication
common:
- 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: MCPServer
  url: mcp/moxe-health-mcp.yml
- 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: 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
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com