{ "data": { "a": { "slug": "health-gorilla", "name": "Health Gorilla", "vendor": "Health Gorilla, Inc.", "vendorUrl": "https://www.healthgorilla.com", "kind": "http-api", "category": "health-data", "summary": "Health Gorilla is a designated TEFCA QHIN whose FHIR R4 API retrieves patient records from national networks (Patient360), places lab orders and returns results, and sends ADT and clinical alerts, for organisations it onboards.", "url": "https://www.anchorterminal.com/tools/health-gorilla", "markdownUrl": "https://www.anchorterminal.com/tools/health-gorilla.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/health-gorilla.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/health-gorilla.json", "license": "Proprietary service under Health Gorilla's API Terms of Use (updated 22 January 2026), with a signed licence agreement required before production", "transports": [ "http" ], "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 credentials (client ID and secret) are issued by Health Gorilla during implementation, separately for sandbox and production. Server-to-server calls use the JWT bearer grant with an assertion signed HS256 with the client secret. User-facing apps use the authorisation code grant, and an implicit grant can be enabled. Scopes such as `system/Patient.read`, `system/Observation.write` and `patient360` are assigned at registration and cannot be self-assigned.", "pricing": "paid", "pricingNotes": "No public prices. The API Terms of Use say fees 'are determined on a case-by-case basis by our business development team', and the sandbox is requested through the contact page (checked 2026-10-14).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer portal, llms.txt or the API terms (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://developer.healthgorilla.com", "llmsTxt": "https://developer.healthgorilla.com/llms.txt", "capabilities": [ "health.records", "health.fhir", "health.consent" ], "tags": [ "hosted", "health-records", "fhir", "qhin", "lab-orders", "oauth", "llms-txt", "webhooks", "status-page", "sales-led", "hitrust", "soc2" ], "lastRelease": "2026-10-14", "graded": true, "anchor": { "graded": true, "score": 59.3, "grade": "C", "agentReady": false, "rank": 583, "ranked": true, "rankOf": 1076, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 63, "payments": 5, "reliability": 58, "schema": 80, "security": 66, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "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.", "bestFor": "US providers, labs and digital health companies that need network record retrieval and lab ordering through one FHIR API with a QHIN behind it.", "strengths": [ "Designated TEFCA QHIN with Patient360 retrieval across national networks, plus lab orders and ADT alerts", "`HG-Idempotency-Key` on POST, replaying the first response and returning 409 on conflicts", "llms.txt, Markdown pages and an OpenAPI 3.1 fragment on each reference page", "Release notes dated separately for sandbox and production, the latest on 14 October 2026" ], "weaknesses": [ "No public prices. Fees are set case by case and the sandbox is requested by form", "Rate limits are enforced with no published numbers", "JWT bearer assertions are signed HS256 with the shared client secret", "The API terms allow termination or disabling of access at any time, with or without notice" ], "agentNotes": [ "Send a fresh UUID in `HG-Idempotency-Key` on every POST and reuse it only when retrying the same payload", "Poll async operations no sooner than the `Retry-After` value and treat 454 as an expired result", "Follow `link.relation=next` in Bundles rather than building offsets yourself", "Expect mocked Patient360 data in sandbox unless network connectivity is enabled for the tenant", "Log `X-HG-Request-Id` from each response for support cases" ], "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": 59.3 } ], "editorialScores": { "ergonomics": 72, "maintenance": 63, "payments": 5, "reliability": 58, "schema": 80, "security": 66, "transparency": 38 }, "provenanceScore": 83 }, "connect": { "http": "GET https://sandbox.healthgorilla.com/fhir/R4/Patient?_count=50\nAuthorization: Bearer \u003caccess-token\u003e\nAccept: application/fhir+json" }, "letme": { "capability": "https://letme.dev/health.records", "tool": "https://letme.dev/health-gorilla" }, "area": "domain-data", "provenance": { "legalEntity": "Health Gorilla, Inc.", "domain": "healthgorilla.com", "domainRegistered": "2006-04-09", "endpointOnVendorDomain": true, "terms": "https://developer.healthgorilla.com/docs/terms-of-use", "privacy": "https://www.healthgorilla.com/home/privacy-policy", "statusPage": "https://status.healthgorilla.com", "changelog": "https://developer.healthgorilla.com/changelog", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The API Terms of Use (updated 22 January 2026) are between the developer and Health Gorilla, Inc., require a signed licence before production, and may be amended with or without notice.", "The privacy policy (last updated 30 August 2024) names Health Gorilla, Inc., covers the website and its platforms, gives no retention periods or sub-processors, and lists a Coral Gables, FL mailing address.", "www.healthgorilla.com/.well-known/security.txt returns the site's 404 page. A page at /home/security-txt shows a security.txt with Contact security@healthgorilla.com and Expires 2025-12-31.", "The website's Terms of Use page links an Enterprise SaaS Agreement (July 2024 version) that we did not read.", "RDAP gives healthgorilla.com a registration date of 2006-04-09." ], "score": 83 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/health-gorilla.json", "live": { "slug": "health-gorilla", "vendorStatus": { "page": "https://status.healthgorilla.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:15.462244766Z" }, "updatedAt": "2026-10-14T09:39:15.462244766Z" } }, "answer": "Health Gorilla scores 59.3 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on payments \u0026 pricing and maintenance \u0026 community.", "b": { "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:41:57.376112052Z", "lastOk": true, "lastStatus": 401, "lastMs": 317, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 317, "p95ms24h": 463, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "updatedAt": "2026-10-14T09:41:57.376112052Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Health Gorilla, Inc.", "b": "Medblocks Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://app.medblocks.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Health Gorilla's API Terms of Use (updated 22 January 2026), with a signed licence agreement required before production", "b": "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", "name": "Licence" }, { "a": "none", "b": "10", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-14", "b": "2026-09-14", "name": "Last release" }, { "a": "no date given", "b": "2026-10-05", "name": "Terms last updated" }, { "a": "2024-08-30", "b": "2026-10-05", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "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": "none", "b": "36 npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Health Gorilla scores 59.3 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Health Gorilla or Medblocks?" }, { "answer": "Health Gorilla uses an OAuth sign-in. Medblocks takes an API key or an OAuth sign-in.", "question": "Do Health Gorilla and Medblocks need an API key?" }, { "answer": "No hosted endpoint is listed for Health Gorilla. Medblocks has a hosted endpoint at https://app.medblocks.com/mcp.", "question": "Can an agent call Health Gorilla and Medblocks without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 58 against 28", "Schema \u0026 documentation, 80 against 62", "Transparency \u0026 trust, 61 against 51" ], "also": null, "goodFor": "US providers, labs and digital health companies that need network record retrieval and lab ordering through one FHIR API with a QHIN behind it.", "slug": "health-gorilla", "watchFor": "No public prices. Fees are set case by case and the sandbox is requested by form" }, { "aheadOn": [ "Payments \u0026 pricing, 25 against 5", "Maintenance \u0026 community, 69 against 63" ], "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" } ], "job": { "capability": "health.records", "name": "Patient record retrieval" }, "others": [ { "json": "https://www.anchorterminal.com/compare/aidbox-vs-health-gorilla.json", "title": "Aidbox vs Health Gorilla", "url": "https://www.anchorterminal.com/compare/aidbox-vs-health-gorilla" }, { "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/health-gorilla-vs-rook.json", "title": "Health Gorilla vs ROOK", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-terra.json", "title": "Health Gorilla vs Terra API", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-terra" }, { "json": "https://www.anchorterminal.com/compare/1uphealth-vs-health-gorilla.json", "title": "1upHealth vs Health Gorilla", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-health-gorilla" }, { "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/health-gorilla-vs-medplum.json", "title": "Health Gorilla vs Medplum", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-medplum" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-metriport.json", "title": "Health Gorilla vs Metriport Medical API", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-metriport" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-particle-health.json", "title": "Health Gorilla vs Particle Health", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-particle-health" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-redox.json", "title": "Health Gorilla vs Redox", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-redox" }, { "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/medblocks-vs-zus-health.json", "title": "Medblocks vs Zus Health", "url": "https://www.anchorterminal.com/compare/medblocks-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-validic.json", "title": "Health Gorilla vs Validic Inform", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-validic" }, { "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" } ], "scores": [ { "by": 30, "edge": "health-gorilla", "health-gorilla": 58, "key": "reliability", "medblocks": 28, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 18, "edge": "health-gorilla", "health-gorilla": 80, "key": "schema", "medblocks": 62, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 0, "edge": "", "health-gorilla": 72, "key": "ergonomics", "medblocks": 72, "name": "Agent ergonomics", "weight": 13 }, { "by": 1, "edge": "medblocks", "health-gorilla": 66, "key": "security", "medblocks": 67, "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "edge": "medblocks", "health-gorilla": 5, "key": "payments", "medblocks": 25, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 6, "edge": "medblocks", "health-gorilla": 63, "key": "maintenance", "medblocks": 69, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 10, "edge": "health-gorilla", "health-gorilla": 61, "key": "transparency", "medblocks": 51, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Health Gorilla scores 59.3 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on payments \u0026 pricing and maintenance \u0026 community. Both do patient record retrieval.", "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.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/health-gorilla-vs-medblocks", "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-medblocks.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/health-gorilla-vs-medblocks.md", "slim": "https://www.anchorterminal.com/compare/health-gorilla-vs-medblocks.min.md" }, "markdown": "Health Gorilla scores 59.3 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on payments \u0026 pricing and maintenance \u0026 community. Both do patient record retrieval.\n\n- Health Gorilla: grade C, 59.3/100, rank #583 of 1076. Markdown https://www.anchorterminal.com/tools/health-gorilla.md · JSON https://www.anchorterminal.com/api/v1/tools/health-gorilla.json\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- 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### Health Gorilla (C)\n\nGood 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.\n\nAhead on:\n- Reliability, 58 against 28\n- Schema \u0026 documentation, 80 against 62\n- Transparency \u0026 trust, 61 against 51\n\nWatch for: No public prices. Fees are set case by case and the sandbox is requested by form\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- Payments \u0026 pricing, 25 against 5\n- Maintenance \u0026 community, 69 against 63\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\n## Score by category\n\n| Category | Weight | Health Gorilla | Medblocks | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 58 | 28 | Health Gorilla +30 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 62 | Health Gorilla +18 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 72 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 66 | 67 | Medblocks +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 5 | 25 | Medblocks +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 63 | 69 | Medblocks +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 51 | Health Gorilla +10 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **59.3 · C** | **52.7 · D** | |\n\n## Facts side by side\n\n| Fact | Health Gorilla | Medblocks |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Health Gorilla, Inc. | Medblocks Inc. |\n| Hosted endpoint | no (local only) | `https://app.medblocks.com/mcp` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| 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 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 |\n| Tools exposed | none | 10 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-14 | 2026-09-14 |\n| Terms last updated | no date given | 2026-10-05 |\n| Privacy policy last updated | 2024-08-30 | 2026-10-05 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | none | 36 npm/wk |\n\n## Verdicts\n\n**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.\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## Before you call either\n\n### Health Gorilla\n\n1. Send a fresh UUID in `HG-Idempotency-Key` on every POST and reuse it only when retrying the same payload\n2. Poll async operations no sooner than the `Retry-After` value and treat 454 as an expired result\n3. Follow `link.relation=next` in Bundles rather than building offsets yourself\n4. Expect mocked Patient360 data in sandbox unless network connectivity is enabled for the tenant\n5. Log `X-HG-Request-Id` from each response for support cases\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## Questions\n\n### Which is better for AI agents, Health Gorilla or Medblocks?\n\nHealth Gorilla scores 59.3 (C) on agent readiness against Medblocks's 52.7 (D), and leads in 3 of 7 scored categories. Medblocks leads on payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Health Gorilla and Medblocks need an API key?\n\nHealth Gorilla uses an OAuth sign-in. Medblocks takes an API key or an OAuth sign-in.\n\n### Can an agent call Health Gorilla and Medblocks without installing anything?\n\nNo hosted endpoint is listed for Health Gorilla. Medblocks has a hosted endpoint at https://app.medblocks.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/health-gorilla-vs-medblocks.json, and with the fewest tokens: https://www.anchorterminal.com/compare/health-gorilla-vs-medblocks.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"health-gorilla\", \"b\": \"medblocks\"}`. From a terminal: `anchor compare health-gorilla medblocks`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/health-gorilla.json and https://www.anchorterminal.com/api/v1/tools/medblocks.json\n\n## Other comparisons with Health Gorilla or Medblocks\n\n- [Aidbox vs Health Gorilla](https://www.anchorterminal.com/compare/aidbox-vs-health-gorilla.md)\n- [Aidbox vs Medblocks](https://www.anchorterminal.com/compare/aidbox-vs-medblocks.md)\n- [Health Gorilla vs ROOK](https://www.anchorterminal.com/compare/health-gorilla-vs-rook.md)\n- [Health Gorilla vs Terra API](https://www.anchorterminal.com/compare/health-gorilla-vs-terra.md)\n- [1upHealth vs Health Gorilla](https://www.anchorterminal.com/compare/1uphealth-vs-health-gorilla.md)\n- [1upHealth vs Medblocks](https://www.anchorterminal.com/compare/1uphealth-vs-medblocks.md)\n- [Health Gorilla vs Medplum](https://www.anchorterminal.com/compare/health-gorilla-vs-medplum.md)\n- [Health Gorilla vs Metriport Medical API](https://www.anchorterminal.com/compare/health-gorilla-vs-metriport.md)\n- [Health Gorilla vs Particle Health](https://www.anchorterminal.com/compare/health-gorilla-vs-particle-health.md)\n- [Health Gorilla vs Redox](https://www.anchorterminal.com/compare/health-gorilla-vs-redox.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- [Medblocks vs Zus Health](https://www.anchorterminal.com/compare/medblocks-vs-zus-health.md)\n- [Health Gorilla vs Validic Inform](https://www.anchorterminal.com/compare/health-gorilla-vs-validic.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", "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": "Health Gorilla vs Medblocks", "url": "" } ], "description": "Health Gorilla scores 59.3 (C) to Medblocks's 52.7 (D) for patient record retrieval. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Health Gorilla C 59.3", "Medblocks D 52.7", "scores" ], "h1": "Health Gorilla vs Medblocks", "image": "https://www.anchorterminal.com/assets/og/compare-health-gorilla-vs-medblocks.png", "path": "/compare/health-gorilla-vs-medblocks", "published": "2026-10-01", "section": "tools", "title": "Health Gorilla vs Medblocks for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-medblocks" }, "tokens": { "markdown": 2400, "slim": 730 }, "version": 1 }