{ "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": "Metriport Medical API scores 50.1 (D) on agent readiness against Particle Health's 48.6 (D), and leads in 3 of 7 scored categories. Particle Health leads on reliability and security \u0026 auth.", "b": { "slug": "particle-health", "name": "Particle Health", "vendor": "Particle Health, Inc.", "vendorUrl": "https://particlehealth.com", "kind": "http-api", "category": "health-data", "summary": "Particle Health retrieves patient records from Carequality, CommonWell, eHealth Exchange, state HIEs and Surescripts, and returns them as FHIR R4B, flat datasets or C-CDA through a REST API, with Signal webhooks for care events.", "url": "https://www.anchorterminal.com/tools/particle-health", "markdownUrl": "https://www.anchorterminal.com/tools/particle-health.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/particle-health.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/particle-health.json", "license": "Proprietary service under customer agreements. The public terms of use (effective 15 October 2020) cover the website only", "transports": [ "http" ], "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 client credentials. A Particle representative issues the first client ID and secret, after which the Management APIs can create service accounts and credentials, and creating new credentials expires the old ones. Each token request must name one project as its scope, and tokens last 60 minutes. Service accounts carry IAM roles such as `roles/project.owner`.", "pricing": "paid", "pricingNotes": "No public prices. The developers page links 'play for free' to portal.particlehealth.com/signup, which did not resolve on 14 October 2026, and the docs ask developers to contact a representative for credentials. The sandbox allows 500 queries per organisation a day (checked 2026-10-14).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, llms.txt or the website (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.particlehealth.com", "llmsTxt": "https://docs.particlehealth.com/llms.txt", "capabilities": [ "health.records", "health.fhir" ], "tags": [ "hosted", "health-records", "fhir", "ccda", "oauth", "llms-txt", "webhooks", "status-page", "sales-led", "hitrust", "soc2" ], "graded": true, "anchor": { "graded": true, "score": 48.6, "grade": "D", "agentReady": false, "rank": 867, "ranked": true, "rankOf": 1076, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 27, "payments": 5, "reliability": 58, "schema": 69, "security": 57, "transparency": 48 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Particle queries Carequality, CommonWell, eHealth Exchange and state HIEs for a patient and returns FHIR R4B, flat data or C-CDA, with project-scoped 60-minute tokens and OpenAPI fragments per endpoint. Credentials come through a representative, the free sign-up link was dead on 14 October 2026, and rate limits, SLA and changelog are unpublished.", "bestFor": "US providers, payers and digital health companies that need a patient's network records as FHIR or flat data, and care-event alerts.", "strengths": [ "Connected to all three national networks plus Healthix, Manifest MedEx and Surescripts", "Tokens scoped to one project and expiring after 60 minutes, with credential rotation that retires old secrets", "FHIR R4B, flat datasets and C-CDA from the same query", "Sandbox of synthetic patients across every production workflow, 500 queries a day" ], "weaknesses": [ "Credentials come from a Particle representative, and the 'play for free' sign-up domain did not resolve", "Rate limits vary with load and have no published numbers", "No changelog, SLA or developer terms in public", "No audit log for operators was found" ], "agentNotes": [ "Pass `projects/\u003cproject_id\u003e` as the scope when requesting a token, and request a new one every 60 minutes", "Poll Get Query Status, or wait for the query-complete webhook, before reading FHIR or flat data", "Back off on 429, since limits change with system load", "Pass continuation tokens back verbatim when paging", "Use the published synthetic patients in sandbox, and stay under 500 queries a day" ], "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": 48.6 } ], "editorialScores": { "ergonomics": 53, "maintenance": 27, "payments": 5, "reliability": 58, "schema": 69, "security": 57, "transparency": 27 }, "provenanceScore": 69 }, "connect": { "http": "POST https://sandbox.particlehealth.com/api/v2/patients\nAuthorization: Bearer \u003caccess-token\u003e\nContent-Type: application/json" }, "letme": { "capability": "https://letme.dev/health.records", "tool": "https://letme.dev/particle-health" }, "area": "domain-data", "provenance": { "legalEntity": "Particle Health, Inc.", "domain": "particlehealth.com", "domainRegistered": "2017-11-22", "endpointOnVendorDomain": true, "terms": "https://particlehealth.com/terms-of-use", "privacy": "https://particlehealth.com/privacy-policy", "statusPage": "https://status.particlehealth.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The terms of use (effective 15 October 2020) cover the website, forbid users to 'harvest or scrape any content or data from the Site', and may change without notice. We read them as a fact and fetched only what robots.txt allows.", "The privacy policy (effective 29 July 2026) covers information collected through the site only and says Particle may keep de-identified data in aggregate.", "The security page lists HITRUST and SOC 2 for the API platform and links a vulnerability submission form. particlehealth.com/.well-known/security.txt returns 404.", "docs.particlehealth.com/changelog returns 404. No public changelog was found.", "RDAP gives particlehealth.com a registration date of 2017-11-22." ], "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/particle-health.json", "live": { "slug": "particle-health", "vendorStatus": { "page": "https://status.particlehealth.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:35.139260792Z" }, "updatedAt": "2026-10-14T09:39:35.139260792Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Metriport Inc.", "b": "Particle Health, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "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 customer agreements. The public terms of use (effective 15 October 2020) cover the website only", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-28", "b": "none", "name": "Last release" }, { "a": "2024-01-01", "b": "2020-10-15", "name": "Terms last updated" }, { "a": "2023-02-21", "b": "2026-07-29", "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": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "793 stars, 28k npm/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Metriport Medical API scores 50.1 (D) on agent readiness against Particle Health's 48.6 (D), and leads in 3 of 7 scored categories. Particle Health leads on reliability and security \u0026 auth.", "question": "Which is better for AI agents, Metriport Medical API or Particle Health?" }, { "answer": "Metriport Medical API needs an API key. Particle Health uses an OAuth sign-in.", "question": "Do Metriport Medical API and Particle Health need an API key?" }, { "answer": "No hosted endpoint is listed for Metriport Medical API. No hosted endpoint is listed for Particle Health.", "question": "Can an agent call Metriport Medical API and Particle Health 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 Particle Health.", "question": "Are Metriport Medical API and Particle Health open source?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 70 against 53", "Maintenance \u0026 community, 74 against 27", "Transparency \u0026 trust, 56 against 48" ], "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, 58 against 45", "Security \u0026 auth, 57 against 41" ], "also": null, "goodFor": "US providers, payers and digital health companies that need a patient's network records as FHIR or flat data, and care-event alerts.", "slug": "particle-health", "watchFor": "Credentials come from a Particle representative, and the 'play for free' sign-up domain did not resolve" } ], "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-particle-health.json", "title": "Aidbox vs Particle Health", "url": "https://www.anchorterminal.com/compare/aidbox-vs-particle-health" }, { "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-particle-health.json", "title": "Medplum vs Particle Health", "url": "https://www.anchorterminal.com/compare/medplum-vs-particle-health" }, { "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/particle-health-vs-rook.json", "title": "Particle Health vs ROOK", "url": "https://www.anchorterminal.com/compare/particle-health-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/particle-health-vs-terra.json", "title": "Particle Health vs Terra API", "url": "https://www.anchorterminal.com/compare/particle-health-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-particle-health.json", "title": "1upHealth vs Particle Health", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-particle-health" }, { "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/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/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/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/particle-health-vs-zus-health.json", "title": "Particle Health vs Zus Health", "url": "https://www.anchorterminal.com/compare/particle-health-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/metriport-vs-validic.json", "title": "Metriport Medical API vs Validic Inform", "url": "https://www.anchorterminal.com/compare/metriport-vs-validic" } ], "scores": [ { "by": 13, "edge": "particle-health", "key": "reliability", "metriport": 45, "name": "Reliability", "particle-health": 58, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 4, "edge": "particle-health", "key": "schema", "metriport": 65, "name": "Schema \u0026 documentation", "particle-health": 69, "weight": 13 }, { "by": 17, "edge": "metriport", "key": "ergonomics", "metriport": 70, "name": "Agent ergonomics", "particle-health": 53, "weight": 13 }, { "by": 16, "edge": "particle-health", "key": "security", "metriport": 41, "name": "Security \u0026 auth", "particle-health": 57, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "metriport": 5, "name": "Payments \u0026 pricing", "particle-health": 5, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 47, "edge": "metriport", "key": "maintenance", "metriport": 74, "name": "Maintenance \u0026 community", "particle-health": 27, "weight": 7 }, { "by": 8, "edge": "metriport", "key": "transparency", "metriport": 56, "name": "Transparency \u0026 trust", "particle-health": 48, "weight": 7 } ], "summary": "Metriport Medical API scores 50.1 (D) on agent readiness against Particle Health's 48.6 (D), and leads in 3 of 7 scored categories. Particle Health leads on reliability and security \u0026 auth. 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.", "particle-health": "Particle queries Carequality, CommonWell, eHealth Exchange and state HIEs for a patient and returns FHIR R4B, flat data or C-CDA, with project-scoped 60-minute tokens and OpenAPI fragments per endpoint. Credentials come through a representative, the free sign-up link was dead on 14 October 2026, and rate limits, SLA and changelog are unpublished." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/metriport-vs-particle-health", "json": "https://www.anchorterminal.com/compare/metriport-vs-particle-health.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/metriport-vs-particle-health.md", "slim": "https://www.anchorterminal.com/compare/metriport-vs-particle-health.min.md" }, "markdown": "Metriport Medical API scores 50.1 (D) on agent readiness against Particle Health's 48.6 (D), and leads in 3 of 7 scored categories. Particle Health leads on reliability and security \u0026 auth. 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- Particle Health: grade D, 48.6/100, rank #867 of 1076. Markdown https://www.anchorterminal.com/tools/particle-health.md · JSON https://www.anchorterminal.com/api/v1/tools/particle-health.json\n- Best health record and wellness data APIs for AI agents: https://www.anchorterminal.com/best/health-data/index.md\n- All 63 health comparisons: https://www.anchorterminal.com/compare/health-data/index.md\n\n## Which one, for what\n\n### 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- Agent ergonomics, 70 against 53\n- Maintenance \u0026 community, 74 against 27\n- Transparency \u0026 trust, 56 against 48\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### Particle Health (D)\n\nGood for: US providers, payers and digital health companies that need a patient's network records as FHIR or flat data, and care-event alerts.\n\nAhead on:\n- Reliability, 58 against 45\n- Security \u0026 auth, 57 against 41\n\nWatch for: Credentials come from a Particle representative, and the 'play for free' sign-up domain did not resolve\n\n\n## Score by category\n\n| Category | Weight | Metriport Medical API | Particle Health | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 58 | Particle Health +13 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 65 | 69 | Particle Health +4 |\n| Agent ergonomics | 13% (16.2 this run) | 70 | 53 | Metriport Medical API +17 |\n| Security \u0026 auth | 14% (17.5 this run) | 41 | 57 | Particle Health +16 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 5 | 5 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 74 | 27 | Metriport Medical API +47 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 56 | 48 | Metriport Medical API +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.1 · D** | **48.6 · D** | |\n\n## Facts side by side\n\n| Fact | Metriport Medical API | Particle Health |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Metriport Inc. | Particle Health, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\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 customer agreements. The public terms of use (effective 15 October 2020) cover the website only |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-28 | none |\n| Terms last updated | 2024-01-01 | 2020-10-15 |\n| Privacy policy last updated | 2023-02-21 | 2026-07-29 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | yes | yes |\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**Particle Health.** Particle queries Carequality, CommonWell, eHealth Exchange and state HIEs for a patient and returns FHIR R4B, flat data or C-CDA, with project-scoped 60-minute tokens and OpenAPI fragments per endpoint. Credentials come through a representative, the free sign-up link was dead on 14 October 2026, and rate limits, SLA and changelog are unpublished.\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### Particle Health\n\n1. Pass `projects/\u003cproject_id\u003e` as the scope when requesting a token, and request a new one every 60 minutes\n2. Poll Get Query Status, or wait for the query-complete webhook, before reading FHIR or flat data\n3. Back off on 429, since limits change with system load\n4. Pass continuation tokens back verbatim when paging\n5. Use the published synthetic patients in sandbox, and stay under 500 queries a day\n\n## Questions\n\n### Which is better for AI agents, Metriport Medical API or Particle Health?\n\nMetriport Medical API scores 50.1 (D) on agent readiness against Particle Health's 48.6 (D), and leads in 3 of 7 scored categories. Particle Health leads on reliability and security \u0026 auth.\n\n### Do Metriport Medical API and Particle Health need an API key?\n\nMetriport Medical API needs an API key. Particle Health uses an OAuth sign-in.\n\n### Can an agent call Metriport Medical API and Particle Health without installing anything?\n\nNo hosted endpoint is listed for Metriport Medical API. No hosted endpoint is listed for Particle Health.\n\n### Are Metriport Medical API and Particle Health 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 Particle Health.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/metriport-vs-particle-health.json, and with the fewest tokens: https://www.anchorterminal.com/compare/metriport-vs-particle-health.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"metriport\", \"b\": \"particle-health\"}`. From a terminal: `anchor compare metriport particle-health`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/metriport.json and https://www.anchorterminal.com/api/v1/tools/particle-health.json\n\n## Other comparisons with Metriport Medical API or Particle Health\n\n- [Aidbox vs Metriport Medical API](https://www.anchorterminal.com/compare/aidbox-vs-metriport.md)\n- [Aidbox vs Particle Health](https://www.anchorterminal.com/compare/aidbox-vs-particle-health.md)\n- [Medplum vs Metriport Medical API](https://www.anchorterminal.com/compare/medplum-vs-metriport.md)\n- [Medplum vs Particle Health](https://www.anchorterminal.com/compare/medplum-vs-particle-health.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- [Particle Health vs ROOK](https://www.anchorterminal.com/compare/particle-health-vs-rook.md)\n- [Particle Health vs Terra API](https://www.anchorterminal.com/compare/particle-health-vs-terra.md)\n- [1upHealth vs Metriport Medical API](https://www.anchorterminal.com/compare/1uphealth-vs-metriport.md)\n- [1upHealth vs Particle Health](https://www.anchorterminal.com/compare/1uphealth-vs-particle-health.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- [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- [Metriport Medical API vs Redox](https://www.anchorterminal.com/compare/metriport-vs-redox.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- [Particle Health vs Zus Health](https://www.anchorterminal.com/compare/particle-health-vs-zus-health.md)\n- [Metriport Medical API vs Validic Inform](https://www.anchorterminal.com/compare/metriport-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": "Metriport Medical API vs Particle Health", "url": "" } ], "description": "Metriport Medical scores 50.1 (D) to Particle Health's 48.6 (D) for patient record retrieval. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Metriport Medical API D 50.1", "Particle Health D 48.6", "scores" ], "h1": "Metriport Medical API vs Particle Health", "image": "https://www.anchorterminal.com/assets/og/compare-metriport-vs-particle-health.png", "path": "/compare/metriport-vs-particle-health", "published": "2026-10-01", "section": "tools", "title": "Metriport Medical vs Particle Health for AI agents (2026)", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/metriport-vs-particle-health" }, "tokens": { "markdown": 2450, "slim": 630 }, "version": 1 }