{ "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:50:05.934939244Z" }, "updatedAt": "2026-10-14T09:50:05.934939244Z" } }, "answer": "Aidbox scores 64.2 (B) on agent readiness against 1upHealth's 46.8 (D), and leads in 6 of 7 scored categories. 1upHealth leads on transparency \u0026 trust.", "b": { "slug": "aidbox", "name": "Aidbox", "vendor": "Health Samurai, Inc.", "vendorUrl": "https://www.health-samurai.io/aidbox", "kind": "http-api", "category": "health-data", "summary": "FHIR R4 and R5 server on PostgreSQL from Health Samurai, run from Docker images under a free development licence or a paid production licence. Agents use each instance's FHIR REST API or its alpha MCP server.", "url": "https://www.anchorterminal.com/tools/aidbox", "markdownUrl": "https://www.anchorterminal.com/tools/aidbox.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/aidbox.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/aidbox.json", "repo": "https://github.com/Aidbox", "license": "Proprietary. Aidbox runs from Health Samurai's Docker images under a free development licence (no PHI) or a paid production licence. Examples and the Python SDK on GitHub are MIT", "transports": [ "http", "streamable-http", "sse" ], "packages": [ { "registry": "oci", "name": "healthsamurai/aidboxone" } ], "auth": "oauth", "authNotes": "Each instance has its own OAuth 2.0 server. Agents use a Client resource with the client credentials grant and POST to /auth/token, and SMART on FHIR backend services with private key JWT are supported. AccessPolicy resources decide what each client, user or operation may do, and access token lifetime is set per Client. Basic auth with the client ID and secret is also documented. The MCP endpoints are closed until an AccessPolicy opens them.", "pricing": "freemium", "pricingNotes": "Aidbox Dev is $0 for development and testing with no PHI, Aidbox Base from $1,900 a month or $19,000 a year, Enterprise by contact (health-samurai.io/price, checked 2026-10-14). A production licence runs 14 days as a trial before Health Samurai extends it. A free hosted sandbox on Google Cloud comes with an aidbox.app account. Whether sign-up asks for a card was not established.", "priceSummary": "$1900 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs or pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://www.health-samurai.io/docs/aidbox", "llmsTxt": "https://www.health-samurai.io/docs/aidbox/llms.txt", "capabilities": [ "health.fhir", "health.records", "health.consent" ], "tags": [ "self-hosted", "fhir", "mcp", "oauth", "smart-on-fhir", "docker", "postgresql", "llms-txt", "iso27001" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 64.2, "grade": "B", "agentReady": false, "rank": 385, "ranked": true, "rankOf": 1076, "categoryRank": 3, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 80, "payments": 25, "reliability": 59, "schema": 77, "security": 74, "transparency": 45 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Graded on the FHIR REST API of an Aidbox instance the owner runs. Monthly releases, two-year LTS lines, SMART on FHIR, AccessPolicy rules and AuditEvent logging are documented, and a free development licence needs no sales call. Aidbox has no rate limiting of its own, its MCP module is alpha, and no terms of service were found on the website.", "bestFor": "An organisation building its own clinical data repository, EHR or payer platform on FHIR, where an agent works against that store.", "strengths": [ "Monthly releases with dated notes, the latest 2609 on 8 October 2026, and LTS lines supported for two years", "SMART on FHIR backend services, client credentials and AccessPolicy rules per client, user or operation", "AuditEvent recording and an audit event topic that can forward to an external repository", "Free development licence and hosted sandbox, with Base pricing published from $1,900 a month", "Cosign-signed images, SBOMs per release and remediation deadlines from 7 days for critical vulnerabilities" ], "weaknesses": [ "No built-in rate limiting or brute-force protection, by the vendor's hardening page", "The MCP module is alpha, its tools take whole resources as free JSON, and no tool annotations are documented", "No terms of service or licence agreement was found on the website, and the privacy policy dates from 10 June 2021", "Closed source with no public CI and no OpenAPI document", "No public status page, security.txt or sub-processor list was found" ], "agentNotes": [ "Ask the operator for a Client with an AccessPolicy limited to the task. Don't rely on the public MCP policy, which the docs mark unsafe", "Use `If-None-Exist` on creates and conditional update on identifiers so retries don't duplicate records", "Use `_elements` and `_count` to keep responses small, and follow the Bundle's paging links", "Throttle yourself. Aidbox applies no rate limit, so a burst lands on the customer's database", "Don't load real patient data into an instance on a development licence" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.2 } ], "editorialScores": { "ergonomics": 79, "maintenance": 80, "payments": 25, "reliability": 59, "schema": 77, "security": 74, "transparency": 51 }, "provenanceScore": 39 }, "connect": { "install": "curl -JO https://aidbox.app/runme \u0026\u0026 docker compose up" }, "letme": { "capability": "https://letme.dev/health.fhir", "tool": "https://letme.dev/aidbox" }, "area": "domain-data", "unitPrices": [ { "item": "Aidbox Base licence", "unit": "month", "usd": 1900, "note": "From price, monthly billing. $19,000 a year on yearly billing" } ], "provenance": { "legalEntity": "Health Samurai, Inc.", "domain": "health-samurai.io", "domainRegistered": "", "endpointOnVendorDomain": false, "terms": "", "privacy": "https://www.health-samurai.io/legal/privacy-policy", "statusPage": "", "changelog": "https://www.health-samurai.io/docs/aidbox/overview/release-notes", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The site footer and privacy policy name Health Samurai, Inc. The privacy policy was last updated on 10 June 2021 and refers to Terms of Use that were not found.", "No terms of service or licence agreement was found at /legal or in the docs.", "www.health-samurai.io/.well-known/security.txt returns a 404 page. The supply chain page sends reports to security@health-samurai.io.", "Aidbox runs on the customer's infrastructure, so endpoints are on the customer's domain. The free sandbox runs on aidbox.app subdomains.", "No public status page was found. The domain registration date was not established." ], "score": 39 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/aidbox.json" }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "1upHealth, Inc.", "b": "Health Samurai, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, SSE (legacy)", "name": "Transports" }, { "a": "OAuth", "b": "OAuth", "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. Aidbox runs from Health Samurai's Docker images under a free development licence (no PHI) or a paid production licence. Examples and the Python SDK on GitHub are MIT", "name": "Licence" }, { "a": "none", "b": "9", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-08", "name": "Last release" }, { "a": "no date given", "b": "no document linked", "name": "Terms last updated" }, { "a": "2026-06-25", "b": "2021-06-10", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "yes", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Aidbox scores 64.2 (B) on agent readiness against 1upHealth's 46.8 (D), and leads in 6 of 7 scored categories. 1upHealth leads on transparency \u0026 trust.", "question": "Which is better for AI agents, 1upHealth or Aidbox?" }, { "answer": "Both use an OAuth sign-in.", "question": "Do 1upHealth and Aidbox need an API key?" }, { "answer": "No hosted endpoint is listed for 1upHealth. No hosted endpoint is listed for Aidbox.", "question": "Can an agent call 1upHealth and Aidbox without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Transparency \u0026 trust, 72 against 45" ], "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, 59 against 52", "Schema \u0026 documentation, 77 against 50", "Agent ergonomics, 79 against 32", "Security \u0026 auth, 74 against 63", "Payments \u0026 pricing, 25 against 20", "Maintenance \u0026 community, 80 against 37" ], "also": null, "goodFor": "An organisation building its own clinical data repository, EHR or payer platform on FHIR, where an agent works against that store.", "slug": "aidbox", "watchFor": "No built-in rate limiting or brute-force protection, by the vendor's hardening page" } ], "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-health-gorilla.json", "title": "Aidbox vs Health Gorilla", "url": "https://www.anchorterminal.com/compare/aidbox-vs-health-gorilla" }, { "json": "https://www.anchorterminal.com/compare/aidbox-vs-medblocks.json", "title": "Aidbox vs Medblocks", "url": "https://www.anchorterminal.com/compare/aidbox-vs-medblocks" }, { "json": "https://www.anchorterminal.com/compare/aidbox-vs-medplum.json", "title": "Aidbox vs Medplum", "url": "https://www.anchorterminal.com/compare/aidbox-vs-medplum" }, { "json": "https://www.anchorterminal.com/compare/aidbox-vs-metriport.json", "title": "Aidbox vs Metriport Medical API", "url": "https://www.anchorterminal.com/compare/aidbox-vs-metriport" }, { "json": "https://www.anchorterminal.com/compare/aidbox-vs-particle-health.json", "title": "Aidbox vs Particle Health", "url": "https://www.anchorterminal.com/compare/aidbox-vs-particle-health" }, { "json": "https://www.anchorterminal.com/compare/aidbox-vs-redox.json", "title": "Aidbox vs Redox", "url": "https://www.anchorterminal.com/compare/aidbox-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/aidbox-vs-rook.json", "title": "Aidbox vs ROOK", "url": "https://www.anchorterminal.com/compare/aidbox-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/aidbox-vs-terra.json", "title": "Aidbox vs Terra API", "url": "https://www.anchorterminal.com/compare/aidbox-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/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/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" } ], "scores": [ { "1uphealth": 52, "aidbox": 59, "by": 7, "edge": "aidbox", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "1uphealth": 50, "aidbox": 77, "by": 27, "edge": "aidbox", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "1uphealth": 32, "aidbox": 79, "by": 47, "edge": "aidbox", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "1uphealth": 63, "aidbox": 74, "by": 11, "edge": "aidbox", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "1uphealth": 20, "aidbox": 25, "by": 5, "edge": "aidbox", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "1uphealth": 37, "aidbox": 80, "by": 43, "edge": "aidbox", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "1uphealth": 72, "aidbox": 45, "by": 27, "edge": "1uphealth", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Aidbox scores 64.2 (B) on agent readiness against 1upHealth's 46.8 (D), and leads in 6 of 7 scored categories. 1upHealth leads on 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.", "aidbox": "Graded on the FHIR REST API of an Aidbox instance the owner runs. Monthly releases, two-year LTS lines, SMART on FHIR, AccessPolicy rules and AuditEvent logging are documented, and a free development licence needs no sales call. Aidbox has no rate limiting of its own, its MCP module is alpha, and no terms of service were found on the website." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/1uphealth-vs-aidbox", "json": "https://www.anchorterminal.com/compare/1uphealth-vs-aidbox.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/1uphealth-vs-aidbox.md", "slim": "https://www.anchorterminal.com/compare/1uphealth-vs-aidbox.min.md" }, "markdown": "Aidbox scores 64.2 (B) on agent readiness against 1upHealth's 46.8 (D), and leads in 6 of 7 scored categories. 1upHealth leads on transparency \u0026 trust. Both do patient record retrieval.\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- Aidbox: grade B, 64.2/100, rank #385 of 1076. Markdown https://www.anchorterminal.com/tools/aidbox.md · JSON https://www.anchorterminal.com/api/v1/tools/aidbox.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- Transparency \u0026 trust, 72 against 45\n\nWatch for: No rate limits, 429 handling or error formats documented\n\n### Aidbox (B)\n\nGood for: An organisation building its own clinical data repository, EHR or payer platform on FHIR, where an agent works against that store.\n\nAhead on:\n- Reliability, 59 against 52\n- Schema \u0026 documentation, 77 against 50\n- Agent ergonomics, 79 against 32\n- Security \u0026 auth, 74 against 63\n- Payments \u0026 pricing, 25 against 20\n- Maintenance \u0026 community, 80 against 37\n\nWatch for: No built-in rate limiting or brute-force protection, by the vendor's hardening page\n\n\n## Score by category\n\n| Category | Weight | 1upHealth | Aidbox | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 52 | 59 | Aidbox +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 50 | 77 | Aidbox +27 |\n| Agent ergonomics | 13% (16.2 this run) | 32 | 79 | Aidbox +47 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 74 | Aidbox +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 25 | Aidbox +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 37 | 80 | Aidbox +43 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 45 | 1upHealth +27 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **46.8 · D** | **64.2 · B** | |\n\n## Facts side by side\n\n| Fact | 1upHealth | Aidbox |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | 1upHealth, Inc. | Health Samurai, Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP, Streamable HTTP, SSE (legacy) |\n| Auth | OAuth | OAuth |\n| Pricing | Paid | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under 1upHealth's Terms of Service (effective 1 August 2024) | Proprietary. Aidbox runs from Health Samurai's Docker images under a free development licence (no PHI) or a paid production licence. Examples and the Python SDK on GitHub are MIT |\n| Tools exposed | none | 9 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-10-08 |\n| Terms last updated | no date given | no document linked |\n| Privacy policy last updated | 2026-06-25 | 2021-06-10 |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | yes | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | 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**Aidbox.** Graded on the FHIR REST API of an Aidbox instance the owner runs. Monthly releases, two-year LTS lines, SMART on FHIR, AccessPolicy rules and AuditEvent logging are documented, and a free development licence needs no sales call. Aidbox has no rate limiting of its own, its MCP module is alpha, and no terms of service were found on the website.\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### Aidbox\n\n1. Ask the operator for a Client with an AccessPolicy limited to the task. Don't rely on the public MCP policy, which the docs mark unsafe\n2. Use `If-None-Exist` on creates and conditional update on identifiers so retries don't duplicate records\n3. Use `_elements` and `_count` to keep responses small, and follow the Bundle's paging links\n4. Throttle yourself. Aidbox applies no rate limit, so a burst lands on the customer's database\n5. Don't load real patient data into an instance on a development licence\n\n## Questions\n\n### Which is better for AI agents, 1upHealth or Aidbox?\n\nAidbox scores 64.2 (B) on agent readiness against 1upHealth's 46.8 (D), and leads in 6 of 7 scored categories. 1upHealth leads on transparency \u0026 trust.\n\n### Do 1upHealth and Aidbox need an API key?\n\nBoth use an OAuth sign-in.\n\n### Can an agent call 1upHealth and Aidbox without installing anything?\n\nNo hosted endpoint is listed for 1upHealth. No hosted endpoint is listed for Aidbox.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/1uphealth-vs-aidbox.json, and with the fewest tokens: https://www.anchorterminal.com/compare/1uphealth-vs-aidbox.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"1uphealth\", \"b\": \"aidbox\"}`. From a terminal: `anchor compare 1uphealth aidbox`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/1uphealth.json and https://www.anchorterminal.com/api/v1/tools/aidbox.json\n\n## Other comparisons with 1upHealth or Aidbox\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 Health Gorilla](https://www.anchorterminal.com/compare/aidbox-vs-health-gorilla.md)\n- [Aidbox vs Medblocks](https://www.anchorterminal.com/compare/aidbox-vs-medblocks.md)\n- [Aidbox vs Medplum](https://www.anchorterminal.com/compare/aidbox-vs-medplum.md)\n- [Aidbox vs Metriport Medical API](https://www.anchorterminal.com/compare/aidbox-vs-metriport.md)\n- [Aidbox vs Particle Health](https://www.anchorterminal.com/compare/aidbox-vs-particle-health.md)\n- [Aidbox vs Redox](https://www.anchorterminal.com/compare/aidbox-vs-redox.md)\n- [Aidbox vs ROOK](https://www.anchorterminal.com/compare/aidbox-vs-rook.md)\n- [Aidbox vs Terra API](https://www.anchorterminal.com/compare/aidbox-vs-terra.md)\n- [Aidbox vs Zus Health](https://www.anchorterminal.com/compare/aidbox-vs-zus-health.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- [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", "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 Aidbox", "url": "" } ], "description": "Aidbox scores 64.2 (B) 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", "Aidbox B 64.2", "scores" ], "h1": "1upHealth vs Aidbox", "image": "https://www.anchorterminal.com/assets/og/compare-1uphealth-vs-aidbox.png", "path": "/compare/1uphealth-vs-aidbox", "published": "2026-10-01", "section": "tools", "title": "1upHealth vs Aidbox for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-aidbox" }, "tokens": { "markdown": 2200, "slim": 680 }, "version": 1 }