{ "data": { "a": { "slug": "medblocks", "name": "Medblocks", "vendor": "Medblocks Inc.", "vendorUrl": "https://medblocks.com", "kind": "http-api", "category": "health-data", "summary": "Medblocks Platform lets an app or agent connect a patient's hospital, clinic and insurer records through SMART on FHIR and read them back as FHIR R4, through a REST API, a TypeScript SDK or a remote MCP server.", "url": "https://www.anchorterminal.com/tools/medblocks", "markdownUrl": "https://www.anchorterminal.com/tools/medblocks.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/medblocks.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/medblocks.json", "repo": "https://github.com/medblocks/skills", "license": "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", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://app.medblocks.com/mcp", "packages": [ { "registry": "npm", "name": "medblocks" } ], "auth": "mixed", "authNotes": "The REST API takes a workspace API key as a Bearer token (`mb_sk_sbx_` for Sandbox, `mb_sk_live_` for Production). Owners and admins mint, rotate and revoke keys in the dashboard, and the full key is shown once. The MCP server at https://app.medblocks.com/mcp also accepts OAuth from Medblocks' own authorisation server, which publishes dynamic client registration, PKCE and ten scopes (patients:read, patients:write, fhir:read and others), with a consent screen of three tick boxes. Patients authorise each hospital themselves through SMART on FHIR. A BAA is needed before production use.", "pricing": "freemium", "pricingNotes": "Free plan at $0 for up to 1,000 active patients, with patient access, synthetic sandboxes and full API access. Enterprise is $60,000 a year with no patient cap and adds backend services, clinical workflows, OCR and data structuring. A patient counts as active from the first successful FHIR pull. Upgrades go through support@medblocks.com, and requests outside the plan return 402 `billing_error` (checked 2026-10-14).", "priceSummary": "$5000 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, llms-full.txt or the billing page. A 402 status is used only for `billing_error` when a plan does not cover a feature (checked 2026-10-14).", "endpoints": [] }, "toolCount": 10, "popularity": { "githubStars": null, "npmWeekly": 36, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://medblocks.com/docs", "llmsTxt": "https://medblocks.com/docs/llms.txt", "capabilities": [ "health.records", "health.consent", "health.ehr", "health.fhir", "agent.tools" ], "tags": [ "hosted", "mcp", "oauth", "fhir", "smart-on-fhir", "typescript", "llms-txt", "free-tier", "hipaa" ], "lastRelease": "2026-09-14", "graded": true, "anchor": { "graded": true, "score": 52.7, "grade": "D", "agentReady": false, "rank": 773, "ranked": true, "rankOf": 1076, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 69, "payments": 25, "reliability": 28, "schema": 62, "security": 67, "transparency": 51 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Remote MCP server with ten tools, OAuth with dynamic client registration and a consent screen that can leave destructive actions off", "Free plan for up to 1,000 active patients and a Synthetic Hospital sandbox with seeded FHIR R4 patients", "One error envelope with 36 stable codes, a `param` field, a request ID and `Retry-After` on 429", "Every MCP tool call writes an audit entry, and the dashboard shows authorisation and pull history per patient", "llms.txt, llms-full.txt and a Markdown copy of every docs page, plus agent skills for Claude Code, Codex and Cursor" ], "weaknesses": [ "No status page, SLA or published rate limits for the Platform API", "No idempotency keys were found, and the API conventions and versioning pages are unwritten placeholders", "The OpenAPI file the reference is generated from is not published", "Only one SDK, in TypeScript, with npm's latest tag still at 1.0.0 while the changelog documents 1.2.0", "The public terms cover the website and Blue Button app, and no sub-processor list or customer terms for the API were found" ], "agentNotes": [ "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", "Ask the person before calling `disconnect_health_system` or `delete_person`. Both are permanent", "Wait for the connection webhook or check connection status before reading records. Pulls run in the background after the patient approves", "Branch on `error.code`, not the message, and wait the `Retry-After` seconds on a 429", "Use a Sandbox workspace and the Synthetic Hospital (password `demopass`) for tests. Sandbox keys cannot reach production sources" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 52.7 } ], "editorialScores": { "ergonomics": 72, "maintenance": 69, "payments": 25, "reliability": 28, "schema": 62, "security": 67, "transparency": 32 }, "provenanceScore": 70 }, "connect": { "install": "npm install medblocks", "http": "curl https://app.medblocks.com/patients -H \"Authorization: Bearer $MEDBLOCKS_API_KEY\" -H \"Content-Type: application/json\"", "claudeCode": "claude mcp add --transport http medblocks https://app.medblocks.com/mcp" }, "letme": { "capability": "https://letme.dev/health.records", "tool": "https://letme.dev/medblocks" }, "area": "domain-data", "unitPrices": [ { "item": "Enterprise plan, uncapped patients", "unit": "month", "usd": 5000, "note": "$60,000 a year per the billing page, shown here as a monthly equivalent" } ], "provenance": { "legalEntity": "Medblocks Inc.", "domain": "medblocks.com", "domainRegistered": "2005-11-04", "endpointOnVendorDomain": true, "terms": "https://medblocks.com/terms", "privacy": "https://medblocks.com/privacy-policy", "statusPage": "", "changelog": "https://medblocks.com/docs/reference/changelog", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The terms, last updated 5 October 2026, name Medblocks Inc., a Delaware corporation, at 100 Front Street, Suite 400 #122, Worcester, MA 01608, and cover the website and the CMS Blue Button application. No separate customer terms for the Platform API were found.", "The terms forbid using robots, scripts or scrapers to access the site. We read public pages and recorded that clause.", "The privacy policy, last updated 5 October 2026, covers the Medblocks applications including Medblocks Platform and the MCP server, and says no data is used to train AI models.", "medblocks.com/.well-known/security.txt returns 404. status.medblocks.com did not answer and no status page was linked from the docs.", "RDAP for medblocks.com gives a registration date of 2005-11-04." ], "score": 70 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/medblocks.json", "live": { "slug": "medblocks", "probe": { "target": "https://app.medblocks.com/mcp", "method": "get", "lastAt": "2026-10-14T09:59:54.038439885Z", "lastOk": true, "lastStatus": 401, "lastMs": 310, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 317, "p95ms24h": 405, "samples24h": 20, "samples30d": 20, "days": [ { "date": "2026-10-14", "probes": 20, "ok": 20 } ] }, "updatedAt": "2026-10-14T09:59:54.038439885Z" } }, "answer": "Zus Health scores 56.6 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on agent ergonomics, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "zus-health", "name": "Zus Health", "vendor": "Zus Health, Inc.", "vendorUrl": "https://www.zushealth.com", "kind": "http-api", "category": "health-data", "summary": "Zus Health assembles a patient's history from CommonWell, Carequality, Surescripts, Quest and ADT networks into the Zus Aggregated Profile, and exposes it through FHIR R4 REST, GraphQL and webhook APIs for care organisations it onboards.", "url": "https://www.anchorterminal.com/tools/zus-health", "markdownUrl": "https://www.anchorterminal.com/tools/zus-health.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zus-health.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zus-health.json", "license": "Proprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum", "transports": [ "http" ], "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 bearer tokens valid for one hour. Backend systems use machine-to-machine App Clients created in the Zus app or through the Auth Service API, limited to 200 token requests an hour per client. Apps can exchange an OIDC ID token from their own identity provider for a Zus token, and integration App Clients with the Builder Data Integration role can fetch tokens for users through the proxy-token endpoint. Accounts are provisioned by Zus, with an initial admin per customer.", "pricing": "paid", "pricingNotes": "No public prices. The Builder Terms set fees in an executed Order Form or pricing list, invoiced monthly. A developer sandbox is requested through a Google Form on the docs site, and its cost is not stated (checked 2026-10-14).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the documentation, llms.txt or the Builder Terms (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.zushealth.com", "llmsTxt": "https://docs.zushealth.com/llms.txt", "capabilities": [ "health.records", "health.fhir", "health.ehr", "health.consent" ], "tags": [ "hosted", "health-records", "fhir", "graphql", "oauth", "llms-txt", "webhooks", "status-page", "sla", "sales-led" ], "lastRelease": "2026-10-14", "graded": true, "anchor": { "graded": true, "score": 56.6, "grade": "C", "agentReady": false, "rank": 669, "ranked": true, "rankOf": 1076, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 64, "payments": 5, "reliability": 66, "schema": 77, "security": 49, "transparency": 59 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "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.", "bestFor": "US care organisations and digital health builders that want a shared, continuously refreshed patient profile in FHIR with EHR embedding.", "strengths": [ "One profile per patient from EHR, pharmacy, ADT and lab networks, shared across Zus customers treating the same patient", "Rate limits with numbers and a published 99.5 per cent SLA with credits", "Conditional writes by identifier and `Zus-If-Match` version checks for safe retries", "Dated changelog that announces changes ahead, such as the proxy-token role change on 14 October 2026" ], "weaknesses": [ "No public prices, and the sandbox is requested through a Google Form", "Four major incidents on the status page between 27 July and 13 August 2026", "No named security certification, security.txt or bug bounty", "The GraphQL API is beta and no official SDK exists" ], "agentNotes": [ "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-Match` with the resource's ETag on PUT and PATCH", "Set `_count` up to 500 on searches, since the default page is 10" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.6 } ], "editorialScores": { "ergonomics": 67, "maintenance": 64, "payments": 5, "reliability": 66, "schema": 77, "security": 49, "transparency": 46 }, "provenanceScore": 71 }, "connect": { "http": "GET https://api.sandbox.zusapi.com/fhir/Patient?_count=50\nAuthorization: Bearer \u003caccess-token\u003e" }, "letme": { "capability": "https://letme.dev/health.records", "tool": "https://letme.dev/zus-health" }, "area": "domain-data", "provenance": { "legalEntity": "Zus Health, Inc.", "domain": "zushealth.com", "domainRegistered": "2012-02-25", "endpointOnVendorDomain": false, "terms": "https://www.zushealth.com/builder-terms-of-service", "privacy": "https://www.zushealth.com/privacy-policy", "statusPage": "https://status.zusapi.com", "changelog": "https://docs.zushealth.com/changelog", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The APIs answer on zusapi.com, a separate domain from zushealth.com.", "The Builder Terms (last updated 11 March 2025) put term changes into effect 30 days after posting and BAA changes after 90 days. The Developer Sandbox Terms (22 January 2024) limit the sandbox to test data. The website lists 1 Lincoln Street, Suite 2900, Boston, MA 02111.", "The privacy policy (last updated 24 June 2026) covers the website only and names Google Analytics.", "The Builder Security Policy (11 March 2025) names no certification and makes a summary of an annual third-party audit available on request.", "www.zushealth.com/.well-known/security.txt returns 404.", "RDAP gives zushealth.com a registration date of 2012-02-25." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/zus-health.json", "live": { "slug": "zus-health", "vendorStatus": { "page": "https://status.zusapi.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:54:10.020449939Z" }, "updatedAt": "2026-10-14T08:54:10.020449939Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Medblocks Inc.", "b": "Zus Health, Inc.", "name": "Vendor" }, { "a": "https://app.medblocks.com/mcp", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "Proprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum", "name": "Licence" }, { "a": "10", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-14", "b": "2026-10-14", "name": "Last release" }, { "a": "2026-10-05", "b": "2025-03-11", "name": "Terms last updated" }, { "a": "2026-10-05", "b": "2026-06-24", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "36 npm/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Zus Health scores 56.6 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on agent ergonomics, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Medblocks or Zus Health?" }, { "answer": "Medblocks takes an API key or an OAuth sign-in. Zus Health uses an OAuth sign-in.", "question": "Do Medblocks and Zus Health need an API key?" }, { "answer": "Medblocks has a hosted endpoint at https://app.medblocks.com/mcp. No hosted endpoint is listed for Zus Health.", "question": "Can an agent call Medblocks and Zus Health without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 72 against 67", "Security \u0026 auth, 67 against 49", "Payments \u0026 pricing, 25 against 5", "Maintenance \u0026 community, 69 against 64" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "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.", "slug": "medblocks", "watchFor": "No status page, SLA or published rate limits for the Platform API" }, { "aheadOn": [ "Reliability, 66 against 28", "Schema \u0026 documentation, 77 against 62", "Transparency \u0026 trust, 59 against 51" ], "also": null, "goodFor": "US care organisations and digital health builders that want a shared, continuously refreshed patient profile in FHIR with EHR embedding.", "slug": "zus-health", "watchFor": "No public prices, and the sandbox is requested through a Google Form" } ], "job": { "capability": "health.records", "name": "Patient record retrieval" }, "others": [ { "json": "https://www.anchorterminal.com/compare/aidbox-vs-medblocks.json", "title": "Aidbox vs Medblocks", "url": "https://www.anchorterminal.com/compare/aidbox-vs-medblocks" }, { "json": "https://www.anchorterminal.com/compare/aidbox-vs-zus-health.json", "title": "Aidbox vs Zus Health", "url": "https://www.anchorterminal.com/compare/aidbox-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/medplum-vs-zus-health.json", "title": "Medplum vs Zus Health", "url": "https://www.anchorterminal.com/compare/medplum-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/1uphealth-vs-medblocks.json", "title": "1upHealth vs Medblocks", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-medblocks" }, { "json": "https://www.anchorterminal.com/compare/1uphealth-vs-zus-health.json", "title": "1upHealth vs Zus Health", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-medblocks.json", "title": "Health Gorilla vs Medblocks", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-medblocks" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-zus-health.json", "title": "Health Gorilla vs Zus Health", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-medplum.json", "title": "Medblocks vs Medplum", "url": "https://www.anchorterminal.com/compare/medblocks-vs-medplum" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-metriport.json", "title": "Medblocks vs Metriport Medical API", "url": "https://www.anchorterminal.com/compare/medblocks-vs-metriport" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-particle-health.json", "title": "Medblocks vs Particle Health", "url": "https://www.anchorterminal.com/compare/medblocks-vs-particle-health" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-redox.json", "title": "Medblocks vs Redox", "url": "https://www.anchorterminal.com/compare/medblocks-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/metriport-vs-zus-health.json", "title": "Metriport Medical API vs Zus Health", "url": "https://www.anchorterminal.com/compare/metriport-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/particle-health-vs-zus-health.json", "title": "Particle Health vs Zus Health", "url": "https://www.anchorterminal.com/compare/particle-health-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-rook.json", "title": "Medblocks vs ROOK", "url": "https://www.anchorterminal.com/compare/medblocks-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-terra.json", "title": "Medblocks vs Terra API", "url": "https://www.anchorterminal.com/compare/medblocks-vs-terra" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-validic.json", "title": "Medblocks vs Validic Inform", "url": "https://www.anchorterminal.com/compare/medblocks-vs-validic" }, { "json": "https://www.anchorterminal.com/compare/rook-vs-zus-health.json", "title": "ROOK vs Zus Health", "url": "https://www.anchorterminal.com/compare/rook-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/terra-vs-zus-health.json", "title": "Terra API vs Zus Health", "url": "https://www.anchorterminal.com/compare/terra-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/validic-vs-zus-health.json", "title": "Validic Inform vs Zus Health", "url": "https://www.anchorterminal.com/compare/validic-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/redox-vs-zus-health.json", "title": "Redox vs Zus Health", "url": "https://www.anchorterminal.com/compare/redox-vs-zus-health" } ], "scores": [ { "by": 38, "edge": "zus-health", "key": "reliability", "medblocks": 28, "name": "Reliability", "weight": 16, "zus-health": 66 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 15, "edge": "zus-health", "key": "schema", "medblocks": 62, "name": "Schema \u0026 documentation", "weight": 13, "zus-health": 77 }, { "by": 5, "edge": "medblocks", "key": "ergonomics", "medblocks": 72, "name": "Agent ergonomics", "weight": 13, "zus-health": 67 }, { "by": 18, "edge": "medblocks", "key": "security", "medblocks": 67, "name": "Security \u0026 auth", "weight": 14, "zus-health": 49 }, { "by": 20, "edge": "medblocks", "key": "payments", "medblocks": 25, "name": "Payments \u0026 pricing", "weight": 10, "zus-health": 5 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 5, "edge": "medblocks", "key": "maintenance", "medblocks": 69, "name": "Maintenance \u0026 community", "weight": 7, "zus-health": 64 }, { "by": 8, "edge": "zus-health", "key": "transparency", "medblocks": 51, "name": "Transparency \u0026 trust", "weight": 7, "zus-health": 59 } ], "summary": "Zus Health scores 56.6 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on agent ergonomics, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community. Both do patient record retrieval.", "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.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/medblocks-vs-zus-health", "json": "https://www.anchorterminal.com/compare/medblocks-vs-zus-health.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/medblocks-vs-zus-health.md", "slim": "https://www.anchorterminal.com/compare/medblocks-vs-zus-health.min.md" }, "markdown": "Zus Health scores 56.6 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on agent ergonomics, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community. Both do patient record retrieval.\n\n- Medblocks: grade D, 52.7/100, rank #773 of 1076. Markdown https://www.anchorterminal.com/tools/medblocks.md · JSON https://www.anchorterminal.com/api/v1/tools/medblocks.json\n- Zus Health: grade C, 56.6/100, rank #669 of 1076. Markdown https://www.anchorterminal.com/tools/zus-health.md · JSON https://www.anchorterminal.com/api/v1/tools/zus-health.json\n- Best health record and wellness data APIs for AI agents: https://www.anchorterminal.com/best/health-data/index.md\n- All 63 health comparisons: https://www.anchorterminal.com/compare/health-data/index.md\n\n## Which one, for what\n\n### Medblocks (D)\n\nGood 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.\n\nAhead on:\n- Agent ergonomics, 72 against 67\n- Security \u0026 auth, 67 against 49\n- Payments \u0026 pricing, 25 against 5\n- Maintenance \u0026 community, 69 against 64\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No status page, SLA or published rate limits for the Platform API\n\n### Zus Health (C)\n\nGood for: US care organisations and digital health builders that want a shared, continuously refreshed patient profile in FHIR with EHR embedding.\n\nAhead on:\n- Reliability, 66 against 28\n- Schema \u0026 documentation, 77 against 62\n- Transparency \u0026 trust, 59 against 51\n\nWatch for: No public prices, and the sandbox is requested through a Google Form\n\n\n## Score by category\n\n| Category | Weight | Medblocks | Zus Health | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 28 | 66 | Zus Health +38 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 62 | 77 | Zus Health +15 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 67 | Medblocks +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 67 | 49 | Medblocks +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 5 | Medblocks +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 69 | 64 | Medblocks +5 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 51 | 59 | Zus Health +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **52.7 · D** | **56.6 · C** | |\n\n## Facts side by side\n\n| Fact | Medblocks | Zus Health |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Medblocks Inc. | Zus Health, Inc. |\n| Hosted endpoint | `https://app.medblocks.com/mcp` | no (local only) |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | 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 | Proprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum |\n| Tools exposed | 10 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-14 | 2026-10-14 |\n| Terms last updated | 2026-10-05 | 2025-03-11 |\n| Privacy policy last updated | 2026-10-05 | 2026-06-24 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 36 npm/wk | none |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Medblocks\n\n1. 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\n2. Ask the person before calling `disconnect_health_system` or `delete_person`. Both are permanent\n3. Wait for the connection webhook or check connection status before reading records. Pulls run in the background after the patient approves\n4. Branch on `error.code`, not the message, and wait the `Retry-After` seconds on a 429\n5. Use a Sandbox workspace and the Synthetic Hospital (password `demopass`) for tests. Sandbox keys cannot reach production sources\n\n### Zus Health\n\n1. Cache the access token for its hour. More than 200 token requests an hour per App Client returns 429\n2. Request Patient History at most once per patient per 24 hours, and poll the job status endpoint\n3. Use conditional create by identifier so a retried write doesn't duplicate a resource\n4. Send `Zus-If-Match` with the resource's ETag on PUT and PATCH\n5. Set `_count` up to 500 on searches, since the default page is 10\n\n## Questions\n\n### Which is better for AI agents, Medblocks or Zus Health?\n\nZus Health scores 56.6 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on agent ergonomics, security \u0026 auth, payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Medblocks and Zus Health need an API key?\n\nMedblocks takes an API key or an OAuth sign-in. Zus Health uses an OAuth sign-in.\n\n### Can an agent call Medblocks and Zus Health without installing anything?\n\nMedblocks has a hosted endpoint at https://app.medblocks.com/mcp. No hosted endpoint is listed for Zus Health.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/medblocks-vs-zus-health.json, and with the fewest tokens: https://www.anchorterminal.com/compare/medblocks-vs-zus-health.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"medblocks\", \"b\": \"zus-health\"}`. From a terminal: `anchor compare medblocks zus-health`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/medblocks.json and https://www.anchorterminal.com/api/v1/tools/zus-health.json\n\n## Other comparisons with Medblocks or Zus Health\n\n- [Aidbox vs Medblocks](https://www.anchorterminal.com/compare/aidbox-vs-medblocks.md)\n- [Aidbox vs Zus Health](https://www.anchorterminal.com/compare/aidbox-vs-zus-health.md)\n- [Medplum vs Zus Health](https://www.anchorterminal.com/compare/medplum-vs-zus-health.md)\n- [1upHealth vs Medblocks](https://www.anchorterminal.com/compare/1uphealth-vs-medblocks.md)\n- [1upHealth vs Zus Health](https://www.anchorterminal.com/compare/1uphealth-vs-zus-health.md)\n- [Health Gorilla vs Medblocks](https://www.anchorterminal.com/compare/health-gorilla-vs-medblocks.md)\n- [Health Gorilla vs Zus Health](https://www.anchorterminal.com/compare/health-gorilla-vs-zus-health.md)\n- [Medblocks vs Medplum](https://www.anchorterminal.com/compare/medblocks-vs-medplum.md)\n- [Medblocks vs Metriport Medical API](https://www.anchorterminal.com/compare/medblocks-vs-metriport.md)\n- [Medblocks vs Particle Health](https://www.anchorterminal.com/compare/medblocks-vs-particle-health.md)\n- [Medblocks vs Redox](https://www.anchorterminal.com/compare/medblocks-vs-redox.md)\n- [Metriport Medical API vs Zus Health](https://www.anchorterminal.com/compare/metriport-vs-zus-health.md)\n- [Particle Health vs Zus Health](https://www.anchorterminal.com/compare/particle-health-vs-zus-health.md)\n- [Medblocks vs ROOK](https://www.anchorterminal.com/compare/medblocks-vs-rook.md)\n- [Medblocks vs Terra API](https://www.anchorterminal.com/compare/medblocks-vs-terra.md)\n- [Medblocks vs Validic Inform](https://www.anchorterminal.com/compare/medblocks-vs-validic.md)\n- [ROOK vs Zus Health](https://www.anchorterminal.com/compare/rook-vs-zus-health.md)\n- [Terra API vs Zus Health](https://www.anchorterminal.com/compare/terra-vs-zus-health.md)\n- [Validic Inform vs Zus Health](https://www.anchorterminal.com/compare/validic-vs-zus-health.md)\n- [Redox vs Zus Health](https://www.anchorterminal.com/compare/redox-vs-zus-health.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-14", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Medblocks vs Zus Health", "url": "" } ], "description": "Zus Health scores 56.6 (C) to Medblocks's 52.7 (D) for patient record retrieval. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Medblocks D 52.7", "Zus Health C 56.6", "scores" ], "h1": "Medblocks vs Zus Health", "image": "https://www.anchorterminal.com/assets/og/compare-medblocks-vs-zus-health.png", "path": "/compare/medblocks-vs-zus-health", "published": "2026-10-01", "section": "tools", "title": "Medblocks vs Zus Health for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/medblocks-vs-zus-health" }, "tokens": { "markdown": 2400, "slim": 780 }, "version": 1 }