{ "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 Redox's 58.3 (C), and leads in 4 of 7 scored categories. Redox leads on reliability, security \u0026 auth and payments \u0026 pricing.", "b": { "slug": "redox", "name": "Redox", "vendor": "Redox, Inc.", "vendorUrl": "https://redoxengine.com", "kind": "http-api", "category": "health-data", "summary": "Redox connects software vendors to hospital EHRs and clinical networks, translating HL7v2, C-CDA, X12 and DICOM into FHIR or Redox data models, with a FHIR API, a Platform API and a hosted MCP server for managing integrations.", "url": "https://www.anchorterminal.com/tools/redox", "markdownUrl": "https://www.anchorterminal.com/tools/redox.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/redox.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/redox.json", "license": "Proprietary service under Redox's Cloud Services Agreement, EULA and SLA (version 2016.1)", "transports": [ "http" ], "remoteUrl": "https://api.redoxengine.com/mcp", "packages": [], "auth": "oauth", "authNotes": "Data exchange uses OAuth API keys. The client signs a JWT assertion with a private key whose public half Redox holds (generated in the dashboard, pasted as a JWKS entry, or served from a JWKS URL), then exchanges it for a bearer token. Keys can be rotated, legacy API keys can be migrated, and user-level API keys exist for the Platform API. Each user connects to the MCP server through OAuth in their AI client after an organisation owner opts the organisation in.", "pricing": "paid", "pricingNotes": "Annual plans. Sandbox starts at $15,000 a year (a development environment with a FHIR sandbox and simulated patients, for organisations under 500 employees), Core starts at $35,000 a year, and Advanced is priced by sales. Consumption is billed on anticipated transaction volume, with no unit rates published. Anyone can create a dashboard account without a card, but what it can call before a plan is not stated (checked 2026-10-14).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the MCP server page or the pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": 107, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.redoxengine.com", "capabilities": [ "health.ehr", "health.fhir", "health.records" ], "tags": [ "hosted", "ehr-integration", "fhir", "hl7v2", "mcp", "oauth", "status-page", "sla", "bug-bounty", "hitrust", "soc2", "sales-led" ], "graded": true, "anchor": { "graded": true, "score": 58.3, "grade": "C", "agentReady": false, "rank": 618, "ranked": true, "rankOf": 1076, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 31, "payments": 15, "reliability": 85, "schema": 56, "security": 78, "transparency": 59 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Redox connects to EHRs and clinical networks behind a FHIR API, with signed-JWT OAuth keys, a 99.95 per cent SLA, a HackerOne bug bounty and a hosted MCP server for managing integrations. The MCP server exposes 107 tools at once with write and delete tools unconfirmed, OpenAPI files sit behind login, and the sandbox plan costs $15,000 a year.", "bestFor": "Health software vendors integrating with many hospital EHRs and networks, and integration teams who want an agent to manage Redox configuration.", "strengths": [ "OAuth API keys signed with the client's own private key, with JWKS URL support and rotation guidance", "Hosted MCP server with per-user OAuth and an organisation-level opt-in", "Published SLA of 99.95 per cent and a 40-minute incident on 8 September 2026 with a postmortem", "HITRUST r2, SOC 2 Type 2 and a public HackerOne bug bounty" ], "weaknesses": [ "The MCP server loads 107 tools in one set, including write and delete tools with no confirmation step", "OpenAPI files and Postman collections are behind the dashboard login, and llms.txt is missing", "No public changelog or dated releases", "The cheapest plan with a sandbox starts at $15,000 a year" ], "agentNotes": [ "Name the environment in every MCP prompt and try configuration changes in staging first, as Redox advises", "Stay under 7,500 requests per IP per five minutes, and back off exponentially on 5XX", "Sign the token request with the private key whose public key is registered on the OAuth API key", "Ask an organisation owner to enable the MCP server before connecting a client", "Treat log payloads returned through MCP as PHI and as untrusted text" ], "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": 58.3 } ], "editorialScores": { "ergonomics": 54, "maintenance": 31, "payments": 15, "reliability": 85, "schema": 56, "security": 78, "transparency": 37 }, "provenanceScore": 80 }, "connect": { "http": "https://api.redoxengine.com/mcp" }, "letme": { "capability": "https://letme.dev/health.ehr", "tool": "https://letme.dev/redox" }, "area": "domain-data", "provenance": { "legalEntity": "Redox, Inc.", "domain": "redoxengine.com", "domainRegistered": "2014-07-23", "endpointOnVendorDomain": true, "terms": "https://redoxengine.com/legal/terms-of-use/", "privacy": "https://redoxengine.com/legal/privacy-policy/", "statusPage": "https://status.redoxengine.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The website terms of use (version 2014.1, last updated 17 October 2015) name Redox, Inc., 25 West Main Street, Suite 500, Madison, WI 53703, and forbid crawling that impairs a system. Service use falls under a Cloud Services Agreement and the EULA, which we did not read.", "The SLA page is version 2016.1, dated 13 February 2016.", "The privacy policy (last updated 18 January 2023) covers the website and says it doesn't govern data Redox processes for customers.", "redoxengine.com/.well-known/security.txt returns 404. The platform security page points to a HackerOne bug bounty.", "docs.redoxengine.com/llms.txt returns the HTML site rather than an llms.txt file. No public changelog was found.", "RDAP gives redoxengine.com a registration date of 2014-07-23." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/redox.json", "live": { "slug": "redox", "probe": { "target": "https://api.redoxengine.com/mcp", "method": "get", "lastAt": "2026-10-14T09:42:04.293207713Z", "lastOk": true, "lastStatus": 401, "lastMs": 251, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 265, "p95ms24h": 428, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.redoxengine.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:39.154707608Z" }, "updatedAt": "2026-10-14T09:42:04.293207713Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Health Gorilla, Inc.", "b": "Redox, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.redoxengine.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth", "name": "Auth" }, { "a": "Paid", "b": "Paid", "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 Redox's Cloud Services Agreement, EULA and SLA (version 2016.1)", "name": "Licence" }, { "a": "none", "b": "107", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-14", "b": "none", "name": "Last release" }, { "a": "no date given", "b": "2015-10-17", "name": "Terms last updated" }, { "a": "2024-08-30", "b": "2023-01-18", "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": "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" } ], "faq": [ { "answer": "Health Gorilla scores 59.3 (C) on agent readiness against Redox's 58.3 (C), and leads in 4 of 7 scored categories. Redox leads on reliability, security \u0026 auth and payments \u0026 pricing.", "question": "Which is better for AI agents, Health Gorilla or Redox?" }, { "answer": "Both use an OAuth sign-in.", "question": "Do Health Gorilla and Redox need an API key?" }, { "answer": "No hosted endpoint is listed for Health Gorilla. Redox has a hosted endpoint at https://api.redoxengine.com/mcp.", "question": "Can an agent call Health Gorilla and Redox without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 80 against 56", "Agent ergonomics, 72 against 54", "Maintenance \u0026 community, 63 against 31" ], "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": [ "Reliability, 85 against 58", "Security \u0026 auth, 78 against 66", "Payments \u0026 pricing, 15 against 5" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "Health software vendors integrating with many hospital EHRs and networks, and integration teams who want an agent to manage Redox configuration.", "slug": "redox", "watchFor": "The MCP server loads 107 tools in one set, including write and delete tools with no confirmation step" } ], "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-redox.json", "title": "Aidbox vs Redox", "url": "https://www.anchorterminal.com/compare/aidbox-vs-redox" }, { "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/medplum-vs-redox.json", "title": "Medplum vs Redox", "url": "https://www.anchorterminal.com/compare/medplum-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/redox-vs-rook.json", "title": "Redox vs ROOK", "url": "https://www.anchorterminal.com/compare/redox-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/redox-vs-terra.json", "title": "Redox vs Terra API", "url": "https://www.anchorterminal.com/compare/redox-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-redox.json", "title": "1upHealth vs Redox", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-redox" }, { "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-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-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-redox.json", "title": "Medblocks vs Redox", "url": "https://www.anchorterminal.com/compare/medblocks-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/metriport-vs-redox.json", "title": "Metriport Medical API vs Redox", "url": "https://www.anchorterminal.com/compare/metriport-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/particle-health-vs-redox.json", "title": "Particle Health vs Redox", "url": "https://www.anchorterminal.com/compare/particle-health-vs-redox" }, { "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/redox-vs-zus-health.json", "title": "Redox vs Zus Health", "url": "https://www.anchorterminal.com/compare/redox-vs-zus-health" } ], "scores": [ { "by": 27, "edge": "redox", "health-gorilla": 58, "key": "reliability", "name": "Reliability", "redox": 85, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 24, "edge": "health-gorilla", "health-gorilla": 80, "key": "schema", "name": "Schema \u0026 documentation", "redox": 56, "weight": 13 }, { "by": 18, "edge": "health-gorilla", "health-gorilla": 72, "key": "ergonomics", "name": "Agent ergonomics", "redox": 54, "weight": 13 }, { "by": 12, "edge": "redox", "health-gorilla": 66, "key": "security", "name": "Security \u0026 auth", "redox": 78, "weight": 14 }, { "by": 10, "edge": "redox", "health-gorilla": 5, "key": "payments", "name": "Payments \u0026 pricing", "redox": 15, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 32, "edge": "health-gorilla", "health-gorilla": 63, "key": "maintenance", "name": "Maintenance \u0026 community", "redox": 31, "weight": 7 }, { "by": 2, "edge": "health-gorilla", "health-gorilla": 61, "key": "transparency", "name": "Transparency \u0026 trust", "redox": 59, "weight": 7 } ], "summary": "Health Gorilla scores 59.3 (C) on agent readiness against Redox's 58.3 (C), and leads in 4 of 7 scored categories. Redox leads on reliability, security \u0026 auth and payments \u0026 pricing. 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.", "redox": "Redox connects to EHRs and clinical networks behind a FHIR API, with signed-JWT OAuth keys, a 99.95 per cent SLA, a HackerOne bug bounty and a hosted MCP server for managing integrations. The MCP server exposes 107 tools at once with write and delete tools unconfirmed, OpenAPI files sit behind login, and the sandbox plan costs $15,000 a year." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/health-gorilla-vs-redox", "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-redox.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/health-gorilla-vs-redox.md", "slim": "https://www.anchorterminal.com/compare/health-gorilla-vs-redox.min.md" }, "markdown": "Health Gorilla scores 59.3 (C) on agent readiness against Redox's 58.3 (C), and leads in 4 of 7 scored categories. Redox leads on reliability, security \u0026 auth and payments \u0026 pricing. 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- Redox: grade C, 58.3/100, rank #618 of 1076. Markdown https://www.anchorterminal.com/tools/redox.md · JSON https://www.anchorterminal.com/api/v1/tools/redox.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- Schema \u0026 documentation, 80 against 56\n- Agent ergonomics, 72 against 54\n- Maintenance \u0026 community, 63 against 31\n\nWatch for: No public prices. Fees are set case by case and the sandbox is requested by form\n\n### Redox (C)\n\nGood for: Health software vendors integrating with many hospital EHRs and networks, and integration teams who want an agent to manage Redox configuration.\n\nAhead on:\n- Reliability, 85 against 58\n- Security \u0026 auth, 78 against 66\n- Payments \u0026 pricing, 15 against 5\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: The MCP server loads 107 tools in one set, including write and delete tools with no confirmation step\n\n\n## Score by category\n\n| Category | Weight | Health Gorilla | Redox | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 58 | 85 | Redox +27 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 56 | Health Gorilla +24 |\n| Agent ergonomics | 13% (16.2 this run) | 72 | 54 | Health Gorilla +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 66 | 78 | Redox +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 5 | 15 | Redox +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 63 | 31 | Health Gorilla +32 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 59 | Health Gorilla +2 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **59.3 · C** | **58.3 · C** | |\n\n## Facts side by side\n\n| Fact | Health Gorilla | Redox |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Health Gorilla, Inc. | Redox, Inc. |\n| Hosted endpoint | no (local only) | `https://api.redoxengine.com/mcp` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth | OAuth |\n| Pricing | Paid | Paid |\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 Redox's Cloud Services Agreement, EULA and SLA (version 2016.1) |\n| Tools exposed | none | 107 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-14 | none |\n| Terms last updated | no date given | 2015-10-17 |\n| Privacy policy last updated | 2024-08-30 | 2023-01-18 |\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 | 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\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**Redox.** Redox connects to EHRs and clinical networks behind a FHIR API, with signed-JWT OAuth keys, a 99.95 per cent SLA, a HackerOne bug bounty and a hosted MCP server for managing integrations. The MCP server exposes 107 tools at once with write and delete tools unconfirmed, OpenAPI files sit behind login, and the sandbox plan costs $15,000 a year.\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### Redox\n\n1. Name the environment in every MCP prompt and try configuration changes in staging first, as Redox advises\n2. Stay under 7,500 requests per IP per five minutes, and back off exponentially on 5XX\n3. Sign the token request with the private key whose public key is registered on the OAuth API key\n4. Ask an organisation owner to enable the MCP server before connecting a client\n5. Treat log payloads returned through MCP as PHI and as untrusted text\n\n## Questions\n\n### Which is better for AI agents, Health Gorilla or Redox?\n\nHealth Gorilla scores 59.3 (C) on agent readiness against Redox's 58.3 (C), and leads in 4 of 7 scored categories. Redox leads on reliability, security \u0026 auth and payments \u0026 pricing.\n\n### Do Health Gorilla and Redox need an API key?\n\nBoth use an OAuth sign-in.\n\n### Can an agent call Health Gorilla and Redox without installing anything?\n\nNo hosted endpoint is listed for Health Gorilla. Redox has a hosted endpoint at https://api.redoxengine.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/health-gorilla-vs-redox.json, and with the fewest tokens: https://www.anchorterminal.com/compare/health-gorilla-vs-redox.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"health-gorilla\", \"b\": \"redox\"}`. From a terminal: `anchor compare health-gorilla redox`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/health-gorilla.json and https://www.anchorterminal.com/api/v1/tools/redox.json\n\n## Other comparisons with Health Gorilla or Redox\n\n- [Aidbox vs Health Gorilla](https://www.anchorterminal.com/compare/aidbox-vs-health-gorilla.md)\n- [Aidbox vs Redox](https://www.anchorterminal.com/compare/aidbox-vs-redox.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- [Medplum vs Redox](https://www.anchorterminal.com/compare/medplum-vs-redox.md)\n- [Redox vs ROOK](https://www.anchorterminal.com/compare/redox-vs-rook.md)\n- [Redox vs Terra API](https://www.anchorterminal.com/compare/redox-vs-terra.md)\n- [1upHealth vs Health Gorilla](https://www.anchorterminal.com/compare/1uphealth-vs-health-gorilla.md)\n- [1upHealth vs Redox](https://www.anchorterminal.com/compare/1uphealth-vs-redox.md)\n- [Health Gorilla vs Medblocks](https://www.anchorterminal.com/compare/health-gorilla-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 Zus Health](https://www.anchorterminal.com/compare/health-gorilla-vs-zus-health.md)\n- [Medblocks vs Redox](https://www.anchorterminal.com/compare/medblocks-vs-redox.md)\n- [Metriport Medical API vs Redox](https://www.anchorterminal.com/compare/metriport-vs-redox.md)\n- [Particle Health vs Redox](https://www.anchorterminal.com/compare/particle-health-vs-redox.md)\n- [Health Gorilla vs Validic Inform](https://www.anchorterminal.com/compare/health-gorilla-vs-validic.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": "Health Gorilla vs Redox", "url": "" } ], "description": "Health Gorilla scores 59.3 (C) to Redox's 58.3 (C) for patient record retrieval. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Health Gorilla C 59.3", "Redox C 58.3", "scores" ], "h1": "Health Gorilla vs Redox", "image": "https://www.anchorterminal.com/assets/og/compare-health-gorilla-vs-redox.png", "path": "/compare/health-gorilla-vs-redox", "published": "2026-10-01", "section": "tools", "title": "Health Gorilla vs Redox for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-redox" }, "tokens": { "markdown": 2250, "slim": 680 }, "version": 1 }