{ "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:53:19.028297263Z" }, "updatedAt": "2026-10-14T09:53:19.028297263Z" } }, "answer": "ROOK scores 54.9 (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": "rook", "name": "ROOK", "vendor": "Rookeries Development Corp.", "vendorUrl": "https://www.tryrook.io", "kind": "http-api", "category": "health-data", "summary": "ROOK Connect, from Rookeries Development Corp., collects health data from wearables and phone health stores, normalises it into sleep, physical and body summaries and events, and sends it by webhook or a REST API.", "url": "https://www.anchorterminal.com/tools/rook", "markdownUrl": "https://www.anchorterminal.com/tools/rook.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/rook.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/rook.json", "repo": "https://github.com/RookeriesDevelopment", "license": "Proprietary service under ROOK's Terms and Conditions for ROOK services", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "react-native-rook-sdk" }, { "registry": "npm", "name": "capacitor-rook-sdk" } ], "auth": "api-key", "authNotes": "A person registers an organisation in the ROOK Portal, which enables a Sandbox project, then generates a client UUID and secret key. The secret is shown once. Calls use HTTP Basic auth with the UUID as username and the secret as password. Production needs new credentials, an active plan and signed agreements. No scopes or key rotation were found. End users authorise each data source through ROOK's authoriser pages, the mobile SDKs or the ROOK App.", "pricing": "paid", "pricingNotes": "Core $399 a month for up to 750 active users, Core+ $999 for 5,000, Business $1,999 for 15,000, Enterprise custom. Add-ons cost $79 to $499 a month. A Sandbox is available before buying a plan. The standard term is 12 months with 30 days' notice to cancel (checked 2026-10-14).", "priceSummary": "$399 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.tryrook.io", "llmsTxt": "https://docs.tryrook.io/llms.txt", "openapi": "https://docs.tryrook.io/redocusaurus/plugin-redoc-0.yaml", "capabilities": [ "health.wearables", "health.consent", "health.fhir" ], "tags": [ "hosted", "wearables", "health-data", "api-key", "openapi", "llms-txt", "sandbox", "webhooks", "status-page", "hipaa" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 54.9, "grade": "C", "agentReady": false, "rank": 718, "ranked": true, "rankOf": 1076, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 49, "maintenance": 73, "payments": 25, "reliability": 75, "schema": 74, "security": 32, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Graded on the REST API. A public OpenAPI file, a free Sandbox from the self-serve portal, published plan prices and a dated changelog. Credentials are one client UUID and secret per environment with no scopes, 429 handling isn't documented, the API is meant for occasional queries rather than bulk reads, and no SOC 2 report or security contact was found.", "bestFor": "A wellness, insurance, corporate wellness or remote monitoring product that wants normalised wearable data pushed to its backend, with plan prices it can see up front.", "strengths": [ "OpenAPI 3.0.3 file with 29 operations and production and sandbox servers, linked from the API reference", "A self-serve portal enables a Sandbox on registration, and the pricing FAQ says it can be tested before buying a plan", "Plan prices are public, from $399 a month for 750 active users, with add-on prices listed", "Data webhooks carry an X-ROOK-HASH HMAC header and are retried on a published schedule", "Dated changelog with five entries between 25 August and 7 October 2026, and SDK LTS releases with a six-month support period" ], "weaknesses": [ "Credentials are one client UUID and secret per environment, sent by Basic auth, with no scopes or rotation documented", "Typical limits of 60 requests a minute and 10,000 a day vary by plan, and no 429 or Retry-After behaviour is documented", "No server-side SDK. The official SDKs are mobile libraries for iOS, Android, Flutter, React Native and Capacitor", "The services terms cite an SLA page that isn't linked or published, and no SOC 2 or ISO 27001 report was found", "A WAF blocks requests without a User-Agent header and parameters containing localhost or SQL-like text" ], "agentNotes": [ "Send HTTP Basic auth with client_uuid as the username and the secret key as the password, plus a User-Agent header, or the WAF returns 403", "Use https://api.rook-connect.review for Sandbox and https://api.rook-connect.com for production. Each has its own credentials", "Read health data from the data webhook. Use the API only for occasional queries, and stay under 60 requests a minute", "Deduplicate summaries on document_version and datetime. ROOK resends a summary with a higher document_version when it changes", "Call POST /api/v1/user_id/{user_id}/data_sources/revoke_auth to end a connection. Some providers take hours to stop sending data" ], "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": 54.9 } ], "editorialScores": { "ergonomics": 49, "maintenance": 73, "payments": 25, "reliability": 75, "schema": 74, "security": 32, "transparency": 52 }, "provenanceScore": 58 }, "connect": { "http": "curl https://api.rook-connect.review/api/v1/client/users/status \\\n -u \u003cclient_uuid\u003e:\u003csecret_key\u003e \\\n -H 'User-Agent: MyApp/1.0.0'" }, "letme": { "capability": "https://letme.dev/health.wearables", "tool": "https://letme.dev/rook" }, "area": "domain-data", "unitPrices": [ { "item": "Core plan, up to 750 active users", "unit": "month", "usd": 399, "note": "tryrook.io/pricing, 2026-10-14" }, { "item": "Business plan, up to 15,000 active users, all add-ons", "unit": "month", "usd": 1999, "note": "tryrook.io/pricing, 2026-10-14" } ], "provenance": { "legalEntity": "Rookeries Development Corp.", "domain": "tryrook.io", "domainRegistered": "", "endpointOnVendorDomain": false, "terms": "https://www.tryrook.io/terms-rook-connect/", "privacy": "https://www.tryrook.io/privacy-policy/", "statusPage": "https://rook.statuspage.io", "changelog": "https://rook.canny.io/changelog", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The Terms and Conditions for ROOK services (last updated August 2026) and the website terms (4 June 2026) name Rookeries Development Corp., 224 NE 59th St, Miami, FL 33137.", "The website terms forbid robots, spiders and page scraping to acquire, copy or monitor any part of the site. robots.txt on www.tryrook.io and docs.tryrook.io allows all paths, and we read public pages only.", "The API answers at api.rook-connect.com and api.rook-connect.review, which are not on tryrook.io.", "rookmotion.com, the domain in the founder's list, did not load (expired certificate). The current site is www.tryrook.io.", "www.tryrook.io/.well-known/security.txt returns 404." ], "score": 58 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/rook.json", "live": { "slug": "rook", "vendorStatus": { "page": "https://rook.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:53:23.529135186Z" }, "updatedAt": "2026-10-14T09:53:23.529135186Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Particle Health, Inc.", "b": "Rookeries Development Corp.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth", "b": "API key", "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 ROOK's Terms and Conditions for ROOK services", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-07", "name": "Last release" }, { "a": "2020-10-15", "b": "2026-08-01", "name": "Terms last updated" }, { "a": "2026-07-29", "b": "2026-05-28", "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": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "ROOK scores 54.9 (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 ROOK?" }, { "answer": "Particle Health uses an OAuth sign-in. ROOK needs an API key.", "question": "Do Particle Health and ROOK need an API key?" }, { "answer": "No hosted endpoint is listed for Particle Health. No hosted endpoint is listed for ROOK.", "question": "Can an agent call Particle Health and ROOK without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 57 against 32" ], "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, 75 against 58", "Schema \u0026 documentation, 74 against 69", "Payments \u0026 pricing, 25 against 5", "Maintenance \u0026 community, 73 against 27", "Transparency \u0026 trust, 55 against 48" ], "also": null, "goodFor": "A wellness, insurance, corporate wellness or remote monitoring product that wants normalised wearable data pushed to its backend, with plan prices it can see up front.", "slug": "rook", "watchFor": "Credentials are one client UUID and secret per environment, sent by Basic auth, with no scopes or rotation documented" } ], "job": { "capability": "health.fhir", "name": "FHIR servers" }, "others": [ { "json": "https://www.anchorterminal.com/compare/1uphealth-vs-rook.json", "title": "1upHealth vs ROOK", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-rook" }, { "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-rook.json", "title": "Aidbox vs ROOK", "url": "https://www.anchorterminal.com/compare/aidbox-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-rook.json", "title": "Health Gorilla vs ROOK", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-rook" }, { "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-rook.json", "title": "Medplum vs ROOK", "url": "https://www.anchorterminal.com/compare/medplum-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/metriport-vs-rook.json", "title": "Metriport Medical API vs ROOK", "url": "https://www.anchorterminal.com/compare/metriport-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/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/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-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-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" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-rook.json", "title": "Medblocks vs ROOK", "url": "https://www.anchorterminal.com/compare/medblocks-vs-rook" }, { "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/rook-vs-terra.json", "title": "ROOK vs Terra API", "url": "https://www.anchorterminal.com/compare/rook-vs-terra" }, { "json": "https://www.anchorterminal.com/compare/rook-vs-validic.json", "title": "ROOK vs Validic Inform", "url": "https://www.anchorterminal.com/compare/rook-vs-validic" } ], "scores": [ { "by": 17, "edge": "rook", "key": "reliability", "name": "Reliability", "particle-health": 58, "rook": 75, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 5, "edge": "rook", "key": "schema", "name": "Schema \u0026 documentation", "particle-health": 69, "rook": 74, "weight": 13 }, { "by": 4, "edge": "particle-health", "key": "ergonomics", "name": "Agent ergonomics", "particle-health": 53, "rook": 49, "weight": 13 }, { "by": 25, "edge": "particle-health", "key": "security", "name": "Security \u0026 auth", "particle-health": 57, "rook": 32, "weight": 14 }, { "by": 20, "edge": "rook", "key": "payments", "name": "Payments \u0026 pricing", "particle-health": 5, "rook": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 46, "edge": "rook", "key": "maintenance", "name": "Maintenance \u0026 community", "particle-health": 27, "rook": 73, "weight": 7 }, { "by": 7, "edge": "rook", "key": "transparency", "name": "Transparency \u0026 trust", "particle-health": 48, "rook": 55, "weight": 7 } ], "summary": "ROOK scores 54.9 (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 fhir servers.", "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.", "rook": "Graded on the REST API. A public OpenAPI file, a free Sandbox from the self-serve portal, published plan prices and a dated changelog. Credentials are one client UUID and secret per environment with no scopes, 429 handling isn't documented, the API is meant for occasional queries rather than bulk reads, and no SOC 2 report or security contact was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/particle-health-vs-rook", "json": "https://www.anchorterminal.com/compare/particle-health-vs-rook.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/particle-health-vs-rook.md", "slim": "https://www.anchorterminal.com/compare/particle-health-vs-rook.min.md" }, "markdown": "ROOK scores 54.9 (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 fhir servers.\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- ROOK: grade C, 54.9/100, rank #718 of 1076. Markdown https://www.anchorterminal.com/tools/rook.md · JSON https://www.anchorterminal.com/api/v1/tools/rook.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 32\n\nWatch for: Credentials come from a Particle representative, and the 'play for free' sign-up domain did not resolve\n\n### ROOK (C)\n\nGood for: A wellness, insurance, corporate wellness or remote monitoring product that wants normalised wearable data pushed to its backend, with plan prices it can see up front.\n\nAhead on:\n- Reliability, 75 against 58\n- Schema \u0026 documentation, 74 against 69\n- Payments \u0026 pricing, 25 against 5\n- Maintenance \u0026 community, 73 against 27\n- Transparency \u0026 trust, 55 against 48\n\nWatch for: Credentials are one client UUID and secret per environment, sent by Basic auth, with no scopes or rotation documented\n\n\n## Score by category\n\n| Category | Weight | Particle Health | ROOK | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 58 | 75 | ROOK +17 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 69 | 74 | ROOK +5 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 49 | Particle Health +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 57 | 32 | Particle Health +25 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 5 | 25 | ROOK +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 27 | 73 | ROOK +46 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 48 | 55 | ROOK +7 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **48.6 · D** | **54.9 · C** | |\n\n## Facts side by side\n\n| Fact | Particle Health | ROOK |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Particle Health, Inc. | Rookeries Development Corp. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | OAuth | API key |\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 ROOK's Terms and Conditions for ROOK services |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-10-07 |\n| Terms last updated | 2020-10-15 | 2026-08-01 |\n| Privacy policy last updated | 2026-07-29 | 2026-05-28 |\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 | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | yes |\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**ROOK.** Graded on the REST API. A public OpenAPI file, a free Sandbox from the self-serve portal, published plan prices and a dated changelog. Credentials are one client UUID and secret per environment with no scopes, 429 handling isn't documented, the API is meant for occasional queries rather than bulk reads, and no SOC 2 report or security contact was found.\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### ROOK\n\n1. Send HTTP Basic auth with client_uuid as the username and the secret key as the password, plus a User-Agent header, or the WAF returns 403\n2. Use https://api.rook-connect.review for Sandbox and https://api.rook-connect.com for production. Each has its own credentials\n3. Read health data from the data webhook. Use the API only for occasional queries, and stay under 60 requests a minute\n4. Deduplicate summaries on document_version and datetime. ROOK resends a summary with a higher document_version when it changes\n5. Call POST /api/v1/user_id/{user_id}/data_sources/revoke_auth to end a connection. Some providers take hours to stop sending data\n\n## Questions\n\n### Which is better for AI agents, Particle Health or ROOK?\n\nROOK scores 54.9 (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 ROOK need an API key?\n\nParticle Health uses an OAuth sign-in. ROOK needs an API key.\n\n### Can an agent call Particle Health and ROOK without installing anything?\n\nNo hosted endpoint is listed for Particle Health. No hosted endpoint is listed for ROOK.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/particle-health-vs-rook.json, and with the fewest tokens: https://www.anchorterminal.com/compare/particle-health-vs-rook.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"particle-health\", \"b\": \"rook\"}`. From a terminal: `anchor compare particle-health rook`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/particle-health.json and https://www.anchorterminal.com/api/v1/tools/rook.json\n\n## Other comparisons with Particle Health or ROOK\n\n- [1upHealth vs ROOK](https://www.anchorterminal.com/compare/1uphealth-vs-rook.md)\n- [Aidbox vs Particle Health](https://www.anchorterminal.com/compare/aidbox-vs-particle-health.md)\n- [Aidbox vs ROOK](https://www.anchorterminal.com/compare/aidbox-vs-rook.md)\n- [Health Gorilla vs ROOK](https://www.anchorterminal.com/compare/health-gorilla-vs-rook.md)\n- [Medplum vs Particle Health](https://www.anchorterminal.com/compare/medplum-vs-particle-health.md)\n- [Medplum vs ROOK](https://www.anchorterminal.com/compare/medplum-vs-rook.md)\n- [Metriport Medical API vs ROOK](https://www.anchorterminal.com/compare/metriport-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- [1upHealth vs Particle Health](https://www.anchorterminal.com/compare/1uphealth-vs-particle-health.md)\n- [Health Gorilla vs Particle Health](https://www.anchorterminal.com/compare/health-gorilla-vs-particle-health.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- [Medblocks vs ROOK](https://www.anchorterminal.com/compare/medblocks-vs-rook.md)\n- [ROOK vs Zus Health](https://www.anchorterminal.com/compare/rook-vs-zus-health.md)\n- [ROOK vs Terra API](https://www.anchorterminal.com/compare/rook-vs-terra.md)\n- [ROOK vs Validic Inform](https://www.anchorterminal.com/compare/rook-vs-validic.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-14", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Particle Health vs ROOK", "url": "" } ], "description": "ROOK scores 54.9 (C) to Particle Health's 48.6 (D) for fhir servers. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Particle Health D 48.6", "ROOK C 54.9", "scores" ], "h1": "Particle Health vs ROOK", "image": "https://www.anchorterminal.com/assets/og/compare-particle-health-vs-rook.png", "path": "/compare/particle-health-vs-rook", "published": "2026-10-01", "section": "tools", "title": "Particle Health vs ROOK for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/particle-health-vs-rook" }, "tokens": { "markdown": 2250, "slim": 630 }, "version": 1 }