Category · Domain data
Health record and wellness data APIs for AI agents
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.
Best health record and wellness data APIs for AI agents, the shortlist · 63 head-to-head comparisons
Capability keys health.records · health.fhir · health.ehr · health.wearables · health.consent · All tools
letme.dev/health.records picks the top-graded tool in this list and says how to call it direct; calling through letme comes later.
The same listing from the live API. Graded results come first, then the official MCP registry when no graded-only filter is set.
https://www.anchorterminal.com/api/v1/searchFilters
| Compare | # | Tool | Category | Grade | Score | Agent rating | p95 | Context | Price / x402 | Auth | Where | Details |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 216 | MedplumOrangebot, Inc. (dba Medplum) · HTTP API | Health | B | 68.7 | none | n/a | n/a | $2000 / mo | OAuth | Hosted | ||
|
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. Top strength Apache 2.0 server with releases about weekly, v5.2.3 on 8 October 2026, and a written version policy Top weakness The MCP |
||||||||||||
| 327 | Terra APITerra Enabling Developers Inc. · HTTP API | Health | B | 65.9 | none | n/a | n/a | $499 / mo | OAuth or key | Hosted | ||
|
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. Top strength Public OpenAPI 3.1 specs on GitHub under Apache 2.0, republished almost daily (spec version 2026.10.08.1 for the Unified API) Top weakness No free tier. Sign-up asks for a plan and billing details, and Quick Start starts at $499 a month with a 30-day money-back guarantee |
||||||||||||
| 385 | AidboxHealth Samurai, Inc. · HTTP API | Health | B | 64.2 | none | n/a | n/a | $1900 / mo | OAuth | Local | ||
|
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. Top strength Monthly releases with dated notes, the latest 2609 on 8 October 2026, and LTS lines supported for two years Top weakness No built-in rate limiting or brute-force protection, by the vendor's hardening page |
||||||||||||
| 583 | Health GorillaHealth Gorilla, Inc. · HTTP API | Health | C | 59.3 | none | n/a | n/a | Paid | OAuth | Local | ||
|
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. Top strength Designated TEFCA QHIN with Patient360 retrieval across national networks, plus lab orders and ADT alerts Top weakness No public prices. Fees are set case by case and the sandbox is requested by form |
||||||||||||
| 618 | RedoxRedox, Inc. · HTTP API | Health | C | 58.3 | none | n/a | n/a | Paid | OAuth | Hosted | ||
|
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. Top strength OAuth API keys signed with the client's own private key, with JWKS URL support and rotation guidance Top weakness The MCP server loads 107 tools in one set, including write and delete tools with no confirmation step |
||||||||||||
| 628 | Validic InformValidic, Inc. (ChartSpan) · HTTP API | Health | C | 57.9 | none | n/a | n/a | Freemium | API key | Local | ||
|
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. Top strength Sign-up, email verification and organisation provisioning are all API calls, with an agent guide at dashboard.validic.com/agents.txt Top weakness The organisation token is sent as |
||||||||||||
| 669 | Zus HealthZus Health, Inc. · HTTP API | Health | C | 56.6 | none | n/a | n/a | Paid | OAuth | Local | ||
|
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. Top strength One profile per patient from EHR, pharmacy, ADT and lab networks, shared across Zus customers treating the same patient Top weakness No public prices, and the sandbox is requested through a Google Form |
||||||||||||
| 718 | ROOKRookeries Development Corp. · HTTP API | Health | C | 54.9 | none | n/a | n/a | $399 / mo | API key | Local | ||
|
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. Top strength OpenAPI 3.0.3 file with 29 operations and production and sandbox servers, linked from the API reference Top weakness Credentials are one client UUID and secret per environment, sent by Basic auth, with no scopes or rotation documented |
||||||||||||
| 773 | MedblocksMedblocks Inc. · HTTP API | Health | D | 52.7 | none | n/a | n/a | $5000 / mo | OAuth or key | Hosted | ||
|
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. Top strength Remote MCP server with ten tools, OAuth with dynamic client registration and a consent screen that can leave destructive actions off Top weakness No status page, SLA or published rate limits for the Platform API |
||||||||||||
| 833 | Metriport Medical APIMetriport Inc. · HTTP API | Health | D | 50.1 | none | n/a | n/a | Paid | API key | Local | ||
|
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. Top strength One asynchronous network query covers HIEs, pharmacies and labs, with a webhook as each source is merged Top weakness Every API key has full access, including destructive operations, with no scopes |
||||||||||||
| 867 | Particle HealthParticle Health, Inc. · HTTP API | Health | D | 48.6 | none | n/a | n/a | Paid | OAuth | Local | ||
|
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. Top strength Connected to all three national networks plus Healthix, Manifest MedEx and Surescripts Top weakness Credentials come from a Particle representative, and the 'play for free' sign-up domain did not resolve |
||||||||||||
| 903 | 1upHealth1upHealth, Inc. · HTTP API | Health | D | 46.8 | none | n/a | n/a | Paid | OAuth | Local | ||
|
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. Top strength Sandbox client credentials from the Dev Portal with only an email verification Top weakness No rate limits, 429 handling or error formats documented |
||||||||||||
Nothing matches these filters. .
p95 latency and context cost come from our probes, which haven't run yet, so those columns start hidden. Grades run from AA to F, and agent-ready means BB or better. Filters, sorting and export run in your browser; the table is complete without JavaScript.
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.
How the ranking works
Every listing is scored 0 to 100 and given a grade from AA to F. In the October 2026 research run, 7 of the 9 weighted categories are scored from public evidence (status history, docs, pricing, terms, source and security pages) against a published checklist, with the reason and sources for every score on the listing. Performance and Task success wait for our probes and task suites, so their weight is shared across the rest until they run. Negative events deduct up to 15 points. Read the methodology.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.