Write a review

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

Metriport Medical API vs Particle Health

Metriport Medical API scores 50.1 (D) on agent readiness against Particle Health's 48.6 (D), and leads in 3 of 7 scored categories. Particle Health leads on reliability and security & auth. Both do patient record retrieval.

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

Metriport Medical APIMetriport Inc. · HTTP API D50.1/100#833 of 1076 Particle HealthParticle Health, Inc. · HTTP API D48.6/100#867 of 1076

Which one, for what

Metriport Medical API D

Best for US care providers and digital health companies that need a patient's network records as FHIR with webhooks.

Ahead on

  • Agent ergonomics, 70 against 53
  • Maintenance & community, 74 against 27
  • Transparency & trust, 56 against 48

Also in its favour

  • Open source

Watch for

Every API key has full access, including destructive operations, with no scopes

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 45
  • Security & auth, 57 against 41

Watch for

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

Score by category

CategoryWeight this runMetriport Medical APIParticle HealthEdge
Reliability16%204558Particle Health +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26569Particle Health +4
Agent ergonomics13%16.27053Metriport Medical API +17
Security & auth14%17.54157Particle Health +16
Payments & pricing10%12.555even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87427Metriport Medical API +47
Transparency & trust7%8.85648Metriport Medical API +8
Negative events≤1500
TotalD 50.1/100D 48.6/100

Facts side by side

FactMetriport Medical APIParticle Health
KindHTTP APIHTTP API
VendorMetriport Inc.Particle Health, Inc.
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthAPI keyOAuth
PricingPaidPaid
x402nono
LicenceProprietary hosted service under Metriport's terms of use. The source in metriport/metriport is AGPLv3, with an enterprise directory under its own licence, and the @metriport/api-sdk package on npm is MITProprietary service under customer agreements. The public terms of use (effective 15 October 2020) cover the website only
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-28none
Terms last updated2024-01-012020-10-15
Privacy policy last updated2023-02-212026-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 waiveryesyes
Popularity793 stars, 28k npm/wknone

Verdicts

Metriport Medical API

One network query pulls a patient's records from HIEs, pharmacies and labs and returns deduplicated FHIR, with per-operation rate limits, RFC 7807 errors and AGPLv3 source. Each API key has full access with no scopes, there are no public prices, and the sandbox opens only after Metriport approves the account.

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

Metriport Medical API

  1. Check the errors array after Start Network Query. It returns 2XX even when some sources fail
  2. Wait for network-query.* webhooks or poll Get Network Query Status before reading consolidated data, which is cached from the last query
  3. Send the resource's eTag in If-Match on updates to avoid overwriting newer data
  4. Keep patient creates under 15 a minute and network queries under 20 a minute per source
  5. In sandbox, create patients whose first name matches a pre-defined persona to get example records

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, Metriport Medical API or Particle Health?

Metriport Medical API scores 50.1 (D) on agent readiness against Particle Health's 48.6 (D), and leads in 3 of 7 scored categories. Particle Health leads on reliability and security & auth.

Do Metriport Medical API and Particle Health need an API key?

Metriport Medical API needs an API key. Particle Health uses an OAuth sign-in.

Can an agent call Metriport Medical API and Particle Health without installing anything?

No hosted endpoint is listed for Metriport Medical API. No hosted endpoint is listed for Particle Health.

Are Metriport Medical API and Particle Health open source?

Metriport Medical API is open source (Proprietary hosted service under Metriport's terms of use. The source in metriport/metriport is AGPLv3, with an enterprise directory under its own licence, and the @metriport/api-sdk package on npm is MIT). No open-source release is listed for Particle Health.

Other comparisons with Metriport Medical API 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