Write a review

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

1upHealth vs Medblocks

Medblocks scores 52.7 (D) on agent readiness against 1upHealth's 46.8 (D), and leads in 5 of 7 scored categories. 1upHealth leads on reliability and transparency & trust. Both do patient record retrieval.

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

1upHealth1upHealth, Inc. · HTTP API D46.8/100#903 of 1076 MedblocksMedblocks Inc. · HTTP API D52.7/100#773 of 1076

Which one, for what

1upHealth D

Best for Consumer and care apps that read a member's health plan claims and clinical data under the CMS rules, and payers meeting those rules.

Ahead on

  • Reliability, 52 against 28
  • Transparency & trust, 72 against 51

Watch for

No rate limits, 429 handling or error formats documented

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

  • Schema & documentation, 62 against 50
  • Agent ergonomics, 72 against 32
  • Payments & pricing, 25 against 20
  • Maintenance & community, 69 against 37

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

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

Score by category

CategoryWeight this run1upHealthMedblocksEdge
Reliability16%2052281upHealth +24
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25062Medblocks +12
Agent ergonomics13%16.23272Medblocks +40
Security & auth14%17.56367Medblocks +4
Payments & pricing10%12.52025Medblocks +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83769Medblocks +32
Transparency & trust7%8.872511upHealth +21
Negative events≤1500
TotalD 46.8/100D 52.7/100

Facts side by side

Fact1upHealthMedblocks
KindHTTP APIHTTP API
Vendor1upHealth, Inc.Medblocks Inc.
Hosted endpointno (local only)https://app.medblocks.com/mcp
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under 1upHealth's Terms of Service (effective 1 August 2024)Proprietary 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 file
Tools exposednone10
Read-only variant documentednono
llms.txtyesyes
Last releasenone2026-09-14
Terms last updatedno date given2026-10-05
Privacy policy last updated2026-06-252026-10-05
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone36 npm/wk

Verdicts

1upHealth

Self-serve Dev Portal sandbox clients and a demo health plan let an app test the CMS Patient Access, Provider Access and Payer-to-Payer FHIR APIs, backed by HITRUST and SOC 2 Type 2. No rate limits, error formats or dated releases are documented, and the Patient Access OAuth step needs the member in a browser.

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.

Before you call either

1upHealth

  1. Hand the Patient Access sign-in to the member, who must authorise in the health plan's auth app
  2. Exchange the authorisation code within five minutes, and refresh before the 15-minute token expires
  3. Email payer-patient-access@1up.health with the client ID to get the app synced to the demo environment
  4. Expect only claims and coverage resources from some payers, and read /r4/metadata first

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

Questions

Which is better for AI agents, 1upHealth or Medblocks?

Medblocks scores 52.7 (D) on agent readiness against 1upHealth's 46.8 (D), and leads in 5 of 7 scored categories. 1upHealth leads on reliability and transparency & trust.

Do 1upHealth and Medblocks need an API key?

1upHealth uses an OAuth sign-in. Medblocks takes an API key or an OAuth sign-in.

Can an agent call 1upHealth and Medblocks without installing anything?

No hosted endpoint is listed for 1upHealth. Medblocks has a hosted endpoint at https://app.medblocks.com/mcp.

Other comparisons with 1upHealth or Medblocks

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