{ "data": { "a": { "slug": "medplum", "name": "Medplum", "vendor": "Orangebot, Inc. (dba Medplum)", "vendorUrl": "https://www.medplum.com", "kind": "http-api", "category": "health-data", "summary": "Open-source FHIR R4 server and healthcare developer platform from Orangebot, Inc. (dba Medplum). Agents reach patient records through the hosted FHIR REST API at api.medplum.com, a remote MCP server or a self-hosted copy.", "url": "https://www.anchorterminal.com/tools/medplum", "markdownUrl": "https://www.anchorterminal.com/tools/medplum.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/medplum.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/medplum.json", "repo": "https://github.com/medplum/medplum", "license": "Apache 2.0 for the server, SDKs and apps in medplum/medplum. The hosted service at api.medplum.com runs under Medplum's terms of service", "transports": [ "http", "streamable-http", "sse" ], "remoteUrl": "https://api.medplum.com/mcp/stream", "packages": [ { "registry": "npm", "name": "@medplum/core" } ], "auth": "oauth", "authNotes": "OAuth 2.0 and OpenID Connect. Machine clients use the client credentials grant with a ClientApplication ID and secret created on the Project Admin page, and a POST to https://api.medplum.com/oauth2/token. SMART scopes and AccessPolicy resources limit what each user, bot or client can read or write, including read-only policies. The MCP server uses OAuth with a browser login on first connect. Client assertion, token exchange, on-behalf-of and mTLS are also documented.", "pricing": "freemium", "pricingNotes": "Hosted plans on medplum.com/pricing (checked 2026-10-14). Free for prototyping, Production $2,000 a month, Premium $6,000 a month, Enterprise by contact. The paid plans include a standard BAA and MSA. Self-hosting the Apache 2.0 server is free. Whether the free plan asks for a card was not established.", "priceSummary": "$2000 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the pricing page or the repository (checked 2026-10-14).", "endpoints": [] }, "toolCount": 3, "popularity": { "githubStars": 2738, "npmWeekly": 269965, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://www.medplum.com/docs", "llmsTxt": "https://www.medplum.com/llms.txt", "registryName": "com.medplum/mcp", "capabilities": [ "health.fhir", "health.records" ], "tags": [ "hosted", "open-source", "self-hosted", "fhir", "mcp", "oauth", "smart-on-fhir", "hipaa", "soc2", "typescript", "llms-txt", "status-page" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 68.7, "grade": "B", "agentReady": false, "rank": 216, "ranked": true, "rankOf": 1076, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 93, "payments": 25, "reliability": 75, "schema": 82, "security": 74, "transparency": 72 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": -2, "negativeNotes": [ "2026-07-24: GHSA-m44r-7c5h-m6mj, high severity. The external auth callback accepted redirect URIs that only had to start with a registered one, which could leak authorisation codes cross-origin. Patched in @medplum/core 5.1.6 and disclosed on GitHub (https://github.com/medplum/medplum/security/advisories/GHSA-m44r-7c5h-m6mj). With GHSA-ch8p-j6cm-r7w5 (2 June 2026, client secret exposure in self-hosted dynamic registration), both fixed and disclosed in public, so the deduction is small (-2)." ], "verdict": "Graded on the hosted FHIR API at api.medplum.com. Rate limits, a `RateLimit` header and a 99.99 per cent SLA are published, AccessPolicy resources allow read-only clients, and an official MCP server sits in the registry. Its main tool can delete records with no annotation, the status page could not be read, and the privacy policy dates from 2022.", "bestFor": "An agent working inside a digital health company's own FHIR store, reading and writing patients, observations and appointments under a BAA.", "strengths": [ "Apache 2.0 server with releases about weekly, v5.2.3 on 8 October 2026, and a written version policy", "Rate limits published per tier, with a `RateLimit` header giving remaining units and seconds to reset", "AccessPolicy resources and SMART scopes allow read-only, per-resource or per-element clients", "Official MCP server at api.medplum.com/mcp/stream, listed in the MCP registry as com.medplum/mcp, with OAuth", "99.99 per cent monthly SLA with service credits stated for the production hosted platform" ], "weaknesses": [ "The MCP `fhir-request` tool can delete or overwrite any resource the token allows, with no readOnlyHint or destructiveHint", "The privacy policy was last updated on 5 April 2022 and the terms on 11 April 2023", "No sub-processor list or retention periods were found", "Two high-severity auth advisories were published and patched in 2026", "Official SDK in TypeScript only" ], "agentNotes": [ "Use a ClientApplication with an AccessPolicy limited to the resources the task needs, and set `readonly` where no writes are needed", "Read the `RateLimit` header and wait for the reset time after a 429. Writes cost 100 quota points, searches 20 and reads 1", "Create patients with conditional create (`If-None-Exist`) or upsert on an identifier so a retry doesn't make a duplicate", "Pass paths to `fhir-request` relative to the FHIR R4 base, with no leading slash or `/fhir/R4` prefix", "Use `Prefer: respond-async` for large bundles. Operations inside the background job don't count against the quota" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68.7 } ], "editorialScores": { "ergonomics": 73, "maintenance": 93, "payments": 25, "reliability": 75, "schema": 82, "security": 74, "transparency": 65 }, "provenanceScore": 78 }, "connect": { "install": "npm install @medplum/core", "http": "curl -X POST https://api.medplum.com/oauth2/token \\\n -H \"Content-Type: application/x-www-form-urlencoded\" \\\n -d \"grant_type=client_credentials\u0026client_id=$MY_CLIENT_ID\u0026client_secret=$MY_CLIENT_SECRET\"" }, "letme": { "capability": "https://letme.dev/health.fhir", "tool": "https://letme.dev/medplum" }, "area": "domain-data", "unitPrices": [ { "item": "Production plan", "unit": "month", "usd": 2000, "note": "Hosted, BAA included, Growth usage tier" }, { "item": "Premium plan", "unit": "month", "usd": 6000, "note": "Hosted, adds lab, medication and HL7 integrations" } ], "provenance": { "legalEntity": "Orangebot, Inc.", "domain": "medplum.com", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.medplum.com/terms", "privacy": "https://www.medplum.com/privacy", "statusPage": "https://status.medplum.com", "changelog": "https://github.com/medplum/medplum/releases", "securityTxt": "valid", "checked": "2026-10-14", "notes": [ "The pricing and security pages name Orangebot, Inc (dba Medplum).", "www.medplum.com/.well-known/security.txt lists security@medplum.com, a PGP key and expires 2027-02-28.", "robots.txt on api.medplum.com and status.medplum.com disallows every path for all agents, so the status history and the live OpenAPI document were not read.", "The terms of service were last updated 2023-04-11 and the privacy policy 2022-04-05.", "The domain registration date was not established." ], "score": 78 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/medplum.json", "live": { "slug": "medplum", "probe": { "target": "https://api.medplum.com/mcp/stream", "method": "get", "lastAt": "2026-10-14T09:41:57.409301454Z", "lastOk": true, "lastStatus": 401, "lastMs": 255, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 256, "p95ms24h": 389, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.medplum.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:53:23.189127499Z" }, "updatedAt": "2026-10-14T09:41:57.409301454Z" } }, "answer": "Medplum scores 68.7 (B) on agent readiness against Particle Health's 48.6 (D), and leads in every scored category.", "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": "Orangebot, Inc. (dba Medplum)", "b": "Particle Health, Inc.", "name": "Vendor" }, { "a": "https://api.medplum.com/mcp/stream", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP, SSE (legacy)", "b": "HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache 2.0 for the server, SDKs and apps in medplum/medplum. The hosted service at api.medplum.com runs under Medplum's terms of service", "b": "Proprietary service under customer agreements. The public terms of use (effective 15 October 2020) cover the website only", "name": "Licence" }, { "a": "3", "b": "none", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "com.medplum/mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-08", "b": "none", "name": "Last release" }, { "a": "2023-04-11", "b": "2020-10-15", "name": "Terms last updated" }, { "a": "2022-04-05", "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": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "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": "2.7k stars, 270k npm/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Medplum scores 68.7 (B) on agent readiness against Particle Health's 48.6 (D), and leads in every scored category.", "question": "Which is better for AI agents, Medplum or Particle Health?" }, { "answer": "Both use an OAuth sign-in.", "question": "Do Medplum and Particle Health need an API key?" }, { "answer": "Medplum has a hosted endpoint at https://api.medplum.com/mcp/stream. No hosted endpoint is listed for Particle Health.", "question": "Can an agent call Medplum and Particle Health without installing anything?" }, { "answer": "Medplum is open source (Apache 2.0 for the server, SDKs and apps in medplum/medplum. The hosted service at api.medplum.com runs under Medplum's terms of service). No open-source release is listed for Particle Health.", "question": "Are Medplum and Particle Health open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 75 against 58", "Schema \u0026 documentation, 82 against 69", "Agent ergonomics, 73 against 53", "Security \u0026 auth, 74 against 57", "Payments \u0026 pricing, 25 against 5", "Maintenance \u0026 community, 93 against 27", "Transparency \u0026 trust, 72 against 48" ], "also": [ "A hosted endpoint, with nothing to install", "Open source" ], "goodFor": "An agent working inside a digital health company's own FHIR store, reading and writing patients, observations and appointments under a BAA.", "slug": "medplum", "watchFor": "The MCP `fhir-request` tool can delete or overwrite any resource the token allows, with no readOnlyHint or destructiveHint" }, { "aheadOn": null, "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.fhir", "name": "FHIR servers" }, "others": [ { "json": "https://www.anchorterminal.com/compare/aidbox-vs-medplum.json", "title": "Aidbox vs Medplum", "url": "https://www.anchorterminal.com/compare/aidbox-vs-medplum" }, { "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-redox.json", "title": "Medplum vs Redox", "url": "https://www.anchorterminal.com/compare/medplum-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/medplum-vs-rook.json", "title": "Medplum vs ROOK", "url": "https://www.anchorterminal.com/compare/medplum-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/medplum-vs-terra.json", "title": "Medplum vs Terra API", "url": "https://www.anchorterminal.com/compare/medplum-vs-terra" }, { "json": "https://www.anchorterminal.com/compare/medplum-vs-zus-health.json", "title": "Medplum vs Zus Health", "url": "https://www.anchorterminal.com/compare/medplum-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/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-medplum.json", "title": "1upHealth vs Medplum", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-medplum" }, { "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-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-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-medplum.json", "title": "Medblocks vs Medplum", "url": "https://www.anchorterminal.com/compare/medblocks-vs-medplum" }, { "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-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/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" } ], "scores": [ { "by": 17, "edge": "medplum", "key": "reliability", "medplum": 75, "name": "Reliability", "particle-health": 58, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "edge": "medplum", "key": "schema", "medplum": 82, "name": "Schema \u0026 documentation", "particle-health": 69, "weight": 13 }, { "by": 20, "edge": "medplum", "key": "ergonomics", "medplum": 73, "name": "Agent ergonomics", "particle-health": 53, "weight": 13 }, { "by": 17, "edge": "medplum", "key": "security", "medplum": 74, "name": "Security \u0026 auth", "particle-health": 57, "weight": 14 }, { "by": 20, "edge": "medplum", "key": "payments", "medplum": 25, "name": "Payments \u0026 pricing", "particle-health": 5, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 66, "edge": "medplum", "key": "maintenance", "medplum": 93, "name": "Maintenance \u0026 community", "particle-health": 27, "weight": 7 }, { "by": 24, "edge": "medplum", "key": "transparency", "medplum": 72, "name": "Transparency \u0026 trust", "particle-health": 48, "weight": 7 } ], "summary": "Medplum scores 68.7 (B) on agent readiness against Particle Health's 48.6 (D), and leads in every scored category. Both do fhir servers.", "verdicts": { "medplum": "Graded on the hosted FHIR API at api.medplum.com. Rate limits, a `RateLimit` header and a 99.99 per cent SLA are published, AccessPolicy resources allow read-only clients, and an official MCP server sits in the registry. Its main tool can delete records with no annotation, the status page could not be read, and the privacy policy dates from 2022.", "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/medplum-vs-particle-health", "json": "https://www.anchorterminal.com/compare/medplum-vs-particle-health.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/medplum-vs-particle-health.md", "slim": "https://www.anchorterminal.com/compare/medplum-vs-particle-health.min.md" }, "markdown": "Medplum scores 68.7 (B) on agent readiness against Particle Health's 48.6 (D), and leads in every scored category. Both do fhir servers.\n\n- Medplum: grade B, 68.7/100, rank #216 of 1076. Markdown https://www.anchorterminal.com/tools/medplum.md · JSON https://www.anchorterminal.com/api/v1/tools/medplum.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### Medplum (B)\n\nGood for: An agent working inside a digital health company's own FHIR store, reading and writing patients, observations and appointments under a BAA.\n\nAhead on:\n- Reliability, 75 against 58\n- Schema \u0026 documentation, 82 against 69\n- Agent ergonomics, 73 against 53\n- Security \u0026 auth, 74 against 57\n- Payments \u0026 pricing, 25 against 5\n- Maintenance \u0026 community, 93 against 27\n- Transparency \u0026 trust, 72 against 48\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Open source\n\nWatch for: The MCP `fhir-request` tool can delete or overwrite any resource the token allows, with no readOnlyHint or destructiveHint\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\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 | Medplum | Particle Health | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 75 | 58 | Medplum +17 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 82 | 69 | Medplum +13 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 53 | Medplum +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 74 | 57 | Medplum +17 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 25 | 5 | Medplum +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 93 | 27 | Medplum +66 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 48 | Medplum +24 |\n| Negative events | ≤15 | -2 | 0 | |\n| **Total** | | **68.7 · B** | **48.6 · D** | |\n\n## Facts side by side\n\n| Fact | Medplum | Particle Health |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Orangebot, Inc. (dba Medplum) | Particle Health, Inc. |\n| Hosted endpoint | `https://api.medplum.com/mcp/stream` | no (local only) |\n| Transports | HTTP, Streamable HTTP, SSE (legacy) | HTTP |\n| Auth | OAuth | OAuth |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | Apache 2.0 for the server, SDKs and apps in medplum/medplum. The hosted service at api.medplum.com runs under Medplum's terms of service | Proprietary service under customer agreements. The public terms of use (effective 15 October 2020) cover the website only |\n| Tools exposed | 3 | none |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| MCP registry | `com.medplum/mcp` | not listed |\n| Last release | 2026-10-08 | none |\n| Terms last updated | 2023-04-11 | 2020-10-15 |\n| Privacy policy last updated | 2022-04-05 | 2026-07-29 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | not found in the text | 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 | 2.7k stars, 270k npm/wk | none |\n\n## Verdicts\n\n**Medplum.** Graded on the hosted FHIR API at api.medplum.com. Rate limits, a `RateLimit` header and a 99.99 per cent SLA are published, AccessPolicy resources allow read-only clients, and an official MCP server sits in the registry. Its main tool can delete records with no annotation, the status page could not be read, and the privacy policy dates from 2022.\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### Medplum\n\n1. Use a ClientApplication with an AccessPolicy limited to the resources the task needs, and set `readonly` where no writes are needed\n2. Read the `RateLimit` header and wait for the reset time after a 429. Writes cost 100 quota points, searches 20 and reads 1\n3. Create patients with conditional create (`If-None-Exist`) or upsert on an identifier so a retry doesn't make a duplicate\n4. Pass paths to `fhir-request` relative to the FHIR R4 base, with no leading slash or `/fhir/R4` prefix\n5. Use `Prefer: respond-async` for large bundles. Operations inside the background job don't count against the quota\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, Medplum or Particle Health?\n\nMedplum scores 68.7 (B) on agent readiness against Particle Health's 48.6 (D), and leads in every scored category.\n\n### Do Medplum and Particle Health need an API key?\n\nBoth use an OAuth sign-in.\n\n### Can an agent call Medplum and Particle Health without installing anything?\n\nMedplum has a hosted endpoint at https://api.medplum.com/mcp/stream. No hosted endpoint is listed for Particle Health.\n\n### Are Medplum and Particle Health open source?\n\nMedplum is open source (Apache 2.0 for the server, SDKs and apps in medplum/medplum. The hosted service at api.medplum.com runs under Medplum's terms of service). 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/medplum-vs-particle-health.json, and with the fewest tokens: https://www.anchorterminal.com/compare/medplum-vs-particle-health.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"medplum\", \"b\": \"particle-health\"}`. From a terminal: `anchor compare medplum particle-health`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/medplum.json and https://www.anchorterminal.com/api/v1/tools/particle-health.json\n\n## Other comparisons with Medplum or Particle Health\n\n- [Aidbox vs Medplum](https://www.anchorterminal.com/compare/aidbox-vs-medplum.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 Redox](https://www.anchorterminal.com/compare/medplum-vs-redox.md)\n- [Medplum vs ROOK](https://www.anchorterminal.com/compare/medplum-vs-rook.md)\n- [Medplum vs Terra API](https://www.anchorterminal.com/compare/medplum-vs-terra.md)\n- [Medplum vs Zus Health](https://www.anchorterminal.com/compare/medplum-vs-zus-health.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 Medplum](https://www.anchorterminal.com/compare/1uphealth-vs-medplum.md)\n- [1upHealth vs Particle Health](https://www.anchorterminal.com/compare/1uphealth-vs-particle-health.md)\n- [Health Gorilla vs Medplum](https://www.anchorterminal.com/compare/health-gorilla-vs-medplum.md)\n- [Health Gorilla vs Particle Health](https://www.anchorterminal.com/compare/health-gorilla-vs-particle-health.md)\n- [Medblocks vs Medplum](https://www.anchorterminal.com/compare/medblocks-vs-medplum.md)\n- [Medblocks vs Particle Health](https://www.anchorterminal.com/compare/medblocks-vs-particle-health.md)\n- [Metriport Medical API vs Particle Health](https://www.anchorterminal.com/compare/metriport-vs-particle-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", "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": "Medplum vs Particle Health", "url": "" } ], "description": "Medplum scores 68.7 (B) to Particle Health's 48.6 (D) for fhir servers. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Medplum B 68.7", "Particle Health D 48.6", "scores" ], "h1": "Medplum vs Particle Health", "image": "https://www.anchorterminal.com/assets/og/compare-medplum-vs-particle-health.png", "path": "/compare/medplum-vs-particle-health", "published": "2026-10-01", "section": "tools", "title": "Medplum vs Particle Health for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/medplum-vs-particle-health" }, "tokens": { "markdown": 2350, "slim": 680 }, "version": 1 }