Head to head · FHIR servers · October 2026 research run

Health Gorilla vs Terra API

Terra API scores 65.9 (B) on agent readiness against Health Gorilla's 59.3 (C), and leads in 5 of 7 scored categories. Health Gorilla leads on transparency & trust. Both do fhir servers.

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

Which one, for what

Health Gorilla C

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

  • Transparency & trust, 61 against 56

Watch for

No public prices. Fees are set case by case and the sandbox is requested by form

Terra API B

Best for A fitness, wellness, insurance or research product whose users connect consumer wearables and apps, and an agent that needs to read one user's sleep, activity or body data through MCP.

Ahead on

  • Reliability, 67 against 58
  • Schema & documentation, 89 against 80
  • Agent ergonomics, 78 against 72
  • Payments & pricing, 20 against 5
  • Maintenance & community, 75 against 63

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No free tier. Sign-up asks for a plan and billing details, and Quick Start starts at $499 a month with a 30-day money-back guarantee

Score by category

CategoryWeight this runHealth GorillaTerra APIEdge
Reliability16%205867Terra API +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28089Terra API +9
Agent ergonomics13%16.27278Terra API +6
Security & auth14%17.56665Health Gorilla +1
Payments & pricing10%12.5520Terra API +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86375Terra API +12
Transparency & trust7%8.86156Health Gorilla +5
Negative events≤1500
TotalC 59.3/100B 65.9/100

Facts side by side

FactHealth GorillaTerra API
KindHTTP APIHTTP API
VendorHealth Gorilla, Inc.Terra Enabling Developers Inc.
Hosted endpointno (local only)https://access.tryterra.co/api/v2/mcp/<user_id>
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidPay per use
x402nono
LicenceProprietary service under Health Gorilla's API Terms of Use (updated 22 January 2026), with a signed licence agreement required before productionProprietary service under Terra's terms of service. The OpenAPI specs repository is Apache 2.0
Tools exposednone6
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-142026-10-13
Terms last updatedno date given2026-05-01
Privacy policy last updated2024-08-302023-04-20
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textyes
Popularitynone13k npm/wk, 11k PyPI/wk

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.

Terra API

Graded on the Unified API and the Terra AI MCP server. A public OpenAPI 3.1 spec, llms.txt, per-user rate limits with Retry-After, and scoped admin tokens with approvals. Access starts at $499 a month with billing details at sign-up, the data API key has no scopes, and API key requests failed for 2 hours 38 minutes on 7 August 2026.

Before you call either

Health Gorilla

  1. Send a fresh UUID in HG-Idempotency-Key on every POST and reuse it only when retrying the same payload
  2. Poll async operations no sooner than the Retry-After value and treat 454 as an expired result
  3. Follow link.relation=next in Bundles rather than building offsets yourself
  4. Expect mocked Patient360 data in sandbox unless network connectivity is enabled for the tenant
  5. Log X-HG-Request-Id from each response for support cases

Terra API

  1. Send dev-id and x-api-key headers on every Unified API and Terra AI call. A missing header returns 401 problem+json
  2. Keep each request window to 1,825 days or less and under 6,000 requested days per user an hour. On 429 with rule r2, wait Retry-After seconds
  3. Pass either fields or select to Terra AI tools, never both and never neither, or the call fails with a validation error
  4. Expect data by webhook after a user connects through the widget session. REST reads are for backfills and on-demand queries
  5. Use the Read only access level for the admin MCP server unless a change is needed. The MCP level can read API keys

Questions

Which is better for AI agents, Health Gorilla or Terra API?

Terra API scores 65.9 (B) on agent readiness against Health Gorilla's 59.3 (C), and leads in 5 of 7 scored categories. Health Gorilla leads on transparency & trust.

Do Health Gorilla and Terra API need an API key?

Health Gorilla uses an OAuth sign-in. Terra API takes an API key or an OAuth sign-in.

Can an agent call Health Gorilla and Terra API without installing anything?

No hosted endpoint is listed for Health Gorilla. Terra API has a hosted endpoint at https://access.tryterra.co/api/v2/mcp/<user_id>.

Other comparisons with Health Gorilla or Terra API

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.