Write a review

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

Medblocks vs Particle Health

Medblocks scores 52.7 (D) on agent readiness against Particle Health's 48.6 (D), and leads in 5 of 7 scored categories. Particle Health leads on reliability and schema & documentation. 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 Particle HealthParticle Health, Inc. · HTTP API D48.6/100#867 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 53
  • Security & auth, 67 against 57
  • Payments & pricing, 25 against 5
  • Maintenance & community, 69 against 27

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

Particle Health D

Best for US providers, payers and digital health companies that need a patient's network records as FHIR or flat data, and care-event alerts.

Ahead on

  • Reliability, 58 against 28
  • Schema & documentation, 69 against 62

Watch for

Credentials come from a Particle representative, and the 'play for free' sign-up domain did not resolve

Score by category

CategoryWeight this runMedblocksParticle HealthEdge
Reliability16%202858Particle Health +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26269Particle Health +7
Agent ergonomics13%16.27253Medblocks +19
Security & auth14%17.56757Medblocks +10
Payments & pricing10%12.5255Medblocks +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86927Medblocks +42
Transparency & trust7%8.85148Medblocks +3
Negative events≤1500
TotalD 52.7/100D 48.6/100

Facts side by side

FactMedblocksParticle Health
KindHTTP APIHTTP API
VendorMedblocks Inc.Particle 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 customer agreements. The public terms of use (effective 15 October 2020) cover the website only
Tools exposed10none
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-14none
Terms last updated2026-10-052020-10-15
Privacy policy last updated2026-10-052026-07-29
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textyes
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.

Particle Health

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.

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

Particle Health

  1. Pass projects/<project_id> as the scope when requesting a token, and request a new one every 60 minutes
  2. Poll Get Query Status, or wait for the query-complete webhook, before reading FHIR or flat data
  3. Back off on 429, since limits change with system load
  4. Pass continuation tokens back verbatim when paging
  5. Use the published synthetic patients in sandbox, and stay under 500 queries a day

Questions

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

Medblocks scores 52.7 (D) on agent readiness against Particle Health's 48.6 (D), and leads in 5 of 7 scored categories. Particle Health leads on reliability and schema & documentation.

Do Medblocks and Particle Health need an API key?

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

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

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

Other comparisons with Medblocks or Particle 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