Head to head · Patient record retrieval · October 2026 research run
Health Gorilla vs Zus Health
Health Gorilla scores 59.3 (C) on agent readiness against Zus Health's 56.6 (C), and leads in 4 of 7 scored categories. Zus Health leads on reliability. 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, labs and digital health companies that need network record retrieval and lab ordering through one FHIR API with a QHIN behind it.
Ahead on
- Agent ergonomics, 72 against 67
- Security & auth, 66 against 49
Watch for
No public prices. Fees are set case by case and the sandbox is requested by form
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
Watch for
No public prices, and the sandbox is requested through a Google Form
Score by category
| Category | Weight this run | Health Gorilla | 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 | 80 | 77 | Health Gorilla +3 |
| Agent ergonomics | 13%16.2 | 72 | 67 | Health Gorilla +5 |
| Security & auth | 14%17.5 | 66 | 49 | Health Gorilla +17 |
| Payments & pricing | 10%12.5 | 5 | 5 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 63 | 64 | Zus Health +1 |
| Transparency & trust | 7%8.8 | 61 | 59 | Health Gorilla +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 59.3/100 | C 56.6/100 |
Facts side by side
| Fact | Health Gorilla | Zus Health |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Health Gorilla, 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 Health Gorilla's API Terms of Use (updated 22 January 2026), with a signed licence agreement required before production | 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 | 2026-10-14 | 2026-10-14 |
| Terms last updated | no date given | 2025-03-11 |
| Privacy policy last updated | 2024-08-30 | 2026-06-24 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
Verdicts
Health Gorilla
A TEFCA QHIN with a FHIR R4 API, OpenAPI fragments on every reference page, idempotency keys on POST and dated weekly release notes. Access is sales-led, with case-by-case fees, a sandbox by request and no published rate limit numbers, and the API terms allow access to be cut at any time.
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
Health Gorilla
- Send a fresh UUID in
HG-Idempotency-Keyon every POST and reuse it only when retrying the same payload - Poll async operations no sooner than the
Retry-Aftervalue and treat 454 as an expired result - Follow
link.relation=nextin Bundles rather than building offsets yourself - Expect mocked Patient360 data in sandbox unless network connectivity is enabled for the tenant
- Log
X-HG-Request-Idfrom each response for support cases
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, Health Gorilla or Zus Health?
Health Gorilla scores 59.3 (C) on agent readiness against Zus Health's 56.6 (C), and leads in 4 of 7 scored categories. Zus Health leads on reliability.
Do Health Gorilla and Zus Health need an API key?
Both use an OAuth sign-in.
Can an agent call Health Gorilla and Zus Health without installing anything?
No hosted endpoint is listed for Health Gorilla. No hosted endpoint is listed for Zus Health.
Other comparisons with Health Gorilla or Zus Health
- Aidbox vs Health Gorilla
- Aidbox vs Zus Health
- Health Gorilla vs ROOK
- Health Gorilla vs Terra API
- Medplum vs Zus Health
- 1upHealth vs Health Gorilla
- 1upHealth vs Zus Health
- Health Gorilla vs Medblocks
- Health Gorilla vs Medplum
- Health Gorilla vs Metriport Medical API
- Health Gorilla vs Particle Health
- Health Gorilla vs Redox
- Medblocks vs Zus Health
- Metriport Medical API vs Zus Health
- Particle Health vs Zus Health
- Health Gorilla vs Validic Inform
- 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/health-gorilla-vs-zus-health.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/health-gorilla.json·/api/v1/tools/zus-health.json - From a terminal
anchor compare health-gorilla zus-health(the CLI) - Over MCP
compare_tools {"a": "health-gorilla", "b": "zus-health"}at/mcp, no key