# Health record and wellness data APIs for AI agents

> 12 health records & wellness data listings ranked by the Anchor benchmark. Leader Medplum (B). APIs that retrieve a patient's clinical records from hospitals and health information networks, connect to EHRs, store records on a FHIR server, or read data from wearables and health apps. Compared on record coverage, FHIR support, consent and patient authorisation, compliance terms and how access is granted.

- Canonical: https://www.anchorterminal.com/categories/health-data
- Markdown: https://www.anchorterminal.com/categories/health-data.md (~3,800 tokens)
- Slim: https://www.anchorterminal.com/categories/health-data.min.md (~580 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/categories/health-data.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-14

APIs that retrieve a patient's clinical records from hospitals and health information networks, connect to EHRs, store records on a FHIR server, or read data from wearables and health apps. Compared on record coverage, FHIR support, consent and patient authorisation, compliance terms and how access is granted.

- Tools ranked: 12 · agent-ready (BB or better): 0 · accept x402: 0 · hosted endpoints: 4 · desk reviews by the panel: 0
- JSON: https://www.anchorterminal.com/api/v1/tools.json (list) · https://www.anchorterminal.com/api/v1/rankings.json (ranked) · https://www.anchorterminal.com/api/v1/x402.json (payable) · https://www.anchorterminal.com/api/v1/capabilities.json (by capability)
- Grades run AA, A, BB, B, C, D, E, F · methodology: https://www.anchorterminal.com/benchmark/

- Shortlist and picks by need: https://www.anchorterminal.com/best/health-data/index.md
- Head-to-head comparisons (63): https://www.anchorterminal.com/compare/health-data/index.md
- Capabilities in this category: health.records, health.fhir, health.ehr, health.wearables, health.consent
- https://letme.dev/health.records picks the top-graded tool in this list and says how to call it direct; calling through letme comes later (https://www.anchorterminal.com/letme/index.md)

## Ranking

| # | Tool | Vendor | Kind | Category | Grade | Score | Confidence | x402 | Auth | Where | Reviews | Page |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 216 | Medplum | Orangebot, Inc. (dba Medplum) | HTTP API | Health | B | 68.7 | medium | no | OAuth | hosted | none | https://www.anchorterminal.com/tools/medplum.md |
| 327 | Terra API | Terra Enabling Developers Inc. | HTTP API | Health | B | 65.9 | medium | no | OAuth or key | hosted | none | https://www.anchorterminal.com/tools/terra.md |
| 385 | Aidbox | Health Samurai, Inc. | HTTP API | Health | B | 64.2 | medium | no | OAuth | local | none | https://www.anchorterminal.com/tools/aidbox.md |
| 583 | Health Gorilla | Health Gorilla, Inc. | HTTP API | Health | C | 59.3 | medium | no | OAuth | local | none | https://www.anchorterminal.com/tools/health-gorilla.md |
| 618 | Redox | Redox, Inc. | HTTP API | Health | C | 58.3 | medium | no | OAuth | hosted | none | https://www.anchorterminal.com/tools/redox.md |
| 628 | Validic Inform | Validic, Inc. (ChartSpan) | HTTP API | Health | C | 57.9 | medium | no | API key | local | none | https://www.anchorterminal.com/tools/validic.md |
| 669 | Zus Health | Zus Health, Inc. | HTTP API | Health | C | 56.6 | medium | no | OAuth | local | none | https://www.anchorterminal.com/tools/zus-health.md |
| 718 | ROOK | Rookeries Development Corp. | HTTP API | Health | C | 54.9 | medium | no | API key | local | none | https://www.anchorterminal.com/tools/rook.md |
| 773 | Medblocks | Medblocks Inc. | HTTP API | Health | D | 52.7 | medium | no | OAuth or key | hosted | none | https://www.anchorterminal.com/tools/medblocks.md |
| 833 | Metriport Medical API | Metriport Inc. | HTTP API | Health | D | 50.1 | medium | no | API key | local | none | https://www.anchorterminal.com/tools/metriport.md |
| 867 | Particle Health | Particle Health, Inc. | HTTP API | Health | D | 48.6 | medium | no | OAuth | local | none | https://www.anchorterminal.com/tools/particle-health.md |
| 903 | 1upHealth | 1upHealth, Inc. | HTTP API | Health | D | 46.8 | medium | no | OAuth | local | none | https://www.anchorterminal.com/tools/1uphealth.md |

Scores are from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/), with Performance and Task success pending. p95 latency and context cost come from our probes, which haven't run yet.

## Summaries

### 216. Medplum, B (68.7)

Open-source FHIR R4 server and healthcare developer platform from Orangebot, Inc. (dba Medplum). Agents reach patient records through the hosted FHIR REST API at api.medplum.com, a remote MCP server or a self-hosted copy. Graded on the hosted FHIR API at api.medplum.com. Rate limits, a `RateLimit` header and a 99.99 per cent SLA are published, AccessPolicy resources allow read-only clients, and an official MCP server sits in the registry. Its main tool can delete records with no annotation, the status page could not be read, and the privacy policy dates from 2022.

- Page: https://www.anchorterminal.com/tools/medplum · Markdown: https://www.anchorterminal.com/tools/medplum.md · JSON: https://www.anchorterminal.com/api/v1/tools/medplum.json
- Capabilities: health.fhir, health.records · endpoint: `https://api.medplum.com/mcp/stream`

### 327. Terra API, B (65.9)

Terra's Unified API collects activity, sleep, body and nutrition data from 500+ wearables and health apps, normalises it into one schema and sends it by webhook or REST. An MCP server, Terra AI, lets agents read a connected user's data. Graded on the Unified API and the Terra AI MCP server. A public OpenAPI 3.1 spec, llms.txt, per-user rate limits with Retry-After, and scoped admin tokens with approvals. Access starts at $499 a month with billing details at sign-up, the data API key has no scopes, and API key requests failed for 2 hours 38 minutes on 7 August 2026.

- Page: https://www.anchorterminal.com/tools/terra · Markdown: https://www.anchorterminal.com/tools/terra.md · JSON: https://www.anchorterminal.com/api/v1/tools/terra.json
- Capabilities: health.wearables, health.consent, health.fhir · endpoint: `https://access.tryterra.co/api/v2/mcp/<user_id>`

### 385. Aidbox, B (64.2)

FHIR R4 and R5 server on PostgreSQL from Health Samurai, run from Docker images under a free development licence or a paid production licence. Agents use each instance's FHIR REST API or its alpha MCP server. Graded on the FHIR REST API of an Aidbox instance the owner runs. Monthly releases, two-year LTS lines, SMART on FHIR, AccessPolicy rules and AuditEvent logging are documented, and a free development licence needs no sales call. Aidbox has no rate limiting of its own, its MCP module is alpha, and no terms of service were found on the website.

- Page: https://www.anchorterminal.com/tools/aidbox · Markdown: https://www.anchorterminal.com/tools/aidbox.md · JSON: https://www.anchorterminal.com/api/v1/tools/aidbox.json
- Capabilities: health.fhir, health.records, health.consent

### 583. Health Gorilla, C (59.3)

Health Gorilla is a designated TEFCA QHIN whose FHIR R4 API retrieves patient records from national networks (Patient360), places lab orders and returns results, and sends ADT and clinical alerts, for organisations it onboards. A TEFCA QHIN with a FHIR R4 API, OpenAPI fragments on every reference page, idempotency keys on POST and dated weekly release notes. Access is sales-led, with case-by-case fees, a sandbox by request and no published rate limit numbers, and the API terms allow access to be cut at any time.

- Page: https://www.anchorterminal.com/tools/health-gorilla · Markdown: https://www.anchorterminal.com/tools/health-gorilla.md · JSON: https://www.anchorterminal.com/api/v1/tools/health-gorilla.json
- Capabilities: health.records, health.fhir, health.consent

### 618. Redox, C (58.3)

Redox connects software vendors to hospital EHRs and clinical networks, translating HL7v2, C-CDA, X12 and DICOM into FHIR or Redox data models, with a FHIR API, a Platform API and a hosted MCP server for managing integrations. Redox connects to EHRs and clinical networks behind a FHIR API, with signed-JWT OAuth keys, a 99.95 per cent SLA, a HackerOne bug bounty and a hosted MCP server for managing integrations. The MCP server exposes 107 tools at once with write and delete tools unconfirmed, OpenAPI files sit behind login, and the sandbox plan costs $15,000 a year.

- Page: https://www.anchorterminal.com/tools/redox · Markdown: https://www.anchorterminal.com/tools/redox.md · JSON: https://www.anchorterminal.com/api/v1/tools/redox.json
- Capabilities: health.ehr, health.fhir, health.records · endpoint: `https://api.redoxengine.com/mcp`

### 628. Validic Inform, C (57.9)

Validic Inform normalises data from wearables, health apps and in-home medical devices into one API, with a REST API for per-user reads and a server-sent events Streaming API for bulk delivery, and a free self-service developer tier. Graded on the Inform REST and Streaming APIs. An agent can create a free developer account through a sign-up API, with only an emailed code needing a person's inbox, and llms.txt plus agent guides document every step. The organisation token travels in the URL query string, the free tier holds synthetic data only, and production access needs an Enterprise contract.

- Page: https://www.anchorterminal.com/tools/validic · Markdown: https://www.anchorterminal.com/tools/validic.md · JSON: https://www.anchorterminal.com/api/v1/tools/validic.json
- Capabilities: health.wearables, health.consent

### 669. Zus Health, C (56.6)

Zus Health assembles a patient's history from CommonWell, Carequality, Surescripts, Quest and ADT networks into the Zus Aggregated Profile, and exposes it through FHIR R4 REST, GraphQL and webhook APIs for care organisations it onboards. FHIR R4 over an aggregated patient profile drawn from CommonWell, Carequality, Surescripts, Quest and ADT networks, with published rate limits, a 99.5 per cent SLA and a dated changelog. Accounts and sandboxes are provisioned by Zus on request, with no public prices, no named security certification and no SDK.

- Page: https://www.anchorterminal.com/tools/zus-health · Markdown: https://www.anchorterminal.com/tools/zus-health.md · JSON: https://www.anchorterminal.com/api/v1/tools/zus-health.json
- Capabilities: health.records, health.fhir, health.ehr, health.consent

### 718. ROOK, C (54.9)

ROOK Connect, from Rookeries Development Corp., collects health data from wearables and phone health stores, normalises it into sleep, physical and body summaries and events, and sends it by webhook or a REST API. Graded on the REST API. A public OpenAPI file, a free Sandbox from the self-serve portal, published plan prices and a dated changelog. Credentials are one client UUID and secret per environment with no scopes, 429 handling isn't documented, the API is meant for occasional queries rather than bulk reads, and no SOC 2 report or security contact was found.

- Page: https://www.anchorterminal.com/tools/rook · Markdown: https://www.anchorterminal.com/tools/rook.md · JSON: https://www.anchorterminal.com/api/v1/tools/rook.json
- Capabilities: health.wearables, health.consent, health.fhir

### 773. Medblocks, D (52.7)

Medblocks Platform lets an app or agent connect a patient's hospital, clinic and insurer records through SMART on FHIR and read them back as FHIR R4, through a REST API, a TypeScript SDK or a remote MCP server. Patient-authorised record retrieval with a ten-tool remote MCP server, OAuth with per-capability consent, an audit entry for every call and a free plan for 1,000 active patients. No status page, no published rate limits and no idempotency keys were found, and the OpenAPI file behind the reference is not published.

- Page: https://www.anchorterminal.com/tools/medblocks · Markdown: https://www.anchorterminal.com/tools/medblocks.md · JSON: https://www.anchorterminal.com/api/v1/tools/medblocks.json
- Capabilities: health.records, health.consent, health.ehr, health.fhir, agent.tools · endpoint: `https://app.medblocks.com/mcp`

### 833. Metriport Medical API, D (50.1)

Metriport's Medical API retrieves a patient's records from US health information exchanges, pharmacies and labs, converts them to deduplicated FHIR, and returns them through a REST API with webhooks. Production use requires a covered entity with an NPI. One network query pulls a patient's records from HIEs, pharmacies and labs and returns deduplicated FHIR, with per-operation rate limits, RFC 7807 errors and AGPLv3 source. Each API key has full access with no scopes, there are no public prices, and the sandbox opens only after Metriport approves the account.

- Page: https://www.anchorterminal.com/tools/metriport · Markdown: https://www.anchorterminal.com/tools/metriport.md · JSON: https://www.anchorterminal.com/api/v1/tools/metriport.json
- Capabilities: health.records, health.fhir, health.consent, health.ehr

### 867. Particle Health, D (48.6)

Particle Health retrieves patient records from Carequality, CommonWell, eHealth Exchange, state HIEs and Surescripts, and returns them as FHIR R4B, flat datasets or C-CDA through a REST API, with Signal webhooks for care events. Particle queries Carequality, CommonWell, eHealth Exchange and state HIEs for a patient and returns FHIR R4B, flat data or C-CDA, with project-scoped 60-minute tokens and OpenAPI fragments per endpoint. Credentials come through a representative, the free sign-up link was dead on 14 October 2026, and rate limits, SLA and changelog are unpublished.

- Page: https://www.anchorterminal.com/tools/particle-health · Markdown: https://www.anchorterminal.com/tools/particle-health.md · JSON: https://www.anchorterminal.com/api/v1/tools/particle-health.json
- Capabilities: health.records, health.fhir

### 903. 1upHealth, D (46.8)

1upHealth runs FHIR APIs for US health plans, including the CMS Patient Access, Provider Access and Payer-to-Payer APIs, which let member-authorised third-party apps read claims, coverage and clinical data. Self-serve Dev Portal sandbox clients and a demo health plan let an app test the CMS Patient Access, Provider Access and Payer-to-Payer FHIR APIs, backed by HITRUST and SOC 2 Type 2. No rate limits, error formats or dated releases are documented, and the Patient Access OAuth step needs the member in a browser.

- Page: https://www.anchorterminal.com/tools/1uphealth · Markdown: https://www.anchorterminal.com/tools/1uphealth.md · JSON: https://www.anchorterminal.com/api/v1/tools/1uphealth.json
- Capabilities: health.records, health.fhir, health.consent

## How we test this category

In this run, public evidence against the published checklist. When the task suites run, one synthetic patient queried through each listing's sandbox. We request records or wearable data, write an observation where the API allows it, and read it back. We check FHIR conformance, the consent step, latency and what access took. This test hasn't run yet, so Task success is pending and the grades here come from the categories assessed from public evidence.