{ "data": { "a": { "slug": "1uphealth", "name": "1upHealth", "vendor": "1upHealth, Inc.", "vendorUrl": "https://1up.health", "kind": "http-api", "category": "health-data", "summary": "1upHealth runs FHIR APIs for US health plans, including the CMS Patient Access, Provider Access and Payer-to-Payer APIs, which let member-authorised third-party apps read claims, coverage and clinical data.", "url": "https://www.anchorterminal.com/tools/1uphealth", "markdownUrl": "https://www.anchorterminal.com/tools/1uphealth.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/1uphealth.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/1uphealth.json", "license": "Proprietary service under 1upHealth's Terms of Service (effective 1 August 2024)", "transports": [ "http" ], "packages": [], "auth": "oauth", "authNotes": "Developers register in the 1up Dev Portal, verify an email and create sandbox client credentials. Patient Access uses the authorisation code grant, with the member signing in to the health plan's auth app, and access tokens last 15 minutes. Provider Access and Payer-to-Payer use client credentials with scopes such as `bulk-data|user/*.rs`. Client secrets can be regenerated in the Dev Portal. Production access follows 1upHealth's vetting of the app.", "pricing": "paid", "pricingNotes": "No public prices. The terms set fees in Order Forms, with one price increase a year on 90 days' notice. The Dev Portal sandbox clients need only a verified email, and no card was mentioned (checked 2026-10-14).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, llms.txt or the terms (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.1up.health", "llmsTxt": "https://docs.1up.health/llms.txt", "capabilities": [ "health.records", "health.fhir", "health.consent" ], "tags": [ "hosted", "health-records", "claims", "fhir", "bulk-data", "oauth", "llms-txt", "status-page", "sla", "free-tier", "hitrust", "soc2" ], "graded": true, "anchor": { "graded": true, "score": 46.8, "grade": "D", "agentReady": false, "rank": 917, "ranked": true, "rankOf": 1094, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 32, "maintenance": 37, "payments": 20, "reliability": 52, "schema": 50, "security": 63, "transparency": 72 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Self-serve Dev Portal sandbox clients and a demo health plan let an app test the CMS Patient Access, Provider Access and Payer-to-Payer FHIR APIs, backed by HITRUST and SOC 2 Type 2. No rate limits, error formats or dated releases are documented, and the Patient Access OAuth step needs the member in a browser.", "bestFor": "Consumer and care apps that read a member's health plan claims and clinical data under the CMS rules, and payers meeting those rules.", "strengths": [ "Sandbox client credentials from the Dev Portal with only an email verification", "Patient Access client IDs work across every payer production environment 1upHealth runs, once vetted", "Privacy policy with stated retention periods and US-only processing", "HITRUST, SOC 2 Type 2 and CSA STAR on a public trust centre" ], "weaknesses": [ "No rate limits, 429 handling or error formats documented", "Release notes are undated", "The status page lists no components", "Patient Connect, the patient-mediated exchange across health systems, was sunset on 30 September 2026" ], "agentNotes": [ "Hand the Patient Access sign-in to the member, who must authorise in the health plan's auth app", "Exchange the authorisation code within five minutes, and refresh before the 15-minute token expires", "Email payer-patient-access@1up.health with the client ID to get the app synced to the demo environment", "Expect only claims and coverage resources from some payers, and read /r4/metadata first" ], "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": 46.8 } ], "editorialScores": { "ergonomics": 32, "maintenance": 37, "payments": 20, "reliability": 52, "schema": 50, "security": 63, "transparency": 61 }, "provenanceScore": 82 }, "connect": { "http": "GET https://api.1uphealthdemo.com/r4/ExplanationOfBenefit\nAuthorization: Bearer \u003caccess-token\u003e" }, "letme": { "capability": "https://letme.dev/health.records", "tool": "https://letme.dev/1uphealth" }, "area": "domain-data", "provenance": { "legalEntity": "1upHealth, Inc.", "domain": "1up.health", "domainRegistered": "2017-07-20", "endpointOnVendorDomain": true, "terms": "https://1up.health/terms-of-service/", "privacy": "https://1up.health/privacy-policy/", "statusPage": "https://status.1up.health", "changelog": "https://docs.1up.health/docs/release-notes", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The Terms of Service (effective 1 August 2024) name 1upHealth, Inc., 280 Summer Street, Boston, MA 02210, and include the SLA as Exhibit A.", "The privacy policy (last updated 25 June 2026) covers the website, keeps logs up to 24 months, clears production data within 30 days and backups within 90 days of a deletion request, keeps data in the US, and leaves PHI to customer BAAs.", "The demo API answers on 1uphealthdemo.com, a separate domain.", "1up.health/.well-known/security.txt returns 404. The trust centre sends vulnerability reports to security@1up.health.", "Release notes carry version numbers such as 26.09.2 but no dates.", "RDAP gives 1up.health a registration date of 2017-07-20." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/1uphealth.json", "live": { "slug": "1uphealth", "vendorStatus": { "page": "https://status.1up.health", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-15T12:30:33.191338559Z" }, "securityTxt": { "url": "https://1up.health/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-15T15:48:47.484682139Z" }, "llmsTxt": { "url": "https://docs.1up.health/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-15T14:15:34.159700529Z" }, "pages": [ { "url": "https://docs.1up.health/docs/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-10-14T20:57:35.414026946Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "cedbe1030f59" }, { "url": "https://1up.health/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-14T20:53:18.912642456Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "fa46893e5c06" }, { "url": "https://1up.health/terms-of-service/", "kind": "terms", "status": 200, "checkedAt": "2026-10-14T20:53:20.999110543Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9f420f2b8312" } ], "updatedAt": "2026-10-15T15:48:47.484682139Z" } }, "answer": "Zus Health scores 56.6 (C) on agent readiness against 1upHealth's 46.8 (D), and leads in 4 of 7 scored categories. 1upHealth leads on security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust.", "b": { "slug": "zus-health", "name": "Zus Health", "vendor": "Zus Health, Inc.", "vendorUrl": "https://www.zushealth.com", "kind": "http-api", "category": "health-data", "summary": "Zus Health assembles a patient's history from CommonWell, Carequality, Surescripts, Quest and ADT networks into the Zus Aggregated Profile, and exposes it through FHIR R4 REST, GraphQL and webhook APIs for care organisations it onboards.", "url": "https://www.anchorterminal.com/tools/zus-health", "markdownUrl": "https://www.anchorterminal.com/tools/zus-health.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zus-health.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zus-health.json", "license": "Proprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum", "transports": [ "http" ], "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 bearer tokens valid for one hour. Backend systems use machine-to-machine App Clients created in the Zus app or through the Auth Service API, limited to 200 token requests an hour per client. Apps can exchange an OIDC ID token from their own identity provider for a Zus token, and integration App Clients with the Builder Data Integration role can fetch tokens for users through the proxy-token endpoint. Accounts are provisioned by Zus, with an initial admin per customer.", "pricing": "paid", "pricingNotes": "No public prices. The Builder Terms set fees in an executed Order Form or pricing list, invoiced monthly. A developer sandbox is requested through a Google Form on the docs site, and its cost is not stated (checked 2026-10-14).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the documentation, llms.txt or the Builder Terms (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.zushealth.com", "llmsTxt": "https://docs.zushealth.com/llms.txt", "capabilities": [ "health.records", "health.fhir", "health.ehr", "health.consent" ], "tags": [ "hosted", "health-records", "fhir", "graphql", "oauth", "llms-txt", "webhooks", "status-page", "sla", "sales-led" ], "lastRelease": "2026-10-14", "graded": true, "anchor": { "graded": true, "score": 56.6, "grade": "C", "agentReady": false, "rank": 674, "ranked": true, "rankOf": 1094, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 64, "payments": 5, "reliability": 66, "schema": 77, "security": 49, "transparency": 59 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "FHIR R4 over an aggregated patient profile drawn from CommonWell, Carequality, Surescripts, Quest and ADT networks, with published rate limits, a 99.5 per cent SLA and a dated changelog. Accounts and sandboxes are provisioned by Zus on request, with no public prices, no named security certification and no SDK.", "bestFor": "US care organisations and digital health builders that want a shared, continuously refreshed patient profile in FHIR with EHR embedding.", "strengths": [ "One profile per patient from EHR, pharmacy, ADT and lab networks, shared across Zus customers treating the same patient", "Rate limits with numbers and a published 99.5 per cent SLA with credits", "Conditional writes by identifier and `Zus-If-Match` version checks for safe retries", "Dated changelog that announces changes ahead, such as the proxy-token role change on 14 October 2026" ], "weaknesses": [ "No public prices, and the sandbox is requested through a Google Form", "Four major incidents on the status page between 27 July and 13 August 2026", "No named security certification, security.txt or bug bounty", "The GraphQL API is beta and no official SDK exists" ], "agentNotes": [ "Cache the access token for its hour. More than 200 token requests an hour per App Client returns 429", "Request Patient History at most once per patient per 24 hours, and poll the job status endpoint", "Use conditional create by identifier so a retried write doesn't duplicate a resource", "Send `Zus-If-Match` with the resource's ETag on PUT and PATCH", "Set `_count` up to 500 on searches, since the default page is 10" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.6 } ], "editorialScores": { "ergonomics": 67, "maintenance": 64, "payments": 5, "reliability": 66, "schema": 77, "security": 49, "transparency": 46 }, "provenanceScore": 71 }, "connect": { "http": "GET https://api.sandbox.zusapi.com/fhir/Patient?_count=50\nAuthorization: Bearer \u003caccess-token\u003e" }, "letme": { "capability": "https://letme.dev/health.records", "tool": "https://letme.dev/zus-health" }, "area": "domain-data", "provenance": { "legalEntity": "Zus Health, Inc.", "domain": "zushealth.com", "domainRegistered": "2012-02-25", "endpointOnVendorDomain": false, "terms": "https://www.zushealth.com/builder-terms-of-service", "privacy": "https://www.zushealth.com/privacy-policy", "statusPage": "https://status.zusapi.com", "changelog": "https://docs.zushealth.com/changelog", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The APIs answer on zusapi.com, a separate domain from zushealth.com.", "The Builder Terms (last updated 11 March 2025) put term changes into effect 30 days after posting and BAA changes after 90 days. The Developer Sandbox Terms (22 January 2024) limit the sandbox to test data. The website lists 1 Lincoln Street, Suite 2900, Boston, MA 02111.", "The privacy policy (last updated 24 June 2026) covers the website only and names Google Analytics.", "The Builder Security Policy (11 March 2025) names no certification and makes a summary of an annual third-party audit available on request.", "www.zushealth.com/.well-known/security.txt returns 404.", "RDAP gives zushealth.com a registration date of 2012-02-25." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/zus-health.json", "live": { "slug": "zus-health", "vendorStatus": { "page": "https://status.zusapi.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-15T10:07:56.30662534Z" }, "securityTxt": { "url": "https://zushealth.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-15T15:48:24.508770833Z" }, "llmsTxt": { "url": "https://docs.zushealth.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-15T14:18:07.822241334Z" }, "pages": [ { "url": "https://docs.zushealth.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-14T21:00:01.505614661Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9349ea051538" }, { "url": "https://www.zushealth.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-14T21:19:34.184342833Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "cd627e540dc7" }, { "url": "https://www.zushealth.com/builder-terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-10-14T21:19:32.098315146Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "64849d2141d4" } ], "updatedAt": "2026-10-15T15:48:24.508770833Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "1upHealth, Inc.", "b": "Zus Health, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under 1upHealth's Terms of Service (effective 1 August 2024)", "b": "Proprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-14", "name": "Last release" }, { "a": "no date given", "b": "2025-03-11", "name": "Terms last updated" }, { "a": "2026-06-25", "b": "2026-06-24", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Zus Health scores 56.6 (C) on agent readiness against 1upHealth's 46.8 (D), and leads in 4 of 7 scored categories. 1upHealth leads on security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust.", "question": "Which is better for AI agents, 1upHealth or Zus Health?" }, { "answer": "Both use an OAuth sign-in.", "question": "Do 1upHealth and Zus Health need an API key?" }, { "answer": "No hosted endpoint is listed for 1upHealth. No hosted endpoint is listed for Zus Health.", "question": "Can an agent call 1upHealth and Zus Health without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 63 against 49", "Payments \u0026 pricing, 20 against 5", "Transparency \u0026 trust, 72 against 59" ], "also": null, "goodFor": "Consumer and care apps that read a member's health plan claims and clinical data under the CMS rules, and payers meeting those rules.", "slug": "1uphealth", "watchFor": "No rate limits, 429 handling or error formats documented" }, { "aheadOn": [ "Reliability, 66 against 52", "Schema \u0026 documentation, 77 against 50", "Agent ergonomics, 67 against 32", "Maintenance \u0026 community, 64 against 37" ], "also": null, "goodFor": "US care organisations and digital health builders that want a shared, continuously refreshed patient profile in FHIR with EHR embedding.", "slug": "zus-health", "watchFor": "No public prices, and the sandbox is requested through a Google Form" } ], "job": { "capability": "health.records", "name": "Patient record retrieval" }, "others": [ { "json": "https://www.anchorterminal.com/compare/1uphealth-vs-rook.json", "title": "1upHealth vs ROOK", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/1uphealth-vs-terra.json", "title": "1upHealth vs Terra API", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-terra" }, { "json": "https://www.anchorterminal.com/compare/aidbox-vs-zus-health.json", "title": "Aidbox vs Zus Health", "url": "https://www.anchorterminal.com/compare/aidbox-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/medplum-vs-zus-health.json", "title": "Medplum vs Zus Health", "url": "https://www.anchorterminal.com/compare/medplum-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/1uphealth-vs-aidbox.json", "title": "1upHealth vs Aidbox", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-aidbox" }, { "json": "https://www.anchorterminal.com/compare/1uphealth-vs-health-gorilla.json", "title": "1upHealth vs Health Gorilla", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-health-gorilla" }, { "json": "https://www.anchorterminal.com/compare/1uphealth-vs-medblocks.json", "title": "1upHealth vs Medblocks", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-medblocks" }, { "json": "https://www.anchorterminal.com/compare/1uphealth-vs-medplum.json", "title": "1upHealth vs Medplum", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-medplum" }, { "json": "https://www.anchorterminal.com/compare/1uphealth-vs-metriport.json", "title": "1upHealth vs Metriport Medical API", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-metriport" }, { "json": "https://www.anchorterminal.com/compare/1uphealth-vs-particle-health.json", "title": "1upHealth vs Particle Health", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-particle-health" }, { "json": "https://www.anchorterminal.com/compare/1uphealth-vs-redox.json", "title": "1upHealth vs Redox", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-zus-health.json", "title": "Health Gorilla vs Zus Health", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-zus-health.json", "title": "Medblocks vs Zus Health", "url": "https://www.anchorterminal.com/compare/medblocks-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/metriport-vs-zus-health.json", "title": "Metriport Medical API vs Zus Health", "url": "https://www.anchorterminal.com/compare/metriport-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/particle-health-vs-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/1uphealth-vs-validic.json", "title": "1upHealth vs Validic Inform", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-validic" }, { "json": "https://www.anchorterminal.com/compare/rook-vs-zus-health.json", "title": "ROOK vs Zus Health", "url": "https://www.anchorterminal.com/compare/rook-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/terra-vs-zus-health.json", "title": "Terra API vs Zus Health", "url": "https://www.anchorterminal.com/compare/terra-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/validic-vs-zus-health.json", "title": "Validic Inform vs Zus Health", "url": "https://www.anchorterminal.com/compare/validic-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/redox-vs-zus-health.json", "title": "Redox vs Zus Health", "url": "https://www.anchorterminal.com/compare/redox-vs-zus-health" } ], "scores": [ { "1uphealth": 52, "by": 14, "edge": "zus-health", "key": "reliability", "name": "Reliability", "weight": 16, "zus-health": 66 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "1uphealth": 50, "by": 27, "edge": "zus-health", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "zus-health": 77 }, { "1uphealth": 32, "by": 35, "edge": "zus-health", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "zus-health": 67 }, { "1uphealth": 63, "by": 14, "edge": "1uphealth", "key": "security", "name": "Security \u0026 auth", "weight": 14, "zus-health": 49 }, { "1uphealth": 20, "by": 15, "edge": "1uphealth", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "zus-health": 5 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "1uphealth": 37, "by": 27, "edge": "zus-health", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "zus-health": 64 }, { "1uphealth": 72, "by": 13, "edge": "1uphealth", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "zus-health": 59 } ], "summary": "Zus Health scores 56.6 (C) on agent readiness against 1upHealth's 46.8 (D), and leads in 4 of 7 scored categories. 1upHealth leads on security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust. Both do patient record retrieval.", "verdicts": { "1uphealth": "Self-serve Dev Portal sandbox clients and a demo health plan let an app test the CMS Patient Access, Provider Access and Payer-to-Payer FHIR APIs, backed by HITRUST and SOC 2 Type 2. No rate limits, error formats or dated releases are documented, and the Patient Access OAuth step needs the member in a browser.", "zus-health": "FHIR R4 over an aggregated patient profile drawn from CommonWell, Carequality, Surescripts, Quest and ADT networks, with published rate limits, a 99.5 per cent SLA and a dated changelog. Accounts and sandboxes are provisioned by Zus on request, with no public prices, no named security certification and no SDK." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/1uphealth-vs-zus-health", "json": "https://www.anchorterminal.com/compare/1uphealth-vs-zus-health.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/1uphealth-vs-zus-health.md", "slim": "https://www.anchorterminal.com/compare/1uphealth-vs-zus-health.min.md" }, "markdown": "Zus Health scores 56.6 (C) on agent readiness against 1upHealth's 46.8 (D), and leads in 4 of 7 scored categories. 1upHealth leads on security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust. Both do patient record retrieval.\n\n- 1upHealth: grade D, 46.8/100, rank #917 of 1094. Markdown https://www.anchorterminal.com/tools/1uphealth.md · JSON https://www.anchorterminal.com/api/v1/tools/1uphealth.json\n- Zus Health: grade C, 56.6/100, rank #674 of 1094. Markdown https://www.anchorterminal.com/tools/zus-health.md · JSON https://www.anchorterminal.com/api/v1/tools/zus-health.json\n- Best health record and wellness data APIs for AI agents: https://www.anchorterminal.com/best/health-data/index.md\n- All 63 health comparisons: https://www.anchorterminal.com/compare/health-data/index.md\n\n## Which one, for what\n\n### 1upHealth (D)\n\nGood for: Consumer and care apps that read a member's health plan claims and clinical data under the CMS rules, and payers meeting those rules.\n\nAhead on:\n- Security \u0026 auth, 63 against 49\n- Payments \u0026 pricing, 20 against 5\n- Transparency \u0026 trust, 72 against 59\n\nWatch for: No rate limits, 429 handling or error formats documented\n\n### Zus Health (C)\n\nGood for: US care organisations and digital health builders that want a shared, continuously refreshed patient profile in FHIR with EHR embedding.\n\nAhead on:\n- Reliability, 66 against 52\n- Schema \u0026 documentation, 77 against 50\n- Agent ergonomics, 67 against 32\n- Maintenance \u0026 community, 64 against 37\n\nWatch for: No public prices, and the sandbox is requested through a Google Form\n\n\n## Score by category\n\n| Category | Weight | 1upHealth | Zus Health | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 52 | 66 | Zus Health +14 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 50 | 77 | Zus Health +27 |\n| Agent ergonomics | 13% (16.2 this run) | 32 | 67 | Zus Health +35 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 49 | 1upHealth +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 5 | 1upHealth +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 37 | 64 | Zus Health +27 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 59 | 1upHealth +13 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **46.8 · D** | **56.6 · C** | |\n\n## Facts side by side\n\n| Fact | 1upHealth | Zus Health |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | 1upHealth, Inc. | Zus Health, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | OAuth | OAuth |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under 1upHealth's Terms of Service (effective 1 August 2024) | Proprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-10-14 |\n| Terms last updated | no date given | 2025-03-11 |\n| Privacy policy last updated | 2026-06-25 | 2026-06-24 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n\n## Verdicts\n\n**1upHealth.** Self-serve Dev Portal sandbox clients and a demo health plan let an app test the CMS Patient Access, Provider Access and Payer-to-Payer FHIR APIs, backed by HITRUST and SOC 2 Type 2. No rate limits, error formats or dated releases are documented, and the Patient Access OAuth step needs the member in a browser.\n\n**Zus Health.** FHIR R4 over an aggregated patient profile drawn from CommonWell, Carequality, Surescripts, Quest and ADT networks, with published rate limits, a 99.5 per cent SLA and a dated changelog. Accounts and sandboxes are provisioned by Zus on request, with no public prices, no named security certification and no SDK.\n\n## Before you call either\n\n### 1upHealth\n\n1. Hand the Patient Access sign-in to the member, who must authorise in the health plan's auth app\n2. Exchange the authorisation code within five minutes, and refresh before the 15-minute token expires\n3. Email payer-patient-access@1up.health with the client ID to get the app synced to the demo environment\n4. Expect only claims and coverage resources from some payers, and read /r4/metadata first\n\n### Zus Health\n\n1. Cache the access token for its hour. More than 200 token requests an hour per App Client returns 429\n2. Request Patient History at most once per patient per 24 hours, and poll the job status endpoint\n3. Use conditional create by identifier so a retried write doesn't duplicate a resource\n4. Send `Zus-If-Match` with the resource's ETag on PUT and PATCH\n5. Set `_count` up to 500 on searches, since the default page is 10\n\n## Questions\n\n### Which is better for AI agents, 1upHealth or Zus Health?\n\nZus Health scores 56.6 (C) on agent readiness against 1upHealth's 46.8 (D), and leads in 4 of 7 scored categories. 1upHealth leads on security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust.\n\n### Do 1upHealth and Zus Health need an API key?\n\nBoth use an OAuth sign-in.\n\n### Can an agent call 1upHealth and Zus Health without installing anything?\n\nNo hosted endpoint is listed for 1upHealth. No hosted endpoint is listed for Zus Health.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/1uphealth-vs-zus-health.json, and with the fewest tokens: https://www.anchorterminal.com/compare/1uphealth-vs-zus-health.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"1uphealth\", \"b\": \"zus-health\"}`. From a terminal: `anchor compare 1uphealth zus-health`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/1uphealth.json and https://www.anchorterminal.com/api/v1/tools/zus-health.json\n\n## Other comparisons with 1upHealth or Zus Health\n\n- [1upHealth vs ROOK](https://www.anchorterminal.com/compare/1uphealth-vs-rook.md)\n- [1upHealth vs Terra API](https://www.anchorterminal.com/compare/1uphealth-vs-terra.md)\n- [Aidbox vs Zus Health](https://www.anchorterminal.com/compare/aidbox-vs-zus-health.md)\n- [Medplum vs Zus Health](https://www.anchorterminal.com/compare/medplum-vs-zus-health.md)\n- [1upHealth vs Aidbox](https://www.anchorterminal.com/compare/1uphealth-vs-aidbox.md)\n- [1upHealth vs Health Gorilla](https://www.anchorterminal.com/compare/1uphealth-vs-health-gorilla.md)\n- [1upHealth vs Medblocks](https://www.anchorterminal.com/compare/1uphealth-vs-medblocks.md)\n- [1upHealth vs Medplum](https://www.anchorterminal.com/compare/1uphealth-vs-medplum.md)\n- [1upHealth vs Metriport Medical API](https://www.anchorterminal.com/compare/1uphealth-vs-metriport.md)\n- [1upHealth vs Particle Health](https://www.anchorterminal.com/compare/1uphealth-vs-particle-health.md)\n- [1upHealth vs Redox](https://www.anchorterminal.com/compare/1uphealth-vs-redox.md)\n- [Health Gorilla vs Zus Health](https://www.anchorterminal.com/compare/health-gorilla-vs-zus-health.md)\n- [Medblocks vs Zus Health](https://www.anchorterminal.com/compare/medblocks-vs-zus-health.md)\n- [Metriport Medical API vs Zus Health](https://www.anchorterminal.com/compare/metriport-vs-zus-health.md)\n- [Particle Health vs Zus Health](https://www.anchorterminal.com/compare/particle-health-vs-zus-health.md)\n- [1upHealth vs Validic Inform](https://www.anchorterminal.com/compare/1uphealth-vs-validic.md)\n- [ROOK vs Zus Health](https://www.anchorterminal.com/compare/rook-vs-zus-health.md)\n- [Terra API vs Zus Health](https://www.anchorterminal.com/compare/terra-vs-zus-health.md)\n- [Validic Inform vs Zus Health](https://www.anchorterminal.com/compare/validic-vs-zus-health.md)\n- [Redox vs Zus Health](https://www.anchorterminal.com/compare/redox-vs-zus-health.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author.", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-15", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "1upHealth vs Zus Health", "url": "" } ], "description": "Zus Health scores 56.6 (C) to 1upHealth's 46.8 (D) for patient record retrieval. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "1upHealth D 46.8", "Zus Health C 56.6", "scores" ], "h1": "1upHealth vs Zus Health", "image": "https://www.anchorterminal.com/assets/og/compare-1uphealth-vs-zus-health.png", "path": "/compare/1uphealth-vs-zus-health", "published": "2026-10-01", "section": "tools", "title": "1upHealth vs Zus Health for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-15", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-zus-health" }, "tokens": { "markdown": 2200, "slim": 630 }, "version": 1 }