Head to head · Patient record retrieval · October 2026 research run
Particle Health vs Zus Health
Zus Health scores 56.6 (C) on agent readiness against Particle Health's 48.6 (D), and leads in 5 of 7 scored categories. Particle Health leads on security & auth. Both do patient record retrieval.
Best health record and wellness data APIs for AI agents · All 63 health comparisons
Which one, for what
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
- Security & auth, 57 against 49
Watch for
Credentials come from a Particle representative, and the 'play for free' sign-up domain did not resolve
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 58
- Schema & documentation, 77 against 69
- Agent ergonomics, 67 against 53
- Maintenance & community, 64 against 27
- Transparency & trust, 59 against 48
Watch for
No public prices, and the sandbox is requested through a Google Form
Score by category
| Category | Weight this run | Particle Health | Zus Health | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 58 | 66 | Zus Health +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 69 | 77 | Zus Health +8 |
| Agent ergonomics | 13%16.2 | 53 | 67 | Zus Health +14 |
| Security & auth | 14%17.5 | 57 | 49 | Particle Health +8 |
| Payments & pricing | 10%12.5 | 5 | 5 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 27 | 64 | Zus Health +37 |
| Transparency & trust | 7%8.8 | 48 | 59 | Zus Health +11 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 48.6/100 | C 56.6/100 |
Facts side by side
| Fact | Particle Health | Zus Health |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Particle Health, Inc. | Zus Health, Inc. |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth | OAuth |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under customer agreements. The public terms of use (effective 15 October 2020) cover the website only | Proprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | none | 2026-10-14 |
| Terms last updated | 2020-10-15 | 2025-03-11 |
| Privacy policy last updated | 2026-07-29 | 2026-06-24 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
Verdicts
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.
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
Particle Health
- Pass
projects/<project_id>as the scope when requesting a token, and request a new one every 60 minutes - Poll Get Query Status, or wait for the query-complete webhook, before reading FHIR or flat data
- Back off on 429, since limits change with system load
- Pass continuation tokens back verbatim when paging
- Use the published synthetic patients in sandbox, and stay under 500 queries a day
Zus Health
- Cache the access token for its hour. More than 200 token requests an hour per App Client returns 429
- Request Patient History at most once per patient per 24 hours, and poll the job status endpoint
- Use conditional create by identifier so a retried write doesn't duplicate a resource
- Send
Zus-If-Matchwith the resource's ETag on PUT and PATCH - Set
_countup to 500 on searches, since the default page is 10
Questions
Which is better for AI agents, Particle Health or Zus Health?
Zus Health scores 56.6 (C) on agent readiness against Particle Health's 48.6 (D), and leads in 5 of 7 scored categories. Particle Health leads on security & auth.
Do Particle Health and Zus Health need an API key?
Both use an OAuth sign-in.
Can an agent call Particle Health and Zus Health without installing anything?
No hosted endpoint is listed for Particle Health. No hosted endpoint is listed for Zus Health.
Other comparisons with Particle Health or Zus Health
- Aidbox vs Particle Health
- Aidbox vs Zus Health
- Medplum vs Particle Health
- Medplum vs Zus Health
- Particle Health vs ROOK
- Particle Health vs Terra API
- 1upHealth vs Particle Health
- 1upHealth vs Zus Health
- Health Gorilla vs Particle Health
- Health Gorilla vs Zus Health
- Medblocks vs Particle Health
- Medblocks vs Zus Health
- Metriport Medical API vs Particle Health
- Metriport Medical API vs Zus Health
- Particle Health vs Redox
- ROOK vs Zus Health
- Terra API vs Zus Health
- Validic Inform vs Zus Health
- Redox vs Zus Health
Machine-readable
- This page as Markdown
/compare/particle-health-vs-zus-health.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/particle-health.json·/api/v1/tools/zus-health.json - From a terminal
anchor compare particle-health zus-health(the CLI) - Over MCP
compare_tools {"a": "particle-health", "b": "zus-health"}at/mcp, no key