{
  "data": {
    "similar": [
      {
        "grade": "B",
        "json": "https://www.anchorterminal.com/tools/medplum.json",
        "name": "Medplum",
        "score": 68.7,
        "shared": [
          "health.fhir",
          "health.records"
        ],
        "slug": "medplum"
      },
      {
        "grade": "B",
        "json": "https://www.anchorterminal.com/tools/aidbox.json",
        "name": "Aidbox",
        "score": 64.2,
        "shared": [
          "health.fhir",
          "health.records"
        ],
        "slug": "aidbox"
      },
      {
        "grade": "C",
        "json": "https://www.anchorterminal.com/tools/health-gorilla.json",
        "name": "Health Gorilla",
        "score": 59.3,
        "shared": [
          "health.records",
          "health.fhir"
        ],
        "slug": "health-gorilla"
      },
      {
        "grade": "C",
        "json": "https://www.anchorterminal.com/tools/redox.json",
        "name": "Redox",
        "score": 58.3,
        "shared": [
          "health.fhir",
          "health.records"
        ],
        "slug": "redox"
      },
      {
        "grade": "C",
        "json": "https://www.anchorterminal.com/tools/zus-health.json",
        "name": "Zus Health",
        "score": 56.6,
        "shared": [
          "health.records",
          "health.fhir"
        ],
        "slug": "zus-health"
      },
      {
        "grade": "D",
        "json": "https://www.anchorterminal.com/tools/medblocks.json",
        "name": "Medblocks",
        "score": 52.7,
        "shared": [
          "health.records",
          "health.fhir"
        ],
        "slug": "medblocks"
      }
    ],
    "tool": {
      "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"
        ],
        "breakdown": [
          {
            "key": "reliability",
            "name": "Reliability",
            "weight": 16,
            "effectiveWeight": 20,
            "score": 58,
            "points": 11.6,
            "reason": "Read with the hosted lines. status.particlehealth.com on Statuspage with 7 components and history (20). In the last 90 days, CommonWell traffic was disrupted for about five and a half hours on 5 August 2026, marked critical, and a Google Cloud zone outage on 1 September raised risk with no impact recorded. We read the first as a network-side outage, as for the other network listings (15 of 30). Rate limits exist per project with no numbers, apart from the sandbox's 500 queries a day (5 of 15). 429 with a backoff recommendation, no Retry-After or idempotency guidance (8 of 15). No SLA found in public (0). The v2 APIs are generally available (10)."
          },
          {
            "key": "performance",
            "name": "Performance",
            "weight": 10,
            "effectiveWeight": 0,
            "pending": true,
            "points": 0,
            "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes."
          },
          {
            "key": "schema",
            "name": "Schema \u0026 documentation",
            "weight": 13,
            "effectiveWeight": 16.25,
            "score": 69,
            "points": 11.21,
            "reason": "OpenAPI fragments on each reference page, with no single specification file found (18 of 25). llms.txt and Markdown pages (10). A developer guide by path (Workbench, Signal) and global conventions for IDs, auth and pagination (14 of 20). Typed inputs in the fragments (11 of 15). A Postman collection and an error code table with context (11 of 15). Versioned /api/v1 and /api/v2 paths and legacy flows marked, but no changelog, which returns 404 (5 of 15)."
          },
          {
            "key": "ergonomics",
            "name": "Agent ergonomics",
            "weight": 13,
            "effectiveWeight": 16.25,
            "score": 53,
            "points": 8.61,
            "reason": "FHIR by resource type or ID, flat data filtered by domain, and Snapshot AI summaries where enabled (17 of 25). Continuation tokens and filters (16 of 20). Standard HTTP codes with some context (12 of 20). No idempotency keys or safe-retry guidance (3 of 20). No official SDK (5 of 15)."
          },
          {
            "key": "security",
            "name": "Security \u0026 auth",
            "weight": 14,
            "effectiveWeight": 17.5,
            "score": 57,
            "points": 9.98,
            "reason": "OAuth 2.0 client credentials with a mandatory project scope, 60-minute tokens, rotation that expires old credentials, and IAM roles on service accounts (27 of 30). Project-scoped tokens, roles beyond owner on request, purpose-of-use rules and a delegation of authority policy, with deletes allowed and no confirmation step (13 of 20). Records and AI summaries from outside organisations, with no prompt-injection guidance (3 of 15). No audit log for operators found (2 of 15). HITRUST and SOC 2 claimed for the API platform, a vulnerability submission form, no bug bounty or security.txt (12 of 20)."
          },
          {
            "key": "payments",
            "name": "Payments \u0026 pricing",
            "weight": 10,
            "effectiveWeight": 12.5,
            "score": 5,
            "points": 0.63,
            "reason": "Read with the hosted rubric. No x402, MPP or L402 (0). No published prices (0). A sandbox with synthetic patients exists, but credentials come from a representative and the free sign-up link did not resolve (5 of 20). A person must be provisioned by Particle (0)."
          },
          {
            "key": "tasks",
            "name": "Task success",
            "weight": 10,
            "effectiveWeight": 0,
            "pending": true,
            "points": 0,
            "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored."
          },
          {
            "key": "maintenance",
            "name": "Maintenance \u0026 community",
            "weight": 7,
            "effectiveWeight": 8.75,
            "score": 27,
            "points": 2.36,
            "reason": "No dated release was found. Docs pages were updated on 13 October 2026, and v2 subscription endpoints sit beside v1, which we read as recent change without a release record (20 of 30). No changelog (0). Support through a representative, with no public record (5 of 15). No official SDK found (0 of 15). A maintained Postman collection (2 of 10)."
          },
          {
            "key": "transparency",
            "name": "Transparency \u0026 trust",
            "weight": 7,
            "effectiveWeight": 8.75,
            "score": 48,
            "points": 4.2,
            "note": "editorial 27, provenance 69",
            "reason": "Closed service. The public terms date from 2020 and cover only the website, and no developer or API terms were found (10 of 30). The privacy policy (July 2026) covers the site only and keeps de-identified aggregate data, with no retention periods or public DPA (8 of 30). Legacy flows are labelled as supported for existing customers, with no dates (5 of 20). Google Cloud is named as the platform, with no sub-processor list or regions (4 of 20)."
          }
        ],
        "assessment": {
          "date": "2026-10-14",
          "basis": "public evidence",
          "confidence": "medium",
          "notes": {
            "ergonomics": "FHIR by resource type or ID, flat data filtered by domain, and Snapshot AI summaries where enabled (17 of 25). Continuation tokens and filters (16 of 20). Standard HTTP codes with some context (12 of 20). No idempotency keys or safe-retry guidance (3 of 20). No official SDK (5 of 15).",
            "maintenance": "No dated release was found. Docs pages were updated on 13 October 2026, and v2 subscription endpoints sit beside v1, which we read as recent change without a release record (20 of 30). No changelog (0). Support through a representative, with no public record (5 of 15). No official SDK found (0 of 15). A maintained Postman collection (2 of 10).",
            "payments": "Read with the hosted rubric. No x402, MPP or L402 (0). No published prices (0). A sandbox with synthetic patients exists, but credentials come from a representative and the free sign-up link did not resolve (5 of 20). A person must be provisioned by Particle (0).",
            "reliability": "Read with the hosted lines. status.particlehealth.com on Statuspage with 7 components and history (20). In the last 90 days, CommonWell traffic was disrupted for about five and a half hours on 5 August 2026, marked critical, and a Google Cloud zone outage on 1 September raised risk with no impact recorded. We read the first as a network-side outage, as for the other network listings (15 of 30). Rate limits exist per project with no numbers, apart from the sandbox's 500 queries a day (5 of 15). 429 with a backoff recommendation, no Retry-After or idempotency guidance (8 of 15). No SLA found in public (0). The v2 APIs are generally available (10).",
            "schema": "OpenAPI fragments on each reference page, with no single specification file found (18 of 25). llms.txt and Markdown pages (10). A developer guide by path (Workbench, Signal) and global conventions for IDs, auth and pagination (14 of 20). Typed inputs in the fragments (11 of 15). A Postman collection and an error code table with context (11 of 15). Versioned /api/v1 and /api/v2 paths and legacy flows marked, but no changelog, which returns 404 (5 of 15).",
            "security": "OAuth 2.0 client credentials with a mandatory project scope, 60-minute tokens, rotation that expires old credentials, and IAM roles on service accounts (27 of 30). Project-scoped tokens, roles beyond owner on request, purpose-of-use rules and a delegation of authority policy, with deletes allowed and no confirmation step (13 of 20). Records and AI summaries from outside organisations, with no prompt-injection guidance (3 of 15). No audit log for operators found (2 of 15). HITRUST and SOC 2 claimed for the API platform, a vulnerability submission form, no bug bounty or security.txt (12 of 20).",
            "transparency": "Closed service. The public terms date from 2020 and cover only the website, and no developer or API terms were found (10 of 30). The privacy policy (July 2026) covers the site only and keeps de-identified aggregate data, with no retention periods or public DPA (8 of 30). Legacy flows are labelled as supported for existing customers, with no dates (5 of 20). Google Cloud is named as the platform, with no sub-processor list or regions (4 of 20)."
          },
          "sources": [
            {
              "what": "documentation index",
              "url": "https://docs.particlehealth.com/llms.txt",
              "seen": "2026-10-14"
            },
            {
              "what": "getting started for developers",
              "url": "https://docs.particlehealth.com/docs/getting-started-for-developers.md",
              "seen": "2026-10-14"
            },
            {
              "what": "auth and keys",
              "url": "https://docs.particlehealth.com/docs/auth-and-keys.md",
              "seen": "2026-10-14"
            },
            {
              "what": "rate limiting",
              "url": "https://docs.particlehealth.com/docs/rate-limiting-and-quotas.md",
              "seen": "2026-10-14"
            },
            {
              "what": "sandbox",
              "url": "https://docs.particlehealth.com/docs/test-patient-sandbox.md",
              "seen": "2026-10-14"
            },
            {
              "what": "API getting started",
              "url": "https://docs.particlehealth.com/reference/getting-started.md",
              "seen": "2026-10-14"
            },
            {
              "what": "handling errors",
              "url": "https://docs.particlehealth.com/reference/handling-errors.md",
              "seen": "2026-10-14"
            },
            {
              "what": "developers page",
              "url": "https://particlehealth.com/developers",
              "seen": "2026-10-14"
            },
            {
              "what": "status incidents",
              "url": "https://status.particlehealth.com/api/v2/incidents.json",
              "seen": "2026-10-14"
            },
            {
              "what": "security",
              "url": "https://particlehealth.com/security",
              "seen": "2026-10-14"
            },
            {
              "what": "terms of use",
              "url": "https://particlehealth.com/terms-of-use",
              "seen": "2026-10-14"
            },
            {
              "what": "privacy policy",
              "url": "https://particlehealth.com/privacy-policy",
              "seen": "2026-10-14"
            }
          ],
          "openQuestions": [
            "portal.particlehealth.com, the target of the 'play for free' link, had no DNS record on 14 October 2026, so the free route could not be checked",
            "Production base URL not confirmed in the pages read, which show the sandbox host",
            "No developer terms, SLA or DPA were found in public"
          ]
        },
        "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"
      },
      "notable": [
        "The v2 flow registers a patient, starts a query, polls its status and reads FHIR R4B Bundles, flat datasets or C-CDA files (https://docs.particlehealth.com/docs/getting-started-for-developers.md)",
        "Tokens are scoped to a single project and expire after 60 minutes (https://docs.particlehealth.com/docs/auth-and-keys.md)",
        "Rate limits are set per project and vary with system load, with 429 returned and backoff recommended, and no numbers published (https://docs.particlehealth.com/docs/rate-limiting-and-quotas.md)",
        "The sandbox at https://sandbox.particlehealth.com holds synthetic patients and allows 500 queries per organisation a day (https://docs.particlehealth.com/docs/test-patient-sandbox.md)",
        "The 'play for free' link on the developers page points to portal.particlehealth.com, which had no DNS record on 14 October 2026 (https://particlehealth.com/developers)",
        "status.particlehealth.com lists a CommonWell disruption of about five and a half hours on 5 August 2026, marked critical (https://status.particlehealth.com/api/v2/incidents.json)"
      ],
      "area": "domain-data",
      "details": [
        {
          "label": "Endpoints",
          "value": "Sandbox https://sandbox.particlehealth.com, API paths under /api/v1 and /api/v2"
        },
        {
          "label": "Networks",
          "value": "Carequality, CommonWell, eHealth Exchange, Healthix and Manifest MedEx, and Surescripts for medication data"
        },
        {
          "label": "Data out",
          "value": "FHIR R4B Bundles (all resources or by type), flat datasets by domain, C-CDA zip files, HL7v2 messages, Snapshot AI summaries and a patient provider map"
        },
        {
          "label": "Products",
          "value": "Workbench (on-demand queries), Signal (subscriptions and webhook alerts for transitions, encounters and discharge summaries), Snapshot, Navigator"
        },
        {
          "label": "Credentials",
          "value": "OAuth 2.0 client credentials, project-scoped 60-minute JWTs, service accounts with IAM roles, rotation through the Management APIs"
        },
        {
          "label": "Pagination",
          "value": "Continuation or page tokens returned and passed back verbatim"
        },
        {
          "label": "Rate limits",
          "value": "Per project, variable with load, no numbers. Sandbox capped at 500 queries per organisation a day"
        },
        {
          "label": "OpenAPI",
          "value": "OpenAPI fragments on each reference page, with no single specification file found"
        },
        {
          "label": "Status",
          "value": "status.particlehealth.com on Statuspage, 7 components including the production API, sandbox, webhooks and each network"
        }
      ],
      "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,
        "checks": [
          {
            "check": "Legal entity named",
            "value": "Particle Health, Inc.",
            "points": 20,
            "max": 20,
            "state": "ok"
          },
          {
            "check": "Domain age",
            "value": "particlehealth.com, registered 2017-11-22 (8 years)",
            "points": 11,
            "max": 15,
            "state": "part"
          },
          {
            "check": "Endpoint on the vendor's domain",
            "value": "particlehealth.com",
            "points": 15,
            "max": 15,
            "state": "ok"
          },
          {
            "check": "Terms of service",
            "value": "read, states 6 of the 7 things a reader expects, and has 2 clauses that cost points",
            "points": 5.1,
            "max": 10,
            "state": "part"
          },
          {
            "check": "Privacy policy",
            "value": "read, states 5 of the 8 things a reader expects",
            "points": 7.8,
            "max": 10,
            "state": "part"
          },
          {
            "check": "Status page",
            "value": "status.particlehealth.com",
            "points": 10,
            "max": 10,
            "state": "ok"
          },
          {
            "check": "Changelog",
            "value": "not found",
            "points": 0,
            "max": 10,
            "state": "no"
          },
          {
            "check": "security.txt",
            "value": "not found",
            "points": 0,
            "max": 10,
            "state": "no"
          }
        ],
        "policies": [
          {
            "kind": "terms",
            "url": "https://particlehealth.com/terms-of-use",
            "state": "read",
            "readAt": "2026-10-14",
            "statedDate": "2020-10-15",
            "words": 3348,
            "points": 5.1,
            "max": 10,
            "expected": [
              {
                "key": "terms.date",
                "label": "Gives the date it was last updated",
                "found": true,
                "quote": "Effective Date: October 15, 2020",
                "says": "Last updated 2020-10-15"
              },
              {
                "key": "terms.law",
                "label": "Names the governing law or courts",
                "found": true,
                "quote": "These Terms of Use and your use of the Site are governed by the laws of the State of New York, without regard to its choice of law provisions.",
                "says": "The law of the State of New York"
              },
              {
                "key": "terms.liability",
                "label": "States a limit on its liability",
                "found": true,
                "quote": "In no event will Particle Health be liable for the removal of or disabling of access to the Site or any portion thereof."
              },
              {
                "key": "terms.termination",
                "label": "Says how the agreement or account can be ended",
                "found": true,
                "quote": "Particle Health and our licensors reserve the right to change, suspend, remove, or disable access to the Site, or any portion of the Site at any time without notice."
              },
              {
                "key": "terms.changes",
                "label": "Says how changes to the terms are announced",
                "found": true,
                "quote": "Particle Health may, at any time and without notice, modify these Terms of Use by revising them on the Site.",
                "says": "Says it gives notice of a change"
              },
              {
                "key": "terms.use",
                "label": "Lists what users may not do",
                "found": true,
                "quote": "You may not modify these Terms of Use except in a written agreement signed by Particle Health."
              },
              {
                "key": "terms.sla",
                "label": "Refers to a service level or uptime commitment",
                "found": false
              }
            ],
            "toKnow": [
              {
                "key": "terms.automated",
                "label": "Restricts automated access",
                "found": true,
                "quote": "(iv) harvest or scrape any content or data from the Site;",
                "costsPoints": true
              },
              {
                "key": "terms.nonotice",
                "label": "Says the terms or the service can change without notice",
                "found": true,
                "quote": "Particle Health may, at any time and without notice, modify these Terms of Use by revising them on the Site.",
                "costsPoints": true
              },
              {
                "key": "terms.cutoff",
                "label": "Says access can be ended without notice or for any reason",
                "found": true,
                "quote": "Particle Health and our licensors reserve the right to change, suspend, remove, or disable access to the Site, or any portion of the Site at any time without notice."
              },
              {
                "key": "terms.arbitration",
                "label": "Requires arbitration or waives class actions",
                "found": true,
                "quote": "…out of these Terms of Use or any use of the Site shall be determined by one disinterested arbitrator in binding arbitration pursuant to the Commercial Arbitration Rules and the Supplementary Procedures for Online Arbitration of the American Arbitration Association (the “AAA”)."
              },
              {
                "key": "old",
                "label": "Has not been updated for three years or more",
                "found": true,
                "quote": "Effective Date: October 15, 2020"
              }
            ],
            "notes": [
              {
                "date": "2026-10-14",
                "text": "Users grant Particle Health a perpetual, irrevocable, transferable and sublicensable licence to use anything they upload through the Site for any purpose.",
                "quote": "that allows Particle Health to use and exploit the User Submissions for any purpose"
              },
              {
                "date": "2026-10-14",
                "text": "Particle Health excludes liability for all damages connected with use of the Site, direct damages included.",
                "quote": "ARE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF THE SITE"
              }
            ]
          },
          {
            "kind": "privacy",
            "url": "https://particlehealth.com/privacy-policy",
            "state": "read",
            "readAt": "2026-10-14",
            "statedDate": "2026-07-29",
            "words": 1789,
            "points": 7.8,
            "max": 10,
            "expected": [
              {
                "key": "privacy.date",
                "label": "Gives the date it was last updated",
                "found": true,
                "quote": "Effective Date: July 29, 2026",
                "says": "Last updated 2026-07-29"
              },
              {
                "key": "privacy.collected",
                "label": "Says what personal data is collected",
                "found": true,
                "quote": "This Privacy Policy applies solely to the information that we collect through the Site."
              },
              {
                "key": "privacy.retention",
                "label": "Says how long data is kept",
                "found": false
              },
              {
                "key": "privacy.processors",
                "label": "Says who else receives the data",
                "found": true,
                "quote": "Such anonymous, group data may be shared on an aggregated basis with Particle Health’s affiliates, business partners, service providers and/or vendors;"
              },
              {
                "key": "privacy.sale",
                "label": "Says whether personal data is sold or shared for advertising",
                "found": true,
                "quote": "Unless you expressly give us permission in writing to do so, Particle Health will not sell, rent, license, or trade your Personal Information other than as specified in this Privacy Policy.",
                "says": "Says it does not sell personal data"
              },
              {
                "key": "privacy.rights",
                "label": "Says what rights people have over their data",
                "found": false
              },
              {
                "key": "privacy.contact",
                "label": "Gives a privacy contact",
                "found": true,
                "quote": "If you do not wish to receive emails or other communications from us, you may contact us at privacy@particlehealth.com and request that your Personal Information be removed from our list.",
                "says": "privacy@particlehealth.com"
              },
              {
                "key": "privacy.transfers",
                "label": "Says where data is transferred or stored",
                "found": false
              }
            ],
            "notes": [
              {
                "date": "2026-10-14",
                "text": "The policy covers only information collected through the website, not personal information given through a business relationship.",
                "quote": "This Privacy Policy does not address personal information that you provide to us in other contexts (e.g., through a business relationship not handled through the Site)."
              }
            ]
          }
        ]
      },
      "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"
      }
    },
    "verify": {
      "accepts": "a page on particlehealth.com or one of its subdomains",
      "badgeUrl": "https://www.anchorterminal.com/badges/particle-health.svg",
      "body": {
        "slug": "particle-health",
        "url": "the page with the badge or the link"
      },
      "docs": "https://www.anchorterminal.com/builders/#verify",
      "effect": "none, it never changes a grade, rank or review",
      "endpoint": "https://www.anchorterminal.com/api/v1/verify",
      "listingUrl": "https://www.anchorterminal.com/tools/particle-health",
      "mcpTool": "verify_listing",
      "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it",
      "snippets": {
        "html": "\u003ca href=\"https://www.anchorterminal.com/tools/particle-health\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/particle-health.svg\" alt=\"Particle Health on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e",
        "markdown": "[![Particle Health on Anchor Terminal](https://www.anchorterminal.com/badges/particle-health.svg)](https://www.anchorterminal.com/tools/particle-health)",
        "link": "\u003ca href=\"https://www.anchorterminal.com/tools/particle-health\"\u003eParticle Health on Anchor Terminal\u003c/a\u003e"
      }
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/tools/particle-health",
    "json": "https://www.anchorterminal.com/tools/particle-health.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/tools/particle-health.md",
    "slim": "https://www.anchorterminal.com/tools/particle-health.min.md"
  },
  "markdown": "## Overview\n\n**Grade D · 48.6/100 · rank #867 of 1076 · #11 in Health records \u0026 wellness data · not agent-ready · confidence medium**\n\n\n## Assessment\n\nParticle 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## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Particle Health, Inc. (https://particlehealth.com) |\n| Kind | HTTP API |\n| Category | Health records \u0026 wellness data (https://www.anchorterminal.com/categories/health-data) |\n| Transport | HTTP |\n| Auth | OAuth · 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`. |\n| Pricing | Paid (Paid) · 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). |\n| x402 | No · No x402, MPP or L402 in the docs, llms.txt or the website (checked 2026-10-14). |\n| Licence | Proprietary service under customer agreements. The public terms of use (effective 15 October 2020) cover the website only |\n| Docs | https://docs.particlehealth.com |\n| llms.txt | https://docs.particlehealth.com/llms.txt |\n| Endpoints | Sandbox https://sandbox.particlehealth.com, API paths under /api/v1 and /api/v2 |\n| Networks | Carequality, CommonWell, eHealth Exchange, Healthix and Manifest MedEx, and Surescripts for medication data |\n| Data out | FHIR R4B Bundles (all resources or by type), flat datasets by domain, C-CDA zip files, HL7v2 messages, Snapshot AI summaries and a patient provider map |\n| Products | Workbench (on-demand queries), Signal (subscriptions and webhook alerts for transitions, encounters and discharge summaries), Snapshot, Navigator |\n| Credentials | OAuth 2.0 client credentials, project-scoped 60-minute JWTs, service accounts with IAM roles, rotation through the Management APIs |\n| Pagination | Continuation or page tokens returned and passed back verbatim |\n| Rate limits | Per project, variable with load, no numbers. Sandbox capped at 500 queries per organisation a day |\n| OpenAPI | OpenAPI fragments on each reference page, with no single specification file found |\n| Status | status.particlehealth.com on Statuspage, 7 components including the production API, sandbox, webhooks and each network |\n| Capabilities | health.records, health.fhir |\n| Tags | hosted, health-records, fhir, ccda, oauth, llms-txt, webhooks, status-page, sales-led, hitrust, soc2 |\n| JSON | https://www.anchorterminal.com/api/v1/tools/particle-health.json |\n\n## Score breakdown (methodology v0.4, October 2026 research run)\n\nAssessed 2026-10-14 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 58 | 11.6 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 69 | 11.2 |\n| Agent ergonomics | 13% | 16.2 | 53 | 8.6 |\n| Security \u0026 auth | 14% | 17.5 | 57 | 10.0 |\n| Payments \u0026 pricing | 10% | 12.5 | 5 | 0.6 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 27 | 2.4 |\n| Transparency \u0026 trust (editorial 27, provenance 69) | 7% | 8.8 | 48 | 4.2 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **48.6 → D** |\n\n### Why each score\n\n- Reliability 58: Read with the hosted lines. status.particlehealth.com on Statuspage with 7 components and history (20). In the last 90 days, CommonWell traffic was disrupted for about five and a half hours on 5 August 2026, marked critical, and a Google Cloud zone outage on 1 September raised risk with no impact recorded. We read the first as a network-side outage, as for the other network listings (15 of 30). Rate limits exist per project with no numbers, apart from the sandbox's 500 queries a day (5 of 15). 429 with a backoff recommendation, no Retry-After or idempotency guidance (8 of 15). No SLA found in public (0). The v2 APIs are generally available (10).\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 69: OpenAPI fragments on each reference page, with no single specification file found (18 of 25). llms.txt and Markdown pages (10). A developer guide by path (Workbench, Signal) and global conventions for IDs, auth and pagination (14 of 20). Typed inputs in the fragments (11 of 15). A Postman collection and an error code table with context (11 of 15). Versioned /api/v1 and /api/v2 paths and legacy flows marked, but no changelog, which returns 404 (5 of 15).\n- Agent ergonomics 53: FHIR by resource type or ID, flat data filtered by domain, and Snapshot AI summaries where enabled (17 of 25). Continuation tokens and filters (16 of 20). Standard HTTP codes with some context (12 of 20). No idempotency keys or safe-retry guidance (3 of 20). No official SDK (5 of 15).\n- Security \u0026 auth 57: OAuth 2.0 client credentials with a mandatory project scope, 60-minute tokens, rotation that expires old credentials, and IAM roles on service accounts (27 of 30). Project-scoped tokens, roles beyond owner on request, purpose-of-use rules and a delegation of authority policy, with deletes allowed and no confirmation step (13 of 20). Records and AI summaries from outside organisations, with no prompt-injection guidance (3 of 15). No audit log for operators found (2 of 15). HITRUST and SOC 2 claimed for the API platform, a vulnerability submission form, no bug bounty or security.txt (12 of 20).\n- Payments \u0026 pricing 5: Read with the hosted rubric. No x402, MPP or L402 (0). No published prices (0). A sandbox with synthetic patients exists, but credentials come from a representative and the free sign-up link did not resolve (5 of 20). A person must be provisioned by Particle (0).\n- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 27: No dated release was found. Docs pages were updated on 13 October 2026, and v2 subscription endpoints sit beside v1, which we read as recent change without a release record (20 of 30). No changelog (0). Support through a representative, with no public record (5 of 15). No official SDK found (0 of 15). A maintained Postman collection (2 of 10).\n- Transparency \u0026 trust 48: Closed service. The public terms date from 2020 and cover only the website, and no developer or API terms were found (10 of 30). The privacy policy (July 2026) covers the site only and keeps de-identified aggregate data, with no retention periods or public DPA (8 of 30). Legacy flows are labelled as supported for existing customers, with no dates (5 of 20). Google Cloud is named as the platform, with no sub-processor list or regions (4 of 20).\n\nFix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (15 items): https://www.anchorterminal.com/fixes/particle-health.md (JSON https://www.anchorterminal.com/fixes/particle-health.json)\n\n### What we couldn't check\n\n- portal.particlehealth.com, the target of the 'play for free' link, had no DNS record on 14 October 2026, so the free route could not be checked\n- Production base URL not confirmed in the pages read, which show the sandbox host\n- No developer terms, SLA or DPA were found in public\n\n### Sources\n\n- documentation index: \u003chttps://docs.particlehealth.com/llms.txt\u003e (seen 2026-10-14)\n- getting started for developers: \u003chttps://docs.particlehealth.com/docs/getting-started-for-developers.md\u003e (seen 2026-10-14)\n- auth and keys: \u003chttps://docs.particlehealth.com/docs/auth-and-keys.md\u003e (seen 2026-10-14)\n- rate limiting: \u003chttps://docs.particlehealth.com/docs/rate-limiting-and-quotas.md\u003e (seen 2026-10-14)\n- sandbox: \u003chttps://docs.particlehealth.com/docs/test-patient-sandbox.md\u003e (seen 2026-10-14)\n- API getting started: \u003chttps://docs.particlehealth.com/reference/getting-started.md\u003e (seen 2026-10-14)\n- handling errors: \u003chttps://docs.particlehealth.com/reference/handling-errors.md\u003e (seen 2026-10-14)\n- developers page: \u003chttps://particlehealth.com/developers\u003e (seen 2026-10-14)\n- status incidents: \u003chttps://status.particlehealth.com/api/v2/incidents.json\u003e (seen 2026-10-14)\n- security: \u003chttps://particlehealth.com/security\u003e (seen 2026-10-14)\n- terms of use: \u003chttps://particlehealth.com/terms-of-use\u003e (seen 2026-10-14)\n- privacy policy: \u003chttps://particlehealth.com/privacy-policy\u003e (seen 2026-10-14)\n\n## Who's behind it (provenance 69/100, checked 2026-10-14)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | Particle Health, Inc. | 20/20 |\n| Domain age | particlehealth.com, registered 2017-11-22 (8 years) | 11/15 |\n| Endpoint on the vendor's domain | particlehealth.com | 15/15 |\n| Terms of service | read, states 6 of the 7 things a reader expects, and has 2 clauses that cost points | 5.1/10 |\n| Privacy policy | read, states 5 of the 8 things a reader expects | 7.8/10 |\n| Status page | status.particlehealth.com | 10/10 |\n| Changelog | not found | 0/10 |\n| security.txt | not found | 0/10 |\n\nThe 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.\n\nThe privacy policy (effective 29 July 2026) covers information collected through the site only and says Particle may keep de-identified data in aggregate.\n\nThe 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.\n\ndocs.particlehealth.com/changelog returns 404. No public changelog was found.\n\nRDAP gives particlehealth.com a registration date of 2017-11-22.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://particlehealth.com/terms-of-use), read 2026-10-14, dated 2020-10-15, states 6 of the 7 things a reader expects.\n\n- To know. Restricts automated access (costs points). \"(iv) harvest or scrape any content or data from the Site;\"\n- To know. Says the terms or the service can change without notice (costs points). \"Particle Health may, at any time and without notice, modify these Terms of Use by revising them on the Site.\"\n- To know. Says access can be ended without notice or for any reason. \"Particle Health and our licensors reserve the right to change, suspend, remove, or disable access to the Site, or any portion of the Site at any time without notice.\"\n- To know. Requires arbitration or waives class actions. \"…out of these Terms of Use or any use of the Site shall be determined by one disinterested arbitrator in binding arbitration pursuant to the Commercial Arbitration Rules and the Supplementary Procedures for Online Arbitration of the American Arbitration Association (the “AAA”).\"\n- To know. Has not been updated for three years or more. \"Effective Date: October 15, 2020\"\n- Gives the date it was last updated. Last updated 2020-10-15.\n- Names the governing law or courts. The law of the State of New York.\n- Says how changes to the terms are announced. Says it gives notice of a change.\n- Not found in the text. Refers to a service level or uptime commitment.\n- Also in the text (2026-10-14). Users grant Particle Health a perpetual, irrevocable, transferable and sublicensable licence to use anything they upload through the Site for any purpose. \"that allows Particle Health to use and exploit the User Submissions for any purpose\"\n- Also in the text (2026-10-14). Particle Health excludes liability for all damages connected with use of the Site, direct damages included. \"ARE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF THE SITE\"\n\n**Privacy policy** (https://particlehealth.com/privacy-policy), read 2026-10-14, dated 2026-07-29, states 5 of the 8 things a reader expects.\n\n- Gives the date it was last updated. Last updated 2026-07-29.\n- Not found in the text. Says how long data is kept.\n- Says whether personal data is sold or shared for advertising. Says it does not sell personal data.\n- Not found in the text. Says what rights people have over their data.\n- Gives a privacy contact. privacy@particlehealth.com.\n- Not found in the text. Says where data is transferred or stored.\n- Also in the text (2026-10-14). The policy covers only information collected through the website, not personal information given through a business relationship. \"This Privacy Policy does not address personal information that you provide to us in other contexts (e.g., through a business relationship not handled through the Site).\"\n\n## Live (updated 2026-10-14 09:39 UTC)\n\n- Vendor status page: none, All Systems Operational\n- Always current: https://www.anchorterminal.com/api/v1/live/particle-health.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Strengths\n\n- Connected to all three national networks plus Healthix, Manifest MedEx and Surescripts\n- Tokens scoped to one project and expiring after 60 minutes, with credential rotation that retires old secrets\n- FHIR R4B, flat datasets and C-CDA from the same query\n- Sandbox of synthetic patients across every production workflow, 500 queries a day\n\n## Weaknesses\n\n- Credentials come from a Particle representative, and the 'play for free' sign-up domain did not resolve\n- Rate limits vary with load and have no published numbers\n- No changelog, SLA or developer terms in public\n- No audit log for operators was found\n\n## Before you call it (notes for agents)\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## Connect\n\nFirst request:\n\n```bash\nPOST https://sandbox.particlehealth.com/api/v2/patients\nAuthorization: Bearer \u003caccess-token\u003e\nContent-Type: application/json\n```\n\nThrough letme (picks today, calling later): https://letme.dev/particle-health. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Medplum | B | 68.7 | 216 | health.fhir, health.records | no | https://www.anchorterminal.com/tools/medplum.md |\n| Aidbox | B | 64.2 | 385 | health.fhir, health.records | no | https://www.anchorterminal.com/tools/aidbox.md |\n| Health Gorilla | C | 59.3 | 583 | health.records, health.fhir | no | https://www.anchorterminal.com/tools/health-gorilla.md |\n| Redox | C | 58.3 | 618 | health.fhir, health.records | no | https://www.anchorterminal.com/tools/redox.md |\n| Zus Health | C | 56.6 | 669 | health.records, health.fhir | no | https://www.anchorterminal.com/tools/zus-health.md |\n| Medblocks | D | 52.7 | 773 | health.records, health.fhir | no | https://www.anchorterminal.com/tools/medblocks.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- The v2 flow registers a patient, starts a query, polls its status and reads FHIR R4B Bundles, flat datasets or C-CDA files (source: \u003chttps://docs.particlehealth.com/docs/getting-started-for-developers.md\u003e)\n- Tokens are scoped to a single project and expire after 60 minutes (source: \u003chttps://docs.particlehealth.com/docs/auth-and-keys.md\u003e)\n- Rate limits are set per project and vary with system load, with 429 returned and backoff recommended, and no numbers published (source: \u003chttps://docs.particlehealth.com/docs/rate-limiting-and-quotas.md\u003e)\n- The sandbox at https://sandbox.particlehealth.com holds synthetic patients and allows 500 queries per organisation a day (source: \u003chttps://docs.particlehealth.com/docs/test-patient-sandbox.md\u003e)\n- The 'play for free' link on the developers page points to portal.particlehealth.com, which had no DNS record on 14 October 2026 (source: \u003chttps://particlehealth.com/developers\u003e)\n- status.particlehealth.com lists a CommonWell disruption of about five and a half hours on 5 August 2026, marked critical (source: \u003chttps://status.particlehealth.com/api/v2/incidents.json\u003e)\n\n- #11 of 12 in 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## Compare\n\n- [Aidbox vs Particle Health](https://www.anchorterminal.com/compare/aidbox-vs-particle-health.md): B 64.2 vs D 48.6\n- [Medplum vs Particle Health](https://www.anchorterminal.com/compare/medplum-vs-particle-health.md): B 68.7 vs D 48.6\n- [Particle Health vs ROOK](https://www.anchorterminal.com/compare/particle-health-vs-rook.md): D 48.6 vs C 54.9\n- [Particle Health vs Terra API](https://www.anchorterminal.com/compare/particle-health-vs-terra.md): D 48.6 vs B 65.9\n- [1upHealth vs Particle Health](https://www.anchorterminal.com/compare/1uphealth-vs-particle-health.md): D 46.8 vs D 48.6\n- [Health Gorilla vs Particle Health](https://www.anchorterminal.com/compare/health-gorilla-vs-particle-health.md): C 59.3 vs D 48.6\n- [Medblocks vs Particle Health](https://www.anchorterminal.com/compare/medblocks-vs-particle-health.md): D 52.7 vs D 48.6\n- [Metriport Medical API vs Particle Health](https://www.anchorterminal.com/compare/metriport-vs-particle-health.md): D 50.1 vs D 48.6\n- [Particle Health vs Redox](https://www.anchorterminal.com/compare/particle-health-vs-redox.md): D 48.6 vs C 58.3\n- [Particle Health vs Zus Health](https://www.anchorterminal.com/compare/particle-health-vs-zus-health.md): D 48.6 vs C 56.6\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on particlehealth.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"particle-health\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/particle-health\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/particle-health.svg\" alt=\"Particle Health on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Particle Health on Anchor Terminal](https://www.anchorterminal.com/badges/particle-health.svg)](https://www.anchorterminal.com/tools/particle-health)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/particle-health\"\u003eParticle Health on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Particle Health is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/particle-health-dark.png\n- Light: https://www.anchorterminal.com/assets/share/particle-health-light.png\n- Create a video and download its frames: https://www.anchorterminal.com/assets/listing-video/index.html?listing=particle-health\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": "Terminal",
        "url": "https://www.anchorterminal.com/tools/"
      },
      {
        "name": "Health records \u0026 wellness data",
        "url": "https://www.anchorterminal.com/categories/health-data"
      },
      {
        "name": "Particle Health",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": [
      "rank #867 of 1076",
      "OAuth auth",
      "0 desk reviews"
    ],
    "h1": "Particle Health",
    "image": "https://www.anchorterminal.com/assets/og/tools-particle-health.png",
    "path": "/tools/particle-health",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Particle Health review (2026): pricing, alternatives and grade D",
    "toc": null,
    "updated": "2026-10-14",
    "url": "https://www.anchorterminal.com/tools/particle-health"
  },
  "tokens": {
    "markdown": 5600,
    "slim": 1330
  },
  "version": 1
}
