Write a review

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

Medblocks vs Zus Health

Zus Health scores 56.6 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on agent ergonomics, security & auth, payments & pricing and maintenance & community. Both do patient record retrieval.

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

MedblocksMedblocks Inc. · HTTP API D52.7/100#773 of 1076 Zus HealthZus Health, Inc. · HTTP API C56.6/100#669 of 1076

Which one, for what

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

  • Agent ergonomics, 72 against 67
  • Security & auth, 67 against 49
  • Payments & pricing, 25 against 5
  • Maintenance & community, 69 against 64

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

Zus Health C

Best for US care organisations and digital health builders that want a shared, continuously refreshed patient profile in FHIR with EHR embedding.

Ahead on

  • Reliability, 66 against 28
  • Schema & documentation, 77 against 62
  • Transparency & trust, 59 against 51

Watch for

No public prices, and the sandbox is requested through a Google Form

Score by category

CategoryWeight this runMedblocksZus HealthEdge
Reliability16%202866Zus Health +38
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26277Zus Health +15
Agent ergonomics13%16.27267Medblocks +5
Security & auth14%17.56749Medblocks +18
Payments & pricing10%12.5255Medblocks +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86964Medblocks +5
Transparency & trust7%8.85159Zus Health +8
Negative events≤1500
TotalD 52.7/100C 56.6/100

Facts side by side

FactMedblocksZus Health
KindHTTP APIHTTP API
VendorMedblocks Inc.Zus Health, Inc.
Hosted endpointhttps://app.medblocks.com/mcpno (local only)
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth
PricingFreemiumPaid
x402nono
LicenceProprietary 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 fileProprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum
Tools exposed10none
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-142026-10-14
Terms last updated2026-10-052025-03-11
Privacy policy last updated2026-10-052026-06-24
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity36 npm/wknone

Verdicts

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.

Zus Health

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.

Before you call either

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

Zus Health

  1. Cache the access token for its hour. More than 200 token requests an hour per App Client returns 429
  2. Request Patient History at most once per patient per 24 hours, and poll the job status endpoint
  3. Use conditional create by identifier so a retried write doesn't duplicate a resource
  4. Send Zus-If-Match with the resource's ETag on PUT and PATCH
  5. Set _count up to 500 on searches, since the default page is 10

Questions

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

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

Do Medblocks and Zus Health need an API key?

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

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

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

Other comparisons with Medblocks or Zus Health

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