{ "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": 903, "ranked": true, "rankOf": 1076, "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": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:38:50.511902685Z" }, "updatedAt": "2026-10-14T09:38:50.511902685Z" } }, "answer": "Validic Inform scores 57.9 (C) on agent readiness against 1upHealth's 46.8 (D), and leads in 5 of 7 scored categories. 1upHealth leads on security \u0026 auth.", "b": { "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" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "1upHealth, Inc.", "b": "Validic, Inc. (ChartSpan)", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, SSE (legacy)", "name": "Transports" }, { "a": "OAuth", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "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 Validic's Online Service Agreement for Inform (last updated 13 August 2025). The inform-quickstart sample apps are MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-12", "name": "Last release" }, { "a": "no date given", "b": "2025-08-13", "name": "Terms last updated" }, { "a": "2026-06-25", "b": "2026-01-20", "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": "yes", "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 1upHealth's 46.8 (D), and leads in 5 of 7 scored categories. 1upHealth leads on security \u0026 auth.", "question": "Which is better for AI agents, 1upHealth or Validic Inform?" }, { "answer": "1upHealth uses an OAuth sign-in. Validic Inform needs an API key.", "question": "Do 1upHealth and Validic Inform need an API key?" }, { "answer": "No hosted endpoint is listed for 1upHealth. No hosted endpoint is listed for Validic Inform.", "question": "Can an agent call 1upHealth and Validic Inform without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 63 against 30" ], "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, 73 against 52", "Schema \u0026 documentation, 75 against 50", "Agent ergonomics, 50 against 32", "Payments \u0026 pricing, 40 against 20", "Maintenance \u0026 community, 74 against 37" ], "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" } ], "job": { "capability": "health.consent", "name": "Patient consent" }, "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/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/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/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/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/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" } ], "scores": [ { "1uphealth": 52, "by": 21, "edge": "validic", "key": "reliability", "name": "Reliability", "validic": 73, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "1uphealth": 50, "by": 25, "edge": "validic", "key": "schema", "name": "Schema \u0026 documentation", "validic": 75, "weight": 13 }, { "1uphealth": 32, "by": 18, "edge": "validic", "key": "ergonomics", "name": "Agent ergonomics", "validic": 50, "weight": 13 }, { "1uphealth": 63, "by": 33, "edge": "1uphealth", "key": "security", "name": "Security \u0026 auth", "validic": 30, "weight": 14 }, { "1uphealth": 20, "by": 20, "edge": "validic", "key": "payments", "name": "Payments \u0026 pricing", "validic": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "1uphealth": 37, "by": 37, "edge": "validic", "key": "maintenance", "name": "Maintenance \u0026 community", "validic": 74, "weight": 7 }, { "1uphealth": 72, "by": 1, "edge": "1uphealth", "key": "transparency", "name": "Transparency \u0026 trust", "validic": 71, "weight": 7 } ], "summary": "Validic Inform scores 57.9 (C) on agent readiness against 1upHealth's 46.8 (D), and leads in 5 of 7 scored categories. 1upHealth leads on security \u0026 auth. Both do patient consent.", "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.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/1uphealth-vs-validic", "json": "https://www.anchorterminal.com/compare/1uphealth-vs-validic.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/1uphealth-vs-validic.md", "slim": "https://www.anchorterminal.com/compare/1uphealth-vs-validic.min.md" }, "markdown": "Validic Inform scores 57.9 (C) on agent readiness against 1upHealth's 46.8 (D), and leads in 5 of 7 scored categories. 1upHealth leads on security \u0026 auth. Both do patient consent.\n\n- 1upHealth: grade D, 46.8/100, rank #903 of 1076. Markdown https://www.anchorterminal.com/tools/1uphealth.md · JSON https://www.anchorterminal.com/api/v1/tools/1uphealth.json\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- 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 30\n\nWatch for: No rate limits, 429 handling or error formats documented\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 52\n- Schema \u0026 documentation, 75 against 50\n- Agent ergonomics, 50 against 32\n- Payments \u0026 pricing, 40 against 20\n- Maintenance \u0026 community, 74 against 37\n\nWatch for: The organisation token is sent as `?token=` in the URL, the only documented option\n\n\n## Score by category\n\n| Category | Weight | 1upHealth | Validic Inform | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 52 | 73 | Validic Inform +21 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 50 | 75 | Validic Inform +25 |\n| Agent ergonomics | 13% (16.2 this run) | 32 | 50 | Validic Inform +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 30 | 1upHealth +33 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 40 | Validic Inform +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 37 | 74 | Validic Inform +37 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 71 | 1upHealth +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **46.8 · D** | **57.9 · C** | |\n\n## Facts side by side\n\n| Fact | 1upHealth | Validic Inform |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | 1upHealth, Inc. | Validic, Inc. (ChartSpan) |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP, SSE (legacy) |\n| Auth | OAuth | API key |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under 1upHealth's Terms of Service (effective 1 August 2024) | Proprietary service under Validic's Online Service Agreement for Inform (last updated 13 August 2025). The inform-quickstart sample apps are MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-10-12 |\n| Terms last updated | no date given | 2025-08-13 |\n| Privacy policy last updated | 2026-06-25 | 2026-01-20 |\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 | yes |\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**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## 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### 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## Questions\n\n### Which is better for AI agents, 1upHealth or Validic Inform?\n\nValidic Inform scores 57.9 (C) on agent readiness against 1upHealth's 46.8 (D), and leads in 5 of 7 scored categories. 1upHealth leads on security \u0026 auth.\n\n### Do 1upHealth and Validic Inform need an API key?\n\n1upHealth uses an OAuth sign-in. Validic Inform needs an API key.\n\n### Can an agent call 1upHealth and Validic Inform without installing anything?\n\nNo hosted endpoint is listed for 1upHealth. No hosted endpoint is listed for Validic Inform.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/1uphealth-vs-validic.json, and with the fewest tokens: https://www.anchorterminal.com/compare/1uphealth-vs-validic.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"1uphealth\", \"b\": \"validic\"}`. From a terminal: `anchor compare 1uphealth validic`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/1uphealth.json and https://www.anchorterminal.com/api/v1/tools/validic.json\n\n## Other comparisons with 1upHealth or Validic Inform\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- [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- [1upHealth vs Zus Health](https://www.anchorterminal.com/compare/1uphealth-vs-zus-health.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- [Validic Inform vs Zus Health](https://www.anchorterminal.com/compare/validic-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", "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": "1upHealth vs Validic Inform", "url": "" } ], "description": "Validic Inform scores 57.9 (C) to 1upHealth's 46.8 (D) for patient consent. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "1upHealth D 46.8", "Validic Inform C 57.9", "scores" ], "h1": "1upHealth vs Validic Inform", "image": "https://www.anchorterminal.com/assets/og/compare-1uphealth-vs-validic.png", "path": "/compare/1uphealth-vs-validic", "published": "2026-10-01", "section": "tools", "title": "1upHealth vs Validic Inform for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-validic" }, "tokens": { "markdown": 2150, "slim": 630 }, "version": 1 }