Write a review

Head to head · Patient consent · October 2026 research run

Medblocks vs Terra API

Terra API scores 65.9 (B) on agent readiness against Medblocks's 52.7 (D), and leads in 5 of 7 scored categories. Medblocks leads on payments & pricing. Both do patient consent.

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

MedblocksMedblocks Inc. · HTTP API D52.7/100#773 of 1076 Terra APITerra Enabling Developers Inc. · HTTP API B65.9/100#327 of 1076

Which one, for what

Medblocks D

Best for A consumer or care app, or an assistant, that needs a patient's own records from US hospitals and payers with the patient's consent, and wants an MCP route as well as REST.

Ahead on

  • Payments & pricing, 25 against 20

Watch for

No status page, SLA or published rate limits for the Platform API

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 28
  • Schema & documentation, 89 against 62
  • Agent ergonomics, 78 against 72
  • Maintenance & community, 75 against 69
  • Transparency & trust, 56 against 51

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 runMedblocksTerra APIEdge
Reliability16%202867Terra API +39
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26289Terra API +27
Agent ergonomics13%16.27278Terra API +6
Security & auth14%17.56765Medblocks +2
Payments & pricing10%12.52520Medblocks +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86975Terra API +6
Transparency & trust7%8.85156Terra API +5
Negative events≤1500
TotalD 52.7/100B 65.9/100

Facts side by side

FactMedblocksTerra API
KindHTTP APIHTTP API
VendorMedblocks Inc.Terra Enabling Developers Inc.
Hosted endpointhttps://app.medblocks.com/mcphttps://access.tryterra.co/api/v2/mcp/<user_id>
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPay per use
x402nono
LicenceProprietary service under Medblocks' terms. The medblocks TypeScript SDK on npm carries a proprietary licence that forbids redistribution and reverse engineering. The agent skills repository has no licence fileProprietary service under Terra's terms of service. The OpenAPI specs repository is Apache 2.0
Tools exposed106
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-142026-10-13
Terms last updated2026-10-052026-05-01
Privacy policy last updated2026-10-052023-04-20
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textyes
Popularity36 npm/wk13k npm/wk, 11k PyPI/wk

Verdicts

Medblocks

Patient-authorised record retrieval with a ten-tool remote MCP server, OAuth with per-capability consent, an audit entry for every call and a free plan for 1,000 active patients. No status page, no published rate limits and no idempotency keys were found, and the OpenAPI file behind the reference is not published.

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

Medblocks

  1. Connect with claude mcp add --transport http medblocks https://app.medblocks.com/mcp and sign in, or send a workspace API key as a Bearer token from a backend
  2. Ask the person before calling disconnect_health_system or delete_person. Both are permanent
  3. Wait for the connection webhook or check connection status before reading records. Pulls run in the background after the patient approves
  4. Branch on error.code, not the message, and wait the Retry-After seconds on a 429
  5. Use a Sandbox workspace and the Synthetic Hospital (password demopass) for tests. Sandbox keys cannot reach production sources

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, Medblocks or Terra API?

Terra API scores 65.9 (B) on agent readiness against Medblocks's 52.7 (D), and leads in 5 of 7 scored categories. Medblocks leads on payments & pricing.

Do Medblocks and Terra API need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Medblocks and Terra API without installing anything?

Yes. Medblocks has a hosted endpoint at https://app.medblocks.com/mcp and Terra API at https://access.tryterra.co/api/v2/mcp/<user_id>.

Other comparisons with Medblocks 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.

Get an auditSee a sample report