Write a review

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

Health Gorilla vs Medblocks

Health Gorilla scores 59.3 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on payments & pricing and maintenance & community. 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 MedblocksMedblocks Inc. · HTTP API D52.7/100#773 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.

Ahead on

  • Reliability, 58 against 28
  • Schema & documentation, 80 against 62
  • Transparency & trust, 61 against 51

Watch for

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

Medblocks D

Best for A consumer or care app, or an assistant, that needs a patient's own records from US hospitals and payers with the patient's consent, and wants an MCP route as well as REST.

Ahead on

  • Payments & pricing, 25 against 5
  • Maintenance & community, 69 against 63

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No status page, SLA or published rate limits for the Platform API

Score by category

CategoryWeight this runHealth GorillaMedblocksEdge
Reliability16%205828Health Gorilla +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28062Health Gorilla +18
Agent ergonomics13%16.27272even
Security & auth14%17.56667Medblocks +1
Payments & pricing10%12.5525Medblocks +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86369Medblocks +6
Transparency & trust7%8.86151Health Gorilla +10
Negative events≤1500
TotalC 59.3/100D 52.7/100

Facts side by side

FactHealth GorillaMedblocks
KindHTTP APIHTTP API
VendorHealth Gorilla, Inc.Medblocks Inc.
Hosted endpointno (local only)https://app.medblocks.com/mcp
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Health Gorilla's API Terms of Use (updated 22 January 2026), with a signed licence agreement required before productionProprietary service under Medblocks' terms. The medblocks TypeScript SDK on npm carries a proprietary licence that forbids redistribution and reverse engineering. The agent skills repository has no licence file
Tools exposednone10
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-142026-09-14
Terms last updatedno date given2026-10-05
Privacy policy last updated2024-08-302026-10-05
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone36 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.

Medblocks

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.

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

Medblocks

  1. Connect with claude mcp add --transport http medblocks https://app.medblocks.com/mcp and sign in, or send a workspace API key as a Bearer token from a backend
  2. Ask the person before calling disconnect_health_system or delete_person. Both are permanent
  3. Wait for the connection webhook or check connection status before reading records. Pulls run in the background after the patient approves
  4. Branch on error.code, not the message, and wait the Retry-After seconds on a 429
  5. Use a Sandbox workspace and the Synthetic Hospital (password demopass) for tests. Sandbox keys cannot reach production sources

Questions

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

Health Gorilla scores 59.3 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on payments & pricing and maintenance & community.

Do Health Gorilla and Medblocks need an API key?

Health Gorilla uses an OAuth sign-in. Medblocks takes an API key or an OAuth sign-in.

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

No hosted endpoint is listed for Health Gorilla. Medblocks has a hosted endpoint at https://app.medblocks.com/mcp.

Other comparisons with Health Gorilla or Medblocks

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