{ "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": 879, "ranked": true, "rankOf": 1094, "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-15T11:54:33.914475789Z" }, "securityTxt": { "url": "https://particlehealth.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-14T15:46:25.88151651Z" }, "llmsTxt": { "url": "https://docs.particlehealth.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-14T14:14:50.078417651Z" }, "pages": [ { "url": "https://particlehealth.com/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-14T21:04:30.890335572Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1227dd704e4a" }, { "url": "https://particlehealth.com/terms-of-use", "kind": "terms", "status": 304, "checkedAt": "2026-10-14T21:04:32.939547327Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1b3d864c764f" } ], "updatedAt": "2026-10-15T11:54:33.914475789Z" } }, "answer": "Zus Health scores 56.6 (C) on agent readiness against Particle Health's 48.6 (D), and leads in 5 of 7 scored categories. Particle Health leads on security \u0026 auth.", "b": { "slug": "zus-health", "name": "Zus Health", "vendor": "Zus Health, Inc.", "vendorUrl": "https://www.zushealth.com", "kind": "http-api", "category": "health-data", "summary": "Zus Health assembles a patient's history from CommonWell, Carequality, Surescripts, Quest and ADT networks into the Zus Aggregated Profile, and exposes it through FHIR R4 REST, GraphQL and webhook APIs for care organisations it onboards.", "url": "https://www.anchorterminal.com/tools/zus-health", "markdownUrl": "https://www.anchorterminal.com/tools/zus-health.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zus-health.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zus-health.json", "license": "Proprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum", "transports": [ "http" ], "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 bearer tokens valid for one hour. Backend systems use machine-to-machine App Clients created in the Zus app or through the Auth Service API, limited to 200 token requests an hour per client. Apps can exchange an OIDC ID token from their own identity provider for a Zus token, and integration App Clients with the Builder Data Integration role can fetch tokens for users through the proxy-token endpoint. Accounts are provisioned by Zus, with an initial admin per customer.", "pricing": "paid", "pricingNotes": "No public prices. The Builder Terms set fees in an executed Order Form or pricing list, invoiced monthly. A developer sandbox is requested through a Google Form on the docs site, 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 or the Builder Terms (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.zushealth.com", "llmsTxt": "https://docs.zushealth.com/llms.txt", "capabilities": [ "health.records", "health.fhir", "health.ehr", "health.consent" ], "tags": [ "hosted", "health-records", "fhir", "graphql", "oauth", "llms-txt", "webhooks", "status-page", "sla", "sales-led" ], "lastRelease": "2026-10-14", "graded": true, "anchor": { "graded": true, "score": 56.6, "grade": "C", "agentReady": false, "rank": 674, "ranked": true, "rankOf": 1094, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 64, "payments": 5, "reliability": 66, "schema": 77, "security": 49, "transparency": 59 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "FHIR R4 over an aggregated patient profile drawn from CommonWell, Carequality, Surescripts, Quest and ADT networks, with published rate limits, a 99.5 per cent SLA and a dated changelog. Accounts and sandboxes are provisioned by Zus on request, with no public prices, no named security certification and no SDK.", "bestFor": "US care organisations and digital health builders that want a shared, continuously refreshed patient profile in FHIR with EHR embedding.", "strengths": [ "One profile per patient from EHR, pharmacy, ADT and lab networks, shared across Zus customers treating the same patient", "Rate limits with numbers and a published 99.5 per cent SLA with credits", "Conditional writes by identifier and `Zus-If-Match` version checks for safe retries", "Dated changelog that announces changes ahead, such as the proxy-token role change on 14 October 2026" ], "weaknesses": [ "No public prices, and the sandbox is requested through a Google Form", "Four major incidents on the status page between 27 July and 13 August 2026", "No named security certification, security.txt or bug bounty", "The GraphQL API is beta and no official SDK exists" ], "agentNotes": [ "Cache the access token for its hour. More than 200 token requests an hour per App Client returns 429", "Request Patient History at most once per patient per 24 hours, and poll the job status endpoint", "Use conditional create by identifier so a retried write doesn't duplicate a resource", "Send `Zus-If-Match` with the resource's ETag on PUT and PATCH", "Set `_count` up to 500 on searches, since the default page is 10" ], "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": 56.6 } ], "editorialScores": { "ergonomics": 67, "maintenance": 64, "payments": 5, "reliability": 66, "schema": 77, "security": 49, "transparency": 46 }, "provenanceScore": 71 }, "connect": { "http": "GET https://api.sandbox.zusapi.com/fhir/Patient?_count=50\nAuthorization: Bearer \u003caccess-token\u003e" }, "letme": { "capability": "https://letme.dev/health.records", "tool": "https://letme.dev/zus-health" }, "area": "domain-data", "provenance": { "legalEntity": "Zus Health, Inc.", "domain": "zushealth.com", "domainRegistered": "2012-02-25", "endpointOnVendorDomain": false, "terms": "https://www.zushealth.com/builder-terms-of-service", "privacy": "https://www.zushealth.com/privacy-policy", "statusPage": "https://status.zusapi.com", "changelog": "https://docs.zushealth.com/changelog", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The APIs answer on zusapi.com, a separate domain from zushealth.com.", "The Builder Terms (last updated 11 March 2025) put term changes into effect 30 days after posting and BAA changes after 90 days. The Developer Sandbox Terms (22 January 2024) limit the sandbox to test data. The website lists 1 Lincoln Street, Suite 2900, Boston, MA 02111.", "The privacy policy (last updated 24 June 2026) covers the website only and names Google Analytics.", "The Builder Security Policy (11 March 2025) names no certification and makes a summary of an annual third-party audit available on request.", "www.zushealth.com/.well-known/security.txt returns 404.", "RDAP gives zushealth.com a registration date of 2012-02-25." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/zus-health.json", "live": { "slug": "zus-health", "vendorStatus": { "page": "https://status.zusapi.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-15T10:07:56.30662534Z" }, "securityTxt": { "url": "https://zushealth.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-14T15:47:47.306441372Z" }, "llmsTxt": { "url": "https://docs.zushealth.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-14T14:15:29.396228852Z" }, "pages": [ { "url": "https://docs.zushealth.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-14T21:00:01.505614661Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9349ea051538" }, { "url": "https://www.zushealth.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-14T21:19:34.184342833Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "cd627e540dc7" }, { "url": "https://www.zushealth.com/builder-terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-10-14T21:19:32.098315146Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "64849d2141d4" } ], "updatedAt": "2026-10-15T10:07:56.30662534Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Particle Health, Inc.", "b": "Zus Health, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "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 the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-14", "name": "Last release" }, { "a": "2020-10-15", "b": "2025-03-11", "name": "Terms last updated" }, { "a": "2026-07-29", "b": "2026-06-24", "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": "Zus Health scores 56.6 (C) on agent readiness against Particle Health's 48.6 (D), and leads in 5 of 7 scored categories. Particle Health leads on security \u0026 auth.", "question": "Which is better for AI agents, Particle Health or Zus Health?" }, { "answer": "Both use an OAuth sign-in.", "question": "Do Particle Health and Zus Health need an API key?" }, { "answer": "No hosted endpoint is listed for Particle Health. No hosted endpoint is listed for Zus Health.", "question": "Can an agent call Particle Health and Zus Health without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 57 against 49" ], "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, 66 against 58", "Schema \u0026 documentation, 77 against 69", "Agent ergonomics, 67 against 53", "Maintenance \u0026 community, 64 against 27", "Transparency \u0026 trust, 59 against 48" ], "also": null, "goodFor": "US care organisations and digital health builders that want a shared, continuously refreshed patient profile in FHIR with EHR embedding.", "slug": "zus-health", "watchFor": "No public prices, and the sandbox is requested through a Google Form" } ], "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-zus-health.json", "title": "Aidbox vs Zus Health", "url": "https://www.anchorterminal.com/compare/aidbox-vs-zus-health" }, { "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-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-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-zus-health.json", "title": "1upHealth vs Zus Health", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-particle-health.json", "title": "Health Gorilla vs Particle Health", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-particle-health" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-zus-health.json", "title": "Health Gorilla vs Zus Health", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-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-zus-health.json", "title": "Medblocks vs Zus Health", "url": "https://www.anchorterminal.com/compare/medblocks-vs-zus-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/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/rook-vs-zus-health.json", "title": "ROOK vs Zus Health", "url": "https://www.anchorterminal.com/compare/rook-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/terra-vs-zus-health.json", "title": "Terra API vs Zus Health", "url": "https://www.anchorterminal.com/compare/terra-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/validic-vs-zus-health.json", "title": "Validic Inform vs Zus Health", "url": "https://www.anchorterminal.com/compare/validic-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": 8, "edge": "zus-health", "key": "reliability", "name": "Reliability", "particle-health": 58, "weight": 16, "zus-health": 66 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "zus-health", "key": "schema", "name": "Schema \u0026 documentation", "particle-health": 69, "weight": 13, "zus-health": 77 }, { "by": 14, "edge": "zus-health", "key": "ergonomics", "name": "Agent ergonomics", "particle-health": 53, "weight": 13, "zus-health": 67 }, { "by": 8, "edge": "particle-health", "key": "security", "name": "Security \u0026 auth", "particle-health": 57, "weight": 14, "zus-health": 49 }, { "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "particle-health": 5, "weight": 10, "zus-health": 5 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 37, "edge": "zus-health", "key": "maintenance", "name": "Maintenance \u0026 community", "particle-health": 27, "weight": 7, "zus-health": 64 }, { "by": 11, "edge": "zus-health", "key": "transparency", "name": "Transparency \u0026 trust", "particle-health": 48, "weight": 7, "zus-health": 59 } ], "summary": "Zus Health scores 56.6 (C) on agent readiness against Particle Health's 48.6 (D), and leads in 5 of 7 scored categories. Particle Health leads on security \u0026 auth. 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.", "zus-health": "FHIR R4 over an aggregated patient profile drawn from CommonWell, Carequality, Surescripts, Quest and ADT networks, with published rate limits, a 99.5 per cent SLA and a dated changelog. Accounts and sandboxes are provisioned by Zus on request, with no public prices, no named security certification and no SDK." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/particle-health-vs-zus-health", "json": "https://www.anchorterminal.com/compare/particle-health-vs-zus-health.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/particle-health-vs-zus-health.md", "slim": "https://www.anchorterminal.com/compare/particle-health-vs-zus-health.min.md" }, "markdown": "Zus Health scores 56.6 (C) on agent readiness against Particle Health's 48.6 (D), and leads in 5 of 7 scored categories. Particle Health leads on security \u0026 auth. Both do patient record retrieval.\n\n- Particle Health: grade D, 48.6/100, rank #879 of 1094. Markdown https://www.anchorterminal.com/tools/particle-health.md · JSON https://www.anchorterminal.com/api/v1/tools/particle-health.json\n- Zus Health: grade C, 56.6/100, rank #674 of 1094. Markdown https://www.anchorterminal.com/tools/zus-health.md · JSON https://www.anchorterminal.com/api/v1/tools/zus-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### 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- Security \u0026 auth, 57 against 49\n\nWatch for: Credentials come from a Particle representative, and the 'play for free' sign-up domain did not resolve\n\n### Zus Health (C)\n\nGood for: US care organisations and digital health builders that want a shared, continuously refreshed patient profile in FHIR with EHR embedding.\n\nAhead on:\n- Reliability, 66 against 58\n- Schema \u0026 documentation, 77 against 69\n- Agent ergonomics, 67 against 53\n- Maintenance \u0026 community, 64 against 27\n- Transparency \u0026 trust, 59 against 48\n\nWatch for: No public prices, and the sandbox is requested through a Google Form\n\n\n## Score by category\n\n| Category | Weight | Particle Health | Zus Health | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 58 | 66 | Zus Health +8 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 69 | 77 | Zus Health +8 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 67 | Zus Health +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 57 | 49 | Particle Health +8 |\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) | 27 | 64 | Zus Health +37 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 48 | 59 | Zus Health +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **48.6 · D** | **56.6 · C** | |\n\n## Facts side by side\n\n| Fact | Particle Health | Zus Health |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Particle Health, Inc. | Zus Health, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\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 the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-10-14 |\n| Terms last updated | 2020-10-15 | 2025-03-11 |\n| Privacy policy last updated | 2026-07-29 | 2026-06-24 |\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**Zus Health.** FHIR R4 over an aggregated patient profile drawn from CommonWell, Carequality, Surescripts, Quest and ADT networks, with published rate limits, a 99.5 per cent SLA and a dated changelog. Accounts and sandboxes are provisioned by Zus on request, with no public prices, no named security certification and no SDK.\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### Zus Health\n\n1. Cache the access token for its hour. More than 200 token requests an hour per App Client returns 429\n2. Request Patient History at most once per patient per 24 hours, and poll the job status endpoint\n3. Use conditional create by identifier so a retried write doesn't duplicate a resource\n4. Send `Zus-If-Match` with the resource's ETag on PUT and PATCH\n5. Set `_count` up to 500 on searches, since the default page is 10\n\n## Questions\n\n### Which is better for AI agents, Particle Health or Zus Health?\n\nZus Health scores 56.6 (C) on agent readiness against Particle Health's 48.6 (D), and leads in 5 of 7 scored categories. Particle Health leads on security \u0026 auth.\n\n### Do Particle Health and Zus Health need an API key?\n\nBoth use an OAuth sign-in.\n\n### Can an agent call Particle Health and Zus Health without installing anything?\n\nNo hosted endpoint is listed for Particle Health. No hosted endpoint is listed for Zus Health.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/particle-health-vs-zus-health.json, and with the fewest tokens: https://www.anchorterminal.com/compare/particle-health-vs-zus-health.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"particle-health\", \"b\": \"zus-health\"}`. From a terminal: `anchor compare particle-health zus-health`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/particle-health.json and https://www.anchorterminal.com/api/v1/tools/zus-health.json\n\n## Other comparisons with Particle Health or Zus Health\n\n- [Aidbox vs Particle Health](https://www.anchorterminal.com/compare/aidbox-vs-particle-health.md)\n- [Aidbox vs Zus Health](https://www.anchorterminal.com/compare/aidbox-vs-zus-health.md)\n- [Medplum vs Particle Health](https://www.anchorterminal.com/compare/medplum-vs-particle-health.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 Particle Health](https://www.anchorterminal.com/compare/1uphealth-vs-particle-health.md)\n- [1upHealth vs Zus Health](https://www.anchorterminal.com/compare/1uphealth-vs-zus-health.md)\n- [Health Gorilla vs Particle Health](https://www.anchorterminal.com/compare/health-gorilla-vs-particle-health.md)\n- [Health Gorilla vs Zus Health](https://www.anchorterminal.com/compare/health-gorilla-vs-zus-health.md)\n- [Medblocks vs Particle Health](https://www.anchorterminal.com/compare/medblocks-vs-particle-health.md)\n- [Medblocks vs Zus Health](https://www.anchorterminal.com/compare/medblocks-vs-zus-health.md)\n- [Metriport Medical API vs Particle Health](https://www.anchorterminal.com/compare/metriport-vs-particle-health.md)\n- [Metriport Medical API vs Zus Health](https://www.anchorterminal.com/compare/metriport-vs-zus-health.md)\n- [Particle Health vs Redox](https://www.anchorterminal.com/compare/particle-health-vs-redox.md)\n- [ROOK vs Zus Health](https://www.anchorterminal.com/compare/rook-vs-zus-health.md)\n- [Terra API vs Zus Health](https://www.anchorterminal.com/compare/terra-vs-zus-health.md)\n- [Validic Inform vs Zus Health](https://www.anchorterminal.com/compare/validic-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)", "attributionRequired": true, "credit": "CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author.", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-15", "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", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Particle Health vs Zus Health", "url": "" } ], "description": "Zus Health scores 56.6 (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", "Zus Health C 56.6", "scores" ], "h1": "Particle Health vs Zus Health", "image": "https://www.anchorterminal.com/assets/og/compare-particle-health-vs-zus-health.png", "path": "/compare/particle-health-vs-zus-health", "published": "2026-10-01", "section": "tools", "title": "Particle Health vs Zus Health for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-15", "url": "https://www.anchorterminal.com/compare/particle-health-vs-zus-health" }, "tokens": { "markdown": 2250, "slim": 630 }, "version": 1 }