Write a review

Head to head · Patient record retrieval · October 2026 research run

Health Gorilla vs Medplum

Medplum scores 68.7 (B) on agent readiness against Health Gorilla's 59.3 (C), and leads in every scored category. Both do patient record retrieval.

Best health record and wellness data APIs for AI agents · All 63 health comparisons

Health GorillaHealth Gorilla, Inc. · HTTP API C59.3/100#583 of 1076 MedplumOrangebot, Inc. (dba Medplum) · HTTP API B68.7/100#216 of 1076

Which one, for what

Health Gorilla C

Best for US providers, labs and digital health companies that need network record retrieval and lab ordering through one FHIR API with a QHIN behind it.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No public prices. Fees are set case by case and the sandbox is requested by form

Medplum B

Best for An agent working inside a digital health company's own FHIR store, reading and writing patients, observations and appointments under a BAA.

Ahead on

  • Reliability, 75 against 58
  • Security & auth, 74 against 66
  • Payments & pricing, 25 against 5
  • Maintenance & community, 93 against 63
  • Transparency & trust, 72 against 61

Also in its favour

  • A hosted endpoint, with nothing to install
  • Open source

Watch for

The MCP fhir-request tool can delete or overwrite any resource the token allows, with no readOnlyHint or destructiveHint

Score by category

CategoryWeight this runHealth GorillaMedplumEdge
Reliability16%205875Medplum +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28082Medplum +2
Agent ergonomics13%16.27273Medplum +1
Security & auth14%17.56674Medplum +8
Payments & pricing10%12.5525Medplum +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86393Medplum +30
Transparency & trust7%8.86172Medplum +11
Negative events≤150-2
TotalC 59.3/100B 68.7/100

Facts side by side

FactHealth GorillaMedplum
KindHTTP APIHTTP API
VendorHealth Gorilla, Inc.Orangebot, Inc. (dba Medplum)
Hosted endpointno (local only)https://api.medplum.com/mcp/stream
TransportsHTTPHTTP, Streamable HTTP, SSE (legacy)
AuthOAuthOAuth
PricingPaidFreemium
x402nono
LicenceProprietary service under Health Gorilla's API Terms of Use (updated 22 January 2026), with a signed licence agreement required before productionApache 2.0 for the server, SDKs and apps in medplum/medplum. The hosted service at api.medplum.com runs under Medplum's terms of service
Tools exposednone3
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listedcom.medplum/mcp
Last release2026-10-142026-10-08
Terms last updatedno date given2023-04-11
Privacy policy last updated2024-08-302022-04-05
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textyes
Popularitynone2.7k stars, 270k npm/wk

Verdicts

Health Gorilla

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.

Medplum

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.

Before you call either

Health Gorilla

  1. Send a fresh UUID in HG-Idempotency-Key on every POST and reuse it only when retrying the same payload
  2. Poll async operations no sooner than the Retry-After value and treat 454 as an expired result
  3. Follow link.relation=next in Bundles rather than building offsets yourself
  4. Expect mocked Patient360 data in sandbox unless network connectivity is enabled for the tenant
  5. Log X-HG-Request-Id from each response for support cases

Medplum

  1. Use a ClientApplication with an AccessPolicy limited to the resources the task needs, and set readonly where no writes are needed
  2. Read the RateLimit header and wait for the reset time after a 429. Writes cost 100 quota points, searches 20 and reads 1
  3. Create patients with conditional create (If-None-Exist) or upsert on an identifier so a retry doesn't make a duplicate
  4. Pass paths to fhir-request relative to the FHIR R4 base, with no leading slash or /fhir/R4 prefix
  5. Use Prefer: respond-async for large bundles. Operations inside the background job don't count against the quota

Questions

Which is better for AI agents, Health Gorilla or Medplum?

Medplum scores 68.7 (B) on agent readiness against Health Gorilla's 59.3 (C), and leads in every scored category.

Do Health Gorilla and Medplum need an API key?

Both use an OAuth sign-in.

Can an agent call Health Gorilla and Medplum without installing anything?

No hosted endpoint is listed for Health Gorilla. Medplum has a hosted endpoint at https://api.medplum.com/mcp/stream.

Are Health Gorilla and Medplum open source?

No open-source release is listed for Health Gorilla. Medplum is open source (Apache 2.0 for the server, SDKs and apps in medplum/medplum. The hosted service at api.medplum.com runs under Medplum's terms of service).

Other comparisons with Health Gorilla or Medplum

Machine-readable

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.

Get an auditSee a sample report