{ "data": { "a": { "slug": "metriport", "name": "Metriport Medical API", "vendor": "Metriport Inc.", "vendorUrl": "https://www.metriport.com", "kind": "http-api", "category": "health-data", "summary": "Metriport's Medical API retrieves a patient's records from US health information exchanges, pharmacies and labs, converts them to deduplicated FHIR, and returns them through a REST API with webhooks. Production use requires a covered entity with an NPI.", "url": "https://www.anchorterminal.com/tools/metriport", "markdownUrl": "https://www.anchorterminal.com/tools/metriport.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/metriport.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/metriport.json", "repo": "https://github.com/metriport/metriport", "license": "Proprietary hosted service under Metriport's terms of use. The source in metriport/metriport is AGPLv3, with an enterprise directory under its own licence, and the @metriport/api-sdk package on npm is MIT", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@metriport/api-sdk" } ], "auth": "api-key", "authNotes": "Every request sends a key in the `x-api-key` header to https://api.metriport.com, or https://api.sandbox.metriport.com in sandbox mode. Keys are generated in the developer dashboard after Metriport approves the account, up to two at once for rotation, each revocable at once and each with full access including destructive operations. No scopes or read-only key were found. Production access needs a covered entity with an NPI and a treatment purpose of use, agreed on an intro call.", "pricing": "paid", "pricingNotes": "No public prices. metriport.com has no pricing page, the terms say some services carry a fee paid by card, wire or Stripe, and production access starts with an intro call booked from the dashboard. A sandbox with example patients opens once Metriport approves the access request, 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, the repository README or the terms (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 793, "npmWeekly": 28168, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.metriport.com/medical-api/getting-started/quickstart", "llmsTxt": "https://docs.metriport.com/llms.txt", "capabilities": [ "health.records", "health.fhir", "health.consent", "health.ehr" ], "tags": [ "hosted", "health-records", "fhir", "open-source", "agpl", "typescript", "llms-txt", "webhooks", "status-page", "sales-led", "hitrust", "soc2" ], "lastRelease": "2026-09-28", "graded": true, "anchor": { "graded": true, "score": 50.1, "grade": "D", "agentReady": false, "rank": 833, "ranked": true, "rankOf": 1076, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 70, "maintenance": 74, "payments": 5, "reliability": 45, "schema": 65, "security": 41, "transparency": 56 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "One network query pulls a patient's records from HIEs, pharmacies and labs and returns deduplicated FHIR, with per-operation rate limits, RFC 7807 errors and AGPLv3 source. Each API key has full access with no scopes, there are no public prices, and the sandbox opens only after Metriport approves the account.", "bestFor": "US care providers and digital health companies that need a patient's network records as FHIR with webhooks.", "strengths": [ "One asynchronous network query covers HIEs, pharmacies and labs, with a webhook as each source is merged", "Consolidated FHIR output is deduplicated and coded, with PDF or HTML record summaries", "Rate limits published per operation, and `count` up to 500 per page", "AGPLv3 source on GitHub and an MIT TypeScript SDK released on 28 September 2026" ], "weaknesses": [ "Every API key has full access, including destructive operations, with no scopes", "No public prices, and the sandbox needs Metriport's approval first", "The Fern definition covers only part of the API and no public changelog was found", "The status page renders only with JavaScript, so its history could not be read" ], "agentNotes": [ "Check the `errors` array after Start Network Query. It returns 2XX even when some sources fail", "Wait for `network-query.*` webhooks or poll Get Network Query Status before reading consolidated data, which is cached from the last query", "Send the resource's `eTag` in `If-Match` on updates to avoid overwriting newer data", "Keep patient creates under 15 a minute and network queries under 20 a minute per source", "In sandbox, create patients whose first name matches a pre-defined persona to get example records" ], "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": 50.1 } ], "editorialScores": { "ergonomics": 70, "maintenance": 74, "payments": 5, "reliability": 45, "schema": 65, "security": 41, "transparency": 43 }, "provenanceScore": 69 }, "connect": { "install": "npm install --save @metriport/api-sdk", "http": "POST https://api.sandbox.metriport.com/medical/v1/patient?facilityId=\u003cfacility-id\u003e\nx-api-key: \u003capi-key\u003e\nContent-Type: application/json" }, "letme": { "capability": "https://letme.dev/health.records", "tool": "https://letme.dev/metriport" }, "area": "domain-data", "provenance": { "legalEntity": "Metriport Inc.", "domain": "metriport.com", "domainRegistered": "2021-02-09", "endpointOnVendorDomain": true, "terms": "https://www.metriport.com/terms", "privacy": "https://www.metriport.com/privacy-policy", "statusPage": "https://status.metriport.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The terms of use (last updated January 2024) give a registered office at 2261 Market Street #4818, San Francisco, CA 94114, forbid access 'through automated or non-human means' and the use of 'data mining, robots, or similar data gathering and extraction tools', and say the site is not built for HIPAA-regulated use. We read them as a fact and fetched only what robots.txt allows.", "The privacy policy (last updated 21 February 2023) covers website visitors and customer contacts, says data is stored in the US, and does not mention API data or PHI.", "www.metriport.com/.well-known/security.txt returns 404. SECURITY.md in the repository sends reports to GitHub's vulnerability reporting or support@metriport.com.", "No public changelog was found in the documentation or on the website.", "RDAP gives metriport.com a registration date of 2021-02-09." ], "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/metriport.json", "live": { "slug": "metriport", "vendorStatus": { "page": "https://status.metriport.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:53:23.949542071Z" }, "updatedAt": "2026-10-14T08:53:23.949542071Z" } }, "answer": "Redox scores 58.3 (C) on agent readiness against Metriport Medical API's 50.1 (D), and leads in 4 of 7 scored categories. Metriport Medical API leads on schema \u0026 documentation, agent ergonomics and maintenance \u0026 community.", "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": "Metriport 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": "API key", "b": "OAuth", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted service under Metriport's terms of use. The source in metriport/metriport is AGPLv3, with an enterprise directory under its own licence, and the @metriport/api-sdk package on npm is MIT", "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-09-28", "b": "none", "name": "Last release" }, { "a": "2024-01-01", "b": "2015-10-17", "name": "Terms last updated" }, { "a": "2023-02-21", "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": "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": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "793 stars, 28k npm/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Redox scores 58.3 (C) on agent readiness against Metriport Medical API's 50.1 (D), and leads in 4 of 7 scored categories. Metriport Medical API leads on schema \u0026 documentation, agent ergonomics and maintenance \u0026 community.", "question": "Which is better for AI agents, Metriport Medical API or Redox?" }, { "answer": "Metriport Medical API needs an API key. Redox uses an OAuth sign-in.", "question": "Do Metriport Medical API and Redox need an API key?" }, { "answer": "No hosted endpoint is listed for Metriport Medical API. Redox has a hosted endpoint at https://api.redoxengine.com/mcp.", "question": "Can an agent call Metriport Medical API and Redox without installing anything?" }, { "answer": "Metriport Medical API is open source (Proprietary hosted service under Metriport's terms of use. The source in metriport/metriport is AGPLv3, with an enterprise directory under its own licence, and the @metriport/api-sdk package on npm is MIT). No open-source release is listed for Redox.", "question": "Are Metriport Medical API and Redox open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 65 against 56", "Agent ergonomics, 70 against 54", "Maintenance \u0026 community, 74 against 31" ], "also": [ "Open source" ], "goodFor": "US care providers and digital health companies that need a patient's network records as FHIR with webhooks.", "slug": "metriport", "watchFor": "Every API key has full access, including destructive operations, with no scopes" }, { "aheadOn": [ "Reliability, 85 against 45", "Security \u0026 auth, 78 against 41", "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-metriport.json", "title": "Aidbox vs Metriport Medical API", "url": "https://www.anchorterminal.com/compare/aidbox-vs-metriport" }, { "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/medplum-vs-metriport.json", "title": "Medplum vs Metriport Medical API", "url": "https://www.anchorterminal.com/compare/medplum-vs-metriport" }, { "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/metriport-vs-rook.json", "title": "Metriport Medical API vs ROOK", "url": "https://www.anchorterminal.com/compare/metriport-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/metriport-vs-terra.json", "title": "Metriport Medical API vs Terra API", "url": "https://www.anchorterminal.com/compare/metriport-vs-terra" }, { "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-metriport.json", "title": "1upHealth vs Metriport Medical API", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-metriport" }, { "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-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-redox.json", "title": "Health Gorilla vs Redox", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-redox" }, { "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-redox.json", "title": "Medblocks vs Redox", "url": "https://www.anchorterminal.com/compare/medblocks-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/metriport-vs-particle-health.json", "title": "Metriport Medical API vs Particle Health", "url": "https://www.anchorterminal.com/compare/metriport-vs-particle-health" }, { "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-redox.json", "title": "Particle Health vs Redox", "url": "https://www.anchorterminal.com/compare/particle-health-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/metriport-vs-validic.json", "title": "Metriport Medical API vs Validic Inform", "url": "https://www.anchorterminal.com/compare/metriport-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": 40, "edge": "redox", "key": "reliability", "metriport": 45, "name": "Reliability", "redox": 85, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 9, "edge": "metriport", "key": "schema", "metriport": 65, "name": "Schema \u0026 documentation", "redox": 56, "weight": 13 }, { "by": 16, "edge": "metriport", "key": "ergonomics", "metriport": 70, "name": "Agent ergonomics", "redox": 54, "weight": 13 }, { "by": 37, "edge": "redox", "key": "security", "metriport": 41, "name": "Security \u0026 auth", "redox": 78, "weight": 14 }, { "by": 10, "edge": "redox", "key": "payments", "metriport": 5, "name": "Payments \u0026 pricing", "redox": 15, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 43, "edge": "metriport", "key": "maintenance", "metriport": 74, "name": "Maintenance \u0026 community", "redox": 31, "weight": 7 }, { "by": 3, "edge": "redox", "key": "transparency", "metriport": 56, "name": "Transparency \u0026 trust", "redox": 59, "weight": 7 } ], "summary": "Redox scores 58.3 (C) on agent readiness against Metriport Medical API's 50.1 (D), and leads in 4 of 7 scored categories. Metriport Medical API leads on schema \u0026 documentation, agent ergonomics and maintenance \u0026 community. Both do patient record retrieval.", "verdicts": { "metriport": "One network query pulls a patient's records from HIEs, pharmacies and labs and returns deduplicated FHIR, with per-operation rate limits, RFC 7807 errors and AGPLv3 source. Each API key has full access with no scopes, there are no public prices, and the sandbox opens only after Metriport approves the account.", "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/metriport-vs-redox", "json": "https://www.anchorterminal.com/compare/metriport-vs-redox.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/metriport-vs-redox.md", "slim": "https://www.anchorterminal.com/compare/metriport-vs-redox.min.md" }, "markdown": "Redox scores 58.3 (C) on agent readiness against Metriport Medical API's 50.1 (D), and leads in 4 of 7 scored categories. Metriport Medical API leads on schema \u0026 documentation, agent ergonomics and maintenance \u0026 community. Both do patient record retrieval.\n\n- Metriport Medical API: grade D, 50.1/100, rank #833 of 1076. Markdown https://www.anchorterminal.com/tools/metriport.md · JSON https://www.anchorterminal.com/api/v1/tools/metriport.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### Metriport Medical API (D)\n\nGood for: US care providers and digital health companies that need a patient's network records as FHIR with webhooks.\n\nAhead on:\n- Schema \u0026 documentation, 65 against 56\n- Agent ergonomics, 70 against 54\n- Maintenance \u0026 community, 74 against 31\n\nAlso in its favour:\n- Open source\n\nWatch for: Every API key has full access, including destructive operations, with no scopes\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 45\n- Security \u0026 auth, 78 against 41\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 | Metriport Medical API | Redox | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 85 | Redox +40 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 65 | 56 | Metriport Medical API +9 |\n| Agent ergonomics | 13% (16.2 this run) | 70 | 54 | Metriport Medical API +16 |\n| Security \u0026 auth | 14% (17.5 this run) | 41 | 78 | Redox +37 |\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) | 74 | 31 | Metriport Medical API +43 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 56 | 59 | Redox +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.1 · D** | **58.3 · C** | |\n\n## Facts side by side\n\n| Fact | Metriport Medical API | Redox |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Metriport Inc. | Redox, Inc. |\n| Hosted endpoint | no (local only) | `https://api.redoxengine.com/mcp` |\n| Transports | HTTP | HTTP |\n| Auth | API key | OAuth |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary hosted service under Metriport's terms of use. The source in metriport/metriport is AGPLv3, with an enterprise directory under its own licence, and the @metriport/api-sdk package on npm is MIT | 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-09-28 | none |\n| Terms last updated | 2024-01-01 | 2015-10-17 |\n| Privacy policy last updated | 2023-02-21 | 2023-01-18 |\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 | yes | not found in the text |\n| Popularity | 793 stars, 28k npm/wk | none |\n\n## Verdicts\n\n**Metriport Medical API.** One network query pulls a patient's records from HIEs, pharmacies and labs and returns deduplicated FHIR, with per-operation rate limits, RFC 7807 errors and AGPLv3 source. Each API key has full access with no scopes, there are no public prices, and the sandbox opens only after Metriport approves the account.\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### Metriport Medical API\n\n1. Check the `errors` array after Start Network Query. It returns 2XX even when some sources fail\n2. Wait for `network-query.*` webhooks or poll Get Network Query Status before reading consolidated data, which is cached from the last query\n3. Send the resource's `eTag` in `If-Match` on updates to avoid overwriting newer data\n4. Keep patient creates under 15 a minute and network queries under 20 a minute per source\n5. In sandbox, create patients whose first name matches a pre-defined persona to get example records\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, Metriport Medical API or Redox?\n\nRedox scores 58.3 (C) on agent readiness against Metriport Medical API's 50.1 (D), and leads in 4 of 7 scored categories. Metriport Medical API leads on schema \u0026 documentation, agent ergonomics and maintenance \u0026 community.\n\n### Do Metriport Medical API and Redox need an API key?\n\nMetriport Medical API needs an API key. Redox uses an OAuth sign-in.\n\n### Can an agent call Metriport Medical API and Redox without installing anything?\n\nNo hosted endpoint is listed for Metriport Medical API. Redox has a hosted endpoint at https://api.redoxengine.com/mcp.\n\n### Are Metriport Medical API and Redox open source?\n\nMetriport Medical API is open source (Proprietary hosted service under Metriport's terms of use. The source in metriport/metriport is AGPLv3, with an enterprise directory under its own licence, and the @metriport/api-sdk package on npm is MIT). No open-source release is listed for Redox.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/metriport-vs-redox.json, and with the fewest tokens: https://www.anchorterminal.com/compare/metriport-vs-redox.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"metriport\", \"b\": \"redox\"}`. From a terminal: `anchor compare metriport redox`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/metriport.json and https://www.anchorterminal.com/api/v1/tools/redox.json\n\n## Other comparisons with Metriport Medical API or Redox\n\n- [Aidbox vs Metriport Medical API](https://www.anchorterminal.com/compare/aidbox-vs-metriport.md)\n- [Aidbox vs Redox](https://www.anchorterminal.com/compare/aidbox-vs-redox.md)\n- [Medplum vs Metriport Medical API](https://www.anchorterminal.com/compare/medplum-vs-metriport.md)\n- [Medplum vs Redox](https://www.anchorterminal.com/compare/medplum-vs-redox.md)\n- [Metriport Medical API vs ROOK](https://www.anchorterminal.com/compare/metriport-vs-rook.md)\n- [Metriport Medical API vs Terra API](https://www.anchorterminal.com/compare/metriport-vs-terra.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 Metriport Medical API](https://www.anchorterminal.com/compare/1uphealth-vs-metriport.md)\n- [1upHealth vs Redox](https://www.anchorterminal.com/compare/1uphealth-vs-redox.md)\n- [Health Gorilla vs Metriport Medical API](https://www.anchorterminal.com/compare/health-gorilla-vs-metriport.md)\n- [Health Gorilla vs Redox](https://www.anchorterminal.com/compare/health-gorilla-vs-redox.md)\n- [Medblocks vs Metriport Medical API](https://www.anchorterminal.com/compare/medblocks-vs-metriport.md)\n- [Medblocks vs Redox](https://www.anchorterminal.com/compare/medblocks-vs-redox.md)\n- [Metriport Medical API vs Particle Health](https://www.anchorterminal.com/compare/metriport-vs-particle-health.md)\n- [Metriport Medical API vs Zus Health](https://www.anchorterminal.com/compare/metriport-vs-zus-health.md)\n- [Particle Health vs Redox](https://www.anchorterminal.com/compare/particle-health-vs-redox.md)\n- [Metriport Medical API vs Validic Inform](https://www.anchorterminal.com/compare/metriport-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": "Metriport Medical API vs Redox", "url": "" } ], "description": "Redox scores 58.3 (C) to Metriport Medical's 50.1 (D) for patient record retrieval. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Metriport Medical API D 50.1", "Redox C 58.3", "scores" ], "h1": "Metriport Medical API vs Redox", "image": "https://www.anchorterminal.com/assets/og/compare-metriport-vs-redox.png", "path": "/compare/metriport-vs-redox", "published": "2026-10-01", "section": "tools", "title": "Metriport Medical vs Redox for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/metriport-vs-redox" }, "tokens": { "markdown": 2400, "slim": 730 }, "version": 1 }