{ "data": { "a": { "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" } }, "answer": "Redox scores 58.3 (C) on agent readiness against Particle Health's 48.6 (D), and leads in 6 of 7 scored categories. Particle Health leads on schema \u0026 documentation.", "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": "Particle Health, Inc.", "b": "Redox, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.redoxengine.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under customer agreements. The public terms of use (effective 15 October 2020) cover the website only", "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": "2020-10-15", "b": "2015-10-17", "name": "Terms last updated" }, { "a": "2026-07-29", "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": "not found in the text", "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" } ], "faq": [ { "answer": "Redox scores 58.3 (C) on agent readiness against Particle Health's 48.6 (D), and leads in 6 of 7 scored categories. Particle Health leads on schema \u0026 documentation.", "question": "Which is better for AI agents, Particle Health or Redox?" }, { "answer": "Both use an OAuth sign-in.", "question": "Do Particle Health and Redox need an API key?" }, { "answer": "No hosted endpoint is listed for Particle Health. Redox has a hosted endpoint at https://api.redoxengine.com/mcp.", "question": "Can an agent call Particle Health and Redox without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 69 against 56" ], "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" }, { "aheadOn": [ "Reliability, 85 against 58", "Security \u0026 auth, 78 against 57", "Payments \u0026 pricing, 15 against 5", "Transparency \u0026 trust, 59 against 48" ], "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-particle-health.json", "title": "Aidbox vs Particle Health", "url": "https://www.anchorterminal.com/compare/aidbox-vs-particle-health" }, { "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-particle-health.json", "title": "Medplum vs Particle Health", "url": "https://www.anchorterminal.com/compare/medplum-vs-particle-health" }, { "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/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/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-particle-health.json", "title": "1upHealth vs Particle Health", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-particle-health" }, { "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-particle-health.json", "title": "Health Gorilla vs Particle Health", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-particle-health" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-redox.json", "title": "Health Gorilla vs Redox", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-particle-health.json", "title": "Medblocks vs Particle Health", "url": "https://www.anchorterminal.com/compare/medblocks-vs-particle-health" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-redox.json", "title": "Medblocks vs Redox", "url": "https://www.anchorterminal.com/compare/medblocks-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/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-redox.json", "title": "Metriport Medical API vs Redox", "url": "https://www.anchorterminal.com/compare/metriport-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/particle-health-vs-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/redox-vs-zus-health.json", "title": "Redox vs Zus Health", "url": "https://www.anchorterminal.com/compare/redox-vs-zus-health" } ], "scores": [ { "by": 27, "edge": "redox", "key": "reliability", "name": "Reliability", "particle-health": 58, "redox": 85, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "edge": "particle-health", "key": "schema", "name": "Schema \u0026 documentation", "particle-health": 69, "redox": 56, "weight": 13 }, { "by": 1, "edge": "redox", "key": "ergonomics", "name": "Agent ergonomics", "particle-health": 53, "redox": 54, "weight": 13 }, { "by": 21, "edge": "redox", "key": "security", "name": "Security \u0026 auth", "particle-health": 57, "redox": 78, "weight": 14 }, { "by": 10, "edge": "redox", "key": "payments", "name": "Payments \u0026 pricing", "particle-health": 5, "redox": 15, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 4, "edge": "redox", "key": "maintenance", "name": "Maintenance \u0026 community", "particle-health": 27, "redox": 31, "weight": 7 }, { "by": 11, "edge": "redox", "key": "transparency", "name": "Transparency \u0026 trust", "particle-health": 48, "redox": 59, "weight": 7 } ], "summary": "Redox scores 58.3 (C) on agent readiness against Particle Health's 48.6 (D), and leads in 6 of 7 scored categories. Particle Health leads on schema \u0026 documentation. Both do patient record retrieval.", "verdicts": { "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.", "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/particle-health-vs-redox", "json": "https://www.anchorterminal.com/compare/particle-health-vs-redox.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/particle-health-vs-redox.md", "slim": "https://www.anchorterminal.com/compare/particle-health-vs-redox.min.md" }, "markdown": "Redox scores 58.3 (C) on agent readiness against Particle Health's 48.6 (D), and leads in 6 of 7 scored categories. Particle Health leads on schema \u0026 documentation. Both do patient record retrieval.\n\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- 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### 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- Schema \u0026 documentation, 69 against 56\n\nWatch for: Credentials come from a Particle representative, and the 'play for free' sign-up domain did not resolve\n\n### Redox (C)\n\nGood for: Health software vendors integrating with many hospital EHRs and networks, and integration teams who want an agent to manage Redox configuration.\n\nAhead on:\n- Reliability, 85 against 58\n- Security \u0026 auth, 78 against 57\n- Payments \u0026 pricing, 15 against 5\n- Transparency \u0026 trust, 59 against 48\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 | Particle Health | Redox | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 58 | 85 | Redox +27 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 69 | 56 | Particle Health +13 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 54 | Redox +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 57 | 78 | Redox +21 |\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) | 27 | 31 | Redox +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 48 | 59 | Redox +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **48.6 · D** | **58.3 · C** | |\n\n## Facts side by side\n\n| Fact | Particle Health | Redox |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Particle Health, Inc. | Redox, Inc. |\n| Hosted endpoint | no (local only) | `https://api.redoxengine.com/mcp` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth | OAuth |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under customer agreements. The public terms of use (effective 15 October 2020) cover the website only | 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| Terms last updated | 2020-10-15 | 2015-10-17 |\n| Privacy policy last updated | 2026-07-29 | 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 | not found in the text | 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\n## Verdicts\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**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### 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### 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, Particle Health or Redox?\n\nRedox scores 58.3 (C) on agent readiness against Particle Health's 48.6 (D), and leads in 6 of 7 scored categories. Particle Health leads on schema \u0026 documentation.\n\n### Do Particle Health and Redox need an API key?\n\nBoth use an OAuth sign-in.\n\n### Can an agent call Particle Health and Redox without installing anything?\n\nNo hosted endpoint is listed for Particle Health. Redox has a hosted endpoint at https://api.redoxengine.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/particle-health-vs-redox.json, and with the fewest tokens: https://www.anchorterminal.com/compare/particle-health-vs-redox.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"particle-health\", \"b\": \"redox\"}`. From a terminal: `anchor compare particle-health redox`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/particle-health.json and https://www.anchorterminal.com/api/v1/tools/redox.json\n\n## Other comparisons with Particle Health or Redox\n\n- [Aidbox vs Particle Health](https://www.anchorterminal.com/compare/aidbox-vs-particle-health.md)\n- [Aidbox vs Redox](https://www.anchorterminal.com/compare/aidbox-vs-redox.md)\n- [Medplum vs Particle Health](https://www.anchorterminal.com/compare/medplum-vs-particle-health.md)\n- [Medplum vs Redox](https://www.anchorterminal.com/compare/medplum-vs-redox.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- [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 Particle Health](https://www.anchorterminal.com/compare/1uphealth-vs-particle-health.md)\n- [1upHealth vs Redox](https://www.anchorterminal.com/compare/1uphealth-vs-redox.md)\n- [Health Gorilla vs Particle Health](https://www.anchorterminal.com/compare/health-gorilla-vs-particle-health.md)\n- [Health Gorilla vs Redox](https://www.anchorterminal.com/compare/health-gorilla-vs-redox.md)\n- [Medblocks vs Particle Health](https://www.anchorterminal.com/compare/medblocks-vs-particle-health.md)\n- [Medblocks vs Redox](https://www.anchorterminal.com/compare/medblocks-vs-redox.md)\n- [Metriport Medical API vs Particle Health](https://www.anchorterminal.com/compare/metriport-vs-particle-health.md)\n- [Metriport Medical API vs Redox](https://www.anchorterminal.com/compare/metriport-vs-redox.md)\n- [Particle Health vs Zus Health](https://www.anchorterminal.com/compare/particle-health-vs-zus-health.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": "Particle Health vs Redox", "url": "" } ], "description": "Redox scores 58.3 (C) to Particle Health's 48.6 (D) for patient record retrieval. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Particle Health D 48.6", "Redox C 58.3", "scores" ], "h1": "Particle Health vs Redox", "image": "https://www.anchorterminal.com/assets/og/compare-particle-health-vs-redox.png", "path": "/compare/particle-health-vs-redox", "published": "2026-10-01", "section": "tools", "title": "Particle Health vs Redox for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/particle-health-vs-redox" }, "tokens": { "markdown": 2200, "slim": 630 }, "version": 1 }