{ "data": { "a": { "slug": "validic", "name": "Validic Inform", "vendor": "Validic, Inc. (ChartSpan)", "vendorUrl": "https://validic.com", "kind": "http-api", "category": "health-data", "summary": "Validic Inform normalises data from wearables, health apps and in-home medical devices into one API, with a REST API for per-user reads and a server-sent events Streaming API for bulk delivery, and a free self-service developer tier.", "url": "https://www.anchorterminal.com/tools/validic", "markdownUrl": "https://www.anchorterminal.com/tools/validic.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/validic.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/validic.json", "repo": "https://github.com/Validic/inform-quickstart", "license": "Proprietary service under Validic's Online Service Agreement for Inform (last updated 13 August 2025). The inform-quickstart sample apps are MIT", "transports": [ "http", "sse" ], "packages": [], "auth": "api-key", "authNotes": "Every Inform request carries the organisation token as `?token=` in the query string, the only option documented. A developer account is created by a sign-up API at https://api.dashboard.validic.com (register, verify a six-digit emailed code, log in, provision), which returns `organization_id` and `organization_token`. End users connect their devices through a Validic marketplace URL returned for each user. No scopes or rotation were found.", "pricing": "freemium", "pricingNotes": "The Developer tier is free with no card or contract and allows 5 connected users, 5 cloud integrations, the Streaming API, a REST API preview and 90-day retention, on synthetic test data, with no SLA. A Business tier is listed as coming soon. Enterprise is negotiated and adds a BAA, custom SLA, all sources and 7-year retention (checked 2026-10-14).", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, agent guides or the sign-up page (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://developer.validic.com", "llmsTxt": "https://developer.validic.com/llms.txt", "capabilities": [ "health.wearables", "health.consent" ], "tags": [ "hosted", "wearables", "remote-patient-monitoring", "api-key", "llms-txt", "sse", "free-tier", "status-page", "programmatic-signup" ], "lastRelease": "2026-10-12", "graded": true, "anchor": { "graded": true, "score": 57.9, "grade": "C", "agentReady": false, "rank": 628, "ranked": true, "rankOf": 1076, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 50, "maintenance": 74, "payments": 40, "reliability": 73, "schema": 75, "security": 30, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Graded on the Inform REST and Streaming APIs. An agent can create a free developer account through a sign-up API, with only an emailed code needing a person's inbox, and llms.txt plus agent guides document every step. The organisation token travels in the URL query string, the free tier holds synthetic data only, and production access needs an Enterprise contract.", "bestFor": "A remote patient monitoring or wellness app that needs normalised readings from many wearables and home devices, and an agent that wants to start building without a sales call.", "strengths": [ "Sign-up, email verification and organisation provisioning are all API calls, with an agent guide at dashboard.validic.com/agents.txt", "Free developer tier with no card or contract, covering 5 users and 5 cloud integrations", "Published rate limit of 2,000 REST requests per token per hour", "Dated release notes, the newest for the Inform platform on 12 October 2026", "No status page incidents between 16 July and 14 October 2026" ], "weaknesses": [ "The organisation token is sent as `?token=` in the URL, the only documented option", "Errors return only a status and a phrase, and a date range over the limit gives a bare 400", "The free tier holds synthetic data only, and the REST API there is a preview", "No server-side SDK and no full OpenAPI file, only fragments on each reference page" ], "agentNotes": [ "Show the developer the free-tier terms and wait for acceptance before calling `POST /auth/register`", "Send `Authorization: \u003cid_token\u003e` to sign-up calls, but pass the organisation token as `?token=` on Inform calls", "Use the customer `uid` in URLs, never Validic's internal `id`, which returns a silent 404", "Keep date ranges to 30 days or less and page month by month for backfills", "Unwrap `data` on list responses and treat an empty array as normal on a new account" ], "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": 57.9 } ], "editorialScores": { "ergonomics": 50, "maintenance": 74, "payments": 40, "reliability": 73, "schema": 75, "security": 30, "transparency": 53 }, "provenanceScore": 88 }, "connect": { "http": "curl \"https://api.v2.validic.com/organizations/$ORG_ID/users?token=$ORG_TOKEN\"" }, "letme": { "capability": "https://letme.dev/health.wearables", "tool": "https://letme.dev/validic" }, "area": "domain-data", "provenance": { "legalEntity": "Validic, Inc.", "domain": "validic.com", "domainRegistered": "2005-09-11", "endpointOnVendorDomain": true, "terms": "https://validic.com/online-service-agreement-inform/", "privacy": "https://validic.com/privacy-policy/", "statusPage": "https://status.validic.com", "changelog": "https://help.validic.com/space/VRN", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The Online Service Agreement (last updated 13 August 2025) names Validic, Inc. The privacy policy was last updated 20 January 2026.", "ChartSpan announced the completed acquisition of Validic on 22 June 2026, and the inform-quickstart licence names Chartspan Medical Technologies.", "validic.com/.well-known/security.txt returns 404.", "The developer changelog at developer.validic.com/changelog stopped on 15 April 2025 and points to the release notes on help.validic.com.", "RDAP for validic.com gives a registration date of 11 September 2005." ], "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/validic.json", "live": { "slug": "validic", "vendorStatus": { "page": "https://status.validic.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:45.767488138Z" }, "updatedAt": "2026-10-14T09:39:45.767488138Z" } }, "answer": "Validic Inform scores 57.9 (C) on agent readiness against Zus Health's 56.6 (C), and leads in 4 of 7 scored categories. Zus Health leads on agent ergonomics and security \u0026 auth.", "b": { "slug": "zus-health", "name": "Zus Health", "vendor": "Zus Health, Inc.", "vendorUrl": "https://www.zushealth.com", "kind": "http-api", "category": "health-data", "summary": "Zus Health assembles a patient's history from CommonWell, Carequality, Surescripts, Quest and ADT networks into the Zus Aggregated Profile, and exposes it through FHIR R4 REST, GraphQL and webhook APIs for care organisations it onboards.", "url": "https://www.anchorterminal.com/tools/zus-health", "markdownUrl": "https://www.anchorterminal.com/tools/zus-health.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zus-health.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zus-health.json", "license": "Proprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum", "transports": [ "http" ], "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 bearer tokens valid for one hour. Backend systems use machine-to-machine App Clients created in the Zus app or through the Auth Service API, limited to 200 token requests an hour per client. Apps can exchange an OIDC ID token from their own identity provider for a Zus token, and integration App Clients with the Builder Data Integration role can fetch tokens for users through the proxy-token endpoint. Accounts are provisioned by Zus, with an initial admin per customer.", "pricing": "paid", "pricingNotes": "No public prices. The Builder Terms set fees in an executed Order Form or pricing list, invoiced monthly. A developer sandbox is requested through a Google Form on the docs site, and its cost is not stated (checked 2026-10-14).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the documentation, llms.txt or the Builder Terms (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.zushealth.com", "llmsTxt": "https://docs.zushealth.com/llms.txt", "capabilities": [ "health.records", "health.fhir", "health.ehr", "health.consent" ], "tags": [ "hosted", "health-records", "fhir", "graphql", "oauth", "llms-txt", "webhooks", "status-page", "sla", "sales-led" ], "lastRelease": "2026-10-14", "graded": true, "anchor": { "graded": true, "score": 56.6, "grade": "C", "agentReady": false, "rank": 669, "ranked": true, "rankOf": 1076, "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-14T08:54:10.020449939Z" }, "updatedAt": "2026-10-14T08:54:10.020449939Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Validic, Inc. (ChartSpan)", "b": "Zus Health, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, SSE (legacy)", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Validic's Online Service Agreement for Inform (last updated 13 August 2025). The inform-quickstart sample apps are MIT", "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": "2026-10-12", "b": "2026-10-14", "name": "Last release" }, { "a": "2025-08-13", "b": "2025-03-11", "name": "Terms last updated" }, { "a": "2026-01-20", "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": "Validic Inform scores 57.9 (C) on agent readiness against Zus Health's 56.6 (C), and leads in 4 of 7 scored categories. Zus Health leads on agent ergonomics and security \u0026 auth.", "question": "Which is better for AI agents, Validic Inform or Zus Health?" }, { "answer": "Validic Inform needs an API key. Zus Health uses an OAuth sign-in.", "question": "Do Validic Inform and Zus Health need an API key?" }, { "answer": "No hosted endpoint is listed for Validic Inform. No hosted endpoint is listed for Zus Health.", "question": "Can an agent call Validic Inform and Zus Health without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 73 against 66", "Payments \u0026 pricing, 40 against 5", "Maintenance \u0026 community, 74 against 64", "Transparency \u0026 trust, 71 against 59" ], "also": null, "goodFor": "A remote patient monitoring or wellness app that needs normalised readings from many wearables and home devices, and an agent that wants to start building without a sales call.", "slug": "validic", "watchFor": "The organisation token is sent as `?token=` in the URL, the only documented option" }, { "aheadOn": [ "Agent ergonomics, 67 against 50", "Security \u0026 auth, 49 against 30" ], "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.consent", "name": "Patient consent" }, "others": [ { "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-zus-health.json", "title": "1upHealth vs Zus Health", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-zus-health" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-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/aidbox-vs-validic.json", "title": "Aidbox vs Validic Inform", "url": "https://www.anchorterminal.com/compare/aidbox-vs-validic" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-validic.json", "title": "Health Gorilla vs Validic Inform", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-validic" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-validic.json", "title": "Medblocks vs Validic Inform", "url": "https://www.anchorterminal.com/compare/medblocks-vs-validic" }, { "json": "https://www.anchorterminal.com/compare/metriport-vs-validic.json", "title": "Metriport Medical API vs Validic Inform", "url": "https://www.anchorterminal.com/compare/metriport-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/rook-vs-validic.json", "title": "ROOK vs Validic Inform", "url": "https://www.anchorterminal.com/compare/rook-vs-validic" }, { "json": "https://www.anchorterminal.com/compare/terra-vs-validic.json", "title": "Terra API vs Validic Inform", "url": "https://www.anchorterminal.com/compare/terra-vs-validic" }, { "json": "https://www.anchorterminal.com/compare/redox-vs-zus-health.json", "title": "Redox vs Zus Health", "url": "https://www.anchorterminal.com/compare/redox-vs-zus-health" } ], "scores": [ { "by": 7, "edge": "validic", "key": "reliability", "name": "Reliability", "validic": 73, "weight": 16, "zus-health": 66 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "edge": "zus-health", "key": "schema", "name": "Schema \u0026 documentation", "validic": 75, "weight": 13, "zus-health": 77 }, { "by": 17, "edge": "zus-health", "key": "ergonomics", "name": "Agent ergonomics", "validic": 50, "weight": 13, "zus-health": 67 }, { "by": 19, "edge": "zus-health", "key": "security", "name": "Security \u0026 auth", "validic": 30, "weight": 14, "zus-health": 49 }, { "by": 35, "edge": "validic", "key": "payments", "name": "Payments \u0026 pricing", "validic": 40, "weight": 10, "zus-health": 5 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 10, "edge": "validic", "key": "maintenance", "name": "Maintenance \u0026 community", "validic": 74, "weight": 7, "zus-health": 64 }, { "by": 12, "edge": "validic", "key": "transparency", "name": "Transparency \u0026 trust", "validic": 71, "weight": 7, "zus-health": 59 } ], "summary": "Validic Inform scores 57.9 (C) on agent readiness against Zus Health's 56.6 (C), and leads in 4 of 7 scored categories. Zus Health leads on agent ergonomics and security \u0026 auth. Both do patient consent.", "verdicts": { "validic": "Graded on the Inform REST and Streaming APIs. An agent can create a free developer account through a sign-up API, with only an emailed code needing a person's inbox, and llms.txt plus agent guides document every step. The organisation token travels in the URL query string, the free tier holds synthetic data only, and production access needs an Enterprise contract.", "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/validic-vs-zus-health", "json": "https://www.anchorterminal.com/compare/validic-vs-zus-health.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/validic-vs-zus-health.md", "slim": "https://www.anchorterminal.com/compare/validic-vs-zus-health.min.md" }, "markdown": "Validic Inform scores 57.9 (C) on agent readiness against Zus Health's 56.6 (C), and leads in 4 of 7 scored categories. Zus Health leads on agent ergonomics and security \u0026 auth. Both do patient consent.\n\n- Validic Inform: grade C, 57.9/100, rank #628 of 1076. Markdown https://www.anchorterminal.com/tools/validic.md · JSON https://www.anchorterminal.com/api/v1/tools/validic.json\n- Zus Health: grade C, 56.6/100, rank #669 of 1076. 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### Validic Inform (C)\n\nGood for: A remote patient monitoring or wellness app that needs normalised readings from many wearables and home devices, and an agent that wants to start building without a sales call.\n\nAhead on:\n- Reliability, 73 against 66\n- Payments \u0026 pricing, 40 against 5\n- Maintenance \u0026 community, 74 against 64\n- Transparency \u0026 trust, 71 against 59\n\nWatch for: The organisation token is sent as `?token=` in the URL, the only documented option\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- Agent ergonomics, 67 against 50\n- Security \u0026 auth, 49 against 30\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 | Validic Inform | Zus Health | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 66 | Validic Inform +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 75 | 77 | Zus Health +2 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 67 | Zus Health +17 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 49 | Zus Health +19 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 5 | Validic Inform +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 74 | 64 | Validic Inform +10 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 59 | Validic Inform +12 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57.9 · C** | **56.6 · C** | |\n\n## Facts side by side\n\n| Fact | Validic Inform | Zus Health |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Validic, Inc. (ChartSpan) | Zus Health, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP, SSE (legacy) | HTTP |\n| Auth | API key | OAuth |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Validic's Online Service Agreement for Inform (last updated 13 August 2025). The inform-quickstart sample apps are MIT | 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 | 2026-10-12 | 2026-10-14 |\n| Terms last updated | 2025-08-13 | 2025-03-11 |\n| Privacy policy last updated | 2026-01-20 | 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**Validic Inform.** Graded on the Inform REST and Streaming APIs. An agent can create a free developer account through a sign-up API, with only an emailed code needing a person's inbox, and llms.txt plus agent guides document every step. The organisation token travels in the URL query string, the free tier holds synthetic data only, and production access needs an Enterprise contract.\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### Validic Inform\n\n1. Show the developer the free-tier terms and wait for acceptance before calling `POST /auth/register`\n2. Send `Authorization: \u003cid_token\u003e` to sign-up calls, but pass the organisation token as `?token=` on Inform calls\n3. Use the customer `uid` in URLs, never Validic's internal `id`, which returns a silent 404\n4. Keep date ranges to 30 days or less and page month by month for backfills\n5. Unwrap `data` on list responses and treat an empty array as normal on a new account\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, Validic Inform or Zus Health?\n\nValidic Inform scores 57.9 (C) on agent readiness against Zus Health's 56.6 (C), and leads in 4 of 7 scored categories. Zus Health leads on agent ergonomics and security \u0026 auth.\n\n### Do Validic Inform and Zus Health need an API key?\n\nValidic Inform needs an API key. Zus Health uses an OAuth sign-in.\n\n### Can an agent call Validic Inform and Zus Health without installing anything?\n\nNo hosted endpoint is listed for Validic Inform. No hosted endpoint is listed for Zus Health.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/validic-vs-zus-health.json, and with the fewest tokens: https://www.anchorterminal.com/compare/validic-vs-zus-health.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"validic\", \"b\": \"zus-health\"}`. From a terminal: `anchor compare validic zus-health`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/validic.json and https://www.anchorterminal.com/api/v1/tools/zus-health.json\n\n## Other comparisons with Validic Inform or Zus Health\n\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 Zus Health](https://www.anchorterminal.com/compare/1uphealth-vs-zus-health.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- [Aidbox vs Validic Inform](https://www.anchorterminal.com/compare/aidbox-vs-validic.md)\n- [Health Gorilla vs Validic Inform](https://www.anchorterminal.com/compare/health-gorilla-vs-validic.md)\n- [Medblocks vs Validic Inform](https://www.anchorterminal.com/compare/medblocks-vs-validic.md)\n- [Metriport Medical API vs Validic Inform](https://www.anchorterminal.com/compare/metriport-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- [ROOK vs Validic Inform](https://www.anchorterminal.com/compare/rook-vs-validic.md)\n- [Terra API vs Validic Inform](https://www.anchorterminal.com/compare/terra-vs-validic.md)\n- [Redox vs Zus Health](https://www.anchorterminal.com/compare/redox-vs-zus-health.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-14", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Validic Inform vs Zus Health", "url": "" } ], "description": "Validic Inform scores 57.9 (C) to Zus Health's 56.6 (C) for patient consent. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Validic Inform C 57.9", "Zus Health C 56.6", "scores" ], "h1": "Validic Inform vs Zus Health", "image": "https://www.anchorterminal.com/assets/og/compare-validic-vs-zus-health.png", "path": "/compare/validic-vs-zus-health", "published": "2026-10-01", "section": "tools", "title": "Validic Inform vs Zus Health for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/validic-vs-zus-health" }, "tokens": { "markdown": 2200, "slim": 630 }, "version": 1 }