Write a review

Head to head · FHIR servers · October 2026 research run

Medplum vs Particle Health

Medplum scores 68.7 (B) on agent readiness against Particle Health's 48.6 (D), and leads in every scored category. Both do fhir servers.

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

MedplumOrangebot, Inc. (dba Medplum) · HTTP API B68.7/100#216 of 1076 Particle HealthParticle Health, Inc. · HTTP API D48.6/100#867 of 1076

Which one, for what

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
  • Schema & documentation, 82 against 69
  • Agent ergonomics, 73 against 53
  • Security & auth, 74 against 57
  • Payments & pricing, 25 against 5
  • Maintenance & community, 93 against 27
  • Transparency & trust, 72 against 48

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

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.

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

Watch for

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

Score by category

CategoryWeight this runMedplumParticle HealthEdge
Reliability16%207558Medplum +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28269Medplum +13
Agent ergonomics13%16.27353Medplum +20
Security & auth14%17.57457Medplum +17
Payments & pricing10%12.5255Medplum +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.89327Medplum +66
Transparency & trust7%8.87248Medplum +24
Negative events≤15-20
TotalB 68.7/100D 48.6/100

Facts side by side

FactMedplumParticle Health
KindHTTP APIHTTP API
VendorOrangebot, Inc. (dba Medplum)Particle Health, Inc.
Hosted endpointhttps://api.medplum.com/mcp/streamno (local only)
TransportsHTTP, Streamable HTTP, SSE (legacy)HTTP
AuthOAuthOAuth
PricingFreemiumPaid
x402nono
LicenceApache 2.0 for the server, SDKs and apps in medplum/medplum. The hosted service at api.medplum.com runs under Medplum's terms of serviceProprietary service under customer agreements. The public terms of use (effective 15 October 2020) cover the website only
Tools exposed3none
Read-only variant documentedyesno
llms.txtyesyes
MCP registrycom.medplum/mcpnot listed
Last release2026-10-08none
Terms last updated2023-04-112020-10-15
Privacy policy last updated2022-04-052026-07-29
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity2.7k stars, 270k npm/wknone

Verdicts

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.

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

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

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, Medplum or Particle Health?

Medplum scores 68.7 (B) on agent readiness against Particle Health's 48.6 (D), and leads in every scored category.

Do Medplum and Particle Health need an API key?

Both use an OAuth sign-in.

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

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

Are Medplum and Particle Health open source?

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). No open-source release is listed for Particle Health.

Other comparisons with Medplum 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