{ "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": "Terra API scores 65.9 (B) on agent readiness against 1upHealth's 46.8 (D), and leads in 5 of 7 scored categories. 1upHealth leads on transparency \u0026 trust.", "b": { "slug": "terra", "name": "Terra API", "vendor": "Terra Enabling Developers Inc.", "vendorUrl": "https://tryterra.co", "kind": "http-api", "category": "health-data", "summary": "Terra's Unified API collects activity, sleep, body and nutrition data from 500+ wearables and health apps, normalises it into one schema and sends it by webhook or REST. An MCP server, Terra AI, lets agents read a connected user's data.", "url": "https://www.anchorterminal.com/tools/terra", "markdownUrl": "https://www.anchorterminal.com/tools/terra.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/terra.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/terra.json", "repo": "https://github.com/tryterra/openapi", "license": "Proprietary service under Terra's terms of service. The OpenAPI specs repository is Apache 2.0", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e", "packages": [ { "registry": "pypi", "name": "terra-python" }, { "registry": "npm", "name": "terra-api" }, { "registry": "npm", "name": "@tryterra/cli" } ], "auth": "mixed", "authNotes": "A self-serve dashboard account gives a dev-id and one x-api-key per environment, sent as headers to the Unified API and to Terra AI. The key has no scopes and can be rotated. The admin API and admin MCP server take personal access tokens with 26 scopes, lifetimes of 7 to 90 days and optional environment limits. The admin MCP server signs in by OAuth, and risky changes need approval in the dashboard. End users connect each wearable through Terra's widget, and Terra holds the provider tokens.", "pricing": "usage", "pricingNotes": "Quick Start from $499 a month includes 100,000 credits, then $0.005 a credit to 1,000,000 and $0.003 above. Sign-up asks for a plan and billing details, with a 30-day money-back guarantee and no free tier found. Testing and staging environments allow 50 users each. Enterprise is custom (checked 2026-10-14).", "priceSummary": "$499 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI specs or the pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": 6, "popularity": { "githubStars": null, "npmWeekly": 13061, "pypiWeekly": 10636, "asOf": "2026-10-14" }, "docsUrl": "https://docs.tryterra.co", "llmsTxt": "https://docs.tryterra.co/llms.txt", "openapi": "https://raw.githubusercontent.com/tryterra/openapi/master/dist/core/v2-bundled.yaml", "capabilities": [ "health.wearables", "health.consent", "health.fhir" ], "tags": [ "hosted", "wearables", "health-data", "mcp", "api-key", "openapi", "llms-txt", "webhooks", "status-page", "python", "typescript", "soc2", "hipaa" ], "lastRelease": "2026-10-13", "graded": true, "anchor": { "graded": true, "score": 65.9, "grade": "B", "agentReady": false, "rank": 327, "ranked": true, "rankOf": 1076, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 75, "payments": 20, "reliability": 67, "schema": 89, "security": 65, "transparency": 56 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Graded on the Unified API and the Terra AI MCP server. A public OpenAPI 3.1 spec, llms.txt, per-user rate limits with Retry-After, and scoped admin tokens with approvals. Access starts at $499 a month with billing details at sign-up, the data API key has no scopes, and API key requests failed for 2 hours 38 minutes on 7 August 2026.", "bestFor": "A fitness, wellness, insurance or research product whose users connect consumer wearables and apps, and an agent that needs to read one user's sleep, activity or body data through MCP.", "strengths": [ "Public OpenAPI 3.1 specs on GitHub under Apache 2.0, republished almost daily (spec version 2026.10.08.1 for the Unified API)", "Rate limits documented per user, with a Retry-After header and an X-Terra-RateLimit-Rule header naming the rule that fired", "Terra AI MCP server has six read tools that take explicit fields or select lists, so an agent fetches only the columns it needs", "Admin tokens carry 26 scopes, expire within 90 days, can be limited to environments, and risky changes need approval in the dashboard", "Credit prices are public, $0.005 a credit from 100,001 to 1,000,000 and $0.003 above, with 200 credits per active user a month" ], "weaknesses": [ "No free tier. Sign-up asks for a plan and billing details, and Quick Start starts at $499 a month with a 30-day money-back guarantee", "The Unified API key is one environment-wide x-api-key with no scopes, and Terra AI takes the same key", "status.tryterra.co shows REST requests failing with authorisation errors for 2 hours 38 minutes on 7 August 2026", "No SLA is published outside Enterprise contracts, and no idempotency keys were found for write endpoints", "The privacy policy, effective 20 April 2023, excludes end-user wearable data, and no public sub-processor list was found" ], "agentNotes": [ "Send dev-id and x-api-key headers on every Unified API and Terra AI call. A missing header returns 401 problem+json", "Keep each request window to 1,825 days or less and under 6,000 requested days per user an hour. On 429 with rule r2, wait Retry-After seconds", "Pass either fields or select to Terra AI tools, never both and never neither, or the call fails with a validation error", "Expect data by webhook after a user connects through the widget session. REST reads are for backfills and on-demand queries", "Use the Read only access level for the admin MCP server unless a change is needed. The MCP level can read API keys" ], "metrics": { "kind": "remote", "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": 65.9 } ], "editorialScores": { "ergonomics": 78, "maintenance": 75, "payments": 20, "reliability": 67, "schema": 89, "security": 65, "transparency": 42 }, "provenanceScore": 69 }, "connect": { "claudeCode": "claude mcp add --transport http terra-ai https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e --header \"dev-id: \u003cYOUR_DEV_ID\u003e\" --header \"x-api-key: \u003cYOUR_API_KEY\u003e\"", "config": { "mcpServers": { "terra-ai": { "headers": { "dev-id": "YOUR_DEV_ID", "x-api-key": "YOUR_API_KEY" }, "url": "https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e" } } } }, "letme": { "capability": "https://letme.dev/health.wearables", "tool": "https://letme.dev/terra" }, "area": "domain-data", "unitPrices": [ { "item": "Quick Start plan, 100,000 credits included", "unit": "month", "usd": 499, "note": "From price on tryterra.co/pricing, 2026-10-14" }, { "item": "Credit beyond the monthly allowance (100,001 to 1,000,000)", "unit": "credit", "usd": 0.005, "note": "$0.003 above 1,000,000 credits. An active user costs 200 credits a month" } ], "provenance": { "legalEntity": "Terra Enabling Developers Inc.", "domain": "tryterra.co", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://tryterra.co/terms-of-service", "privacy": "https://tryterra.co/privacy", "statusPage": "https://status.tryterra.co", "changelog": "https://docs.tryterra.co/changelog/2026/readme", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The terms of service, last updated 1 May 2026, are between the customer and Terra Enabling Developers Inc., a Delaware corporation. The privacy policy names a UK subsidiary, Terra Enabling Developers Ltd.", "The privacy policy (effective 20 April 2023) says it doesn't cover data collected from wearables about end users, and that processing takes place mainly in the United Kingdom.", "tryterra.co/.well-known/security.txt returns 404.", "RDAP for tryterra.co returned no registration date.", "API and MCP endpoints answer at access.tryterra.co, a tryterra.co subdomain." ], "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/terra.json", "live": { "slug": "terra", "probe": { "target": "https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e", "method": "get", "lastAt": "2026-10-14T09:42:10.210334836Z", "lastOk": true, "lastStatus": 401, "lastMs": 45, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 47, "p95ms24h": 126, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.tryterra.co", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-14T08:54:00.980823971Z" }, "updatedAt": "2026-10-14T09:42:10.210334836Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "1upHealth, Inc.", "b": "Terra Enabling Developers Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Pay per use", "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 Terra's terms of service. The OpenAPI specs repository is Apache 2.0", "name": "Licence" }, { "a": "none", "b": "6", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-13", "name": "Last release" }, { "a": "no date given", "b": "2026-05-01", "name": "Terms last updated" }, { "a": "2026-06-25", "b": "2023-04-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": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "13k npm/wk, 11k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Terra API scores 65.9 (B) on agent readiness against 1upHealth's 46.8 (D), and leads in 5 of 7 scored categories. 1upHealth leads on transparency \u0026 trust.", "question": "Which is better for AI agents, 1upHealth or Terra API?" }, { "answer": "1upHealth uses an OAuth sign-in. Terra API takes an API key or an OAuth sign-in.", "question": "Do 1upHealth and Terra API need an API key?" }, { "answer": "No hosted endpoint is listed for 1upHealth. Terra API has a hosted endpoint at https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e.", "question": "Can an agent call 1upHealth and Terra API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Transparency \u0026 trust, 72 against 56" ], "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, 67 against 52", "Schema \u0026 documentation, 89 against 50", "Agent ergonomics, 78 against 32", "Maintenance \u0026 community, 75 against 37" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "A fitness, wellness, insurance or research product whose users connect consumer wearables and apps, and an agent that needs to read one user's sleep, activity or body data through MCP.", "slug": "terra", "watchFor": "No free tier. Sign-up asks for a plan and billing details, and Quick Start starts at $499 a month with a 30-day money-back guarantee" } ], "job": { "capability": "health.fhir", "name": "FHIR servers" }, "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/aidbox-vs-terra.json", "title": "Aidbox vs Terra API", "url": "https://www.anchorterminal.com/compare/aidbox-vs-terra" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-terra.json", "title": "Health Gorilla vs Terra API", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-terra" }, { "json": "https://www.anchorterminal.com/compare/medplum-vs-terra.json", "title": "Medplum vs Terra API", "url": "https://www.anchorterminal.com/compare/medplum-vs-terra" }, { "json": "https://www.anchorterminal.com/compare/metriport-vs-terra.json", "title": "Metriport Medical API vs Terra API", "url": "https://www.anchorterminal.com/compare/metriport-vs-terra" }, { "json": "https://www.anchorterminal.com/compare/particle-health-vs-terra.json", "title": "Particle Health vs Terra API", "url": "https://www.anchorterminal.com/compare/particle-health-vs-terra" }, { "json": "https://www.anchorterminal.com/compare/redox-vs-terra.json", "title": "Redox vs Terra API", "url": "https://www.anchorterminal.com/compare/redox-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/1uphealth-vs-validic.json", "title": "1upHealth vs Validic Inform", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-validic" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-terra.json", "title": "Medblocks vs Terra API", "url": "https://www.anchorterminal.com/compare/medblocks-vs-terra" }, { "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-terra.json", "title": "ROOK vs Terra API", "url": "https://www.anchorterminal.com/compare/rook-vs-terra" }, { "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": 15, "edge": "terra", "key": "reliability", "name": "Reliability", "terra": 67, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "1uphealth": 50, "by": 39, "edge": "terra", "key": "schema", "name": "Schema \u0026 documentation", "terra": 89, "weight": 13 }, { "1uphealth": 32, "by": 46, "edge": "terra", "key": "ergonomics", "name": "Agent ergonomics", "terra": 78, "weight": 13 }, { "1uphealth": 63, "by": 2, "edge": "terra", "key": "security", "name": "Security \u0026 auth", "terra": 65, "weight": 14 }, { "1uphealth": 20, "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "terra": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "1uphealth": 37, "by": 38, "edge": "terra", "key": "maintenance", "name": "Maintenance \u0026 community", "terra": 75, "weight": 7 }, { "1uphealth": 72, "by": 16, "edge": "1uphealth", "key": "transparency", "name": "Transparency \u0026 trust", "terra": 56, "weight": 7 } ], "summary": "Terra API scores 65.9 (B) on agent readiness against 1upHealth's 46.8 (D), and leads in 5 of 7 scored categories. 1upHealth leads on transparency \u0026 trust. Both do fhir servers.", "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.", "terra": "Graded on the Unified API and the Terra AI MCP server. A public OpenAPI 3.1 spec, llms.txt, per-user rate limits with Retry-After, and scoped admin tokens with approvals. Access starts at $499 a month with billing details at sign-up, the data API key has no scopes, and API key requests failed for 2 hours 38 minutes on 7 August 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/1uphealth-vs-terra", "json": "https://www.anchorterminal.com/compare/1uphealth-vs-terra.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/1uphealth-vs-terra.md", "slim": "https://www.anchorterminal.com/compare/1uphealth-vs-terra.min.md" }, "markdown": "Terra API scores 65.9 (B) on agent readiness against 1upHealth's 46.8 (D), and leads in 5 of 7 scored categories. 1upHealth leads on transparency \u0026 trust. Both do fhir servers.\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- Terra API: grade B, 65.9/100, rank #327 of 1076. Markdown https://www.anchorterminal.com/tools/terra.md · JSON https://www.anchorterminal.com/api/v1/tools/terra.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 56\n\nWatch for: No rate limits, 429 handling or error formats documented\n\n### Terra API (B)\n\nGood for: A fitness, wellness, insurance or research product whose users connect consumer wearables and apps, and an agent that needs to read one user's sleep, activity or body data through MCP.\n\nAhead on:\n- Reliability, 67 against 52\n- Schema \u0026 documentation, 89 against 50\n- Agent ergonomics, 78 against 32\n- Maintenance \u0026 community, 75 against 37\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No free tier. Sign-up asks for a plan and billing details, and Quick Start starts at $499 a month with a 30-day money-back guarantee\n\n\n## Score by category\n\n| Category | Weight | 1upHealth | Terra API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 52 | 67 | Terra API +15 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 50 | 89 | Terra API +39 |\n| Agent ergonomics | 13% (16.2 this run) | 32 | 78 | Terra API +46 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 65 | Terra API +2 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 20 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 37 | 75 | Terra API +38 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 56 | 1upHealth +16 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **46.8 · D** | **65.9 · B** | |\n\n## Facts side by side\n\n| Fact | 1upHealth | Terra API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | 1upHealth, Inc. | Terra Enabling Developers Inc. |\n| Hosted endpoint | no (local only) | `https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Paid | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under 1upHealth's Terms of Service (effective 1 August 2024) | Proprietary service under Terra's terms of service. The OpenAPI specs repository is Apache 2.0 |\n| Tools exposed | none | 6 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-10-13 |\n| Terms last updated | no date given | 2026-05-01 |\n| Privacy policy last updated | 2026-06-25 | 2023-04-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 | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | none | 13k npm/wk, 11k PyPI/wk |\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**Terra API.** Graded on the Unified API and the Terra AI MCP server. A public OpenAPI 3.1 spec, llms.txt, per-user rate limits with Retry-After, and scoped admin tokens with approvals. Access starts at $499 a month with billing details at sign-up, the data API key has no scopes, and API key requests failed for 2 hours 38 minutes on 7 August 2026.\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### Terra API\n\n1. Send dev-id and x-api-key headers on every Unified API and Terra AI call. A missing header returns 401 problem+json\n2. Keep each request window to 1,825 days or less and under 6,000 requested days per user an hour. On 429 with rule r2, wait Retry-After seconds\n3. Pass either fields or select to Terra AI tools, never both and never neither, or the call fails with a validation error\n4. Expect data by webhook after a user connects through the widget session. REST reads are for backfills and on-demand queries\n5. Use the Read only access level for the admin MCP server unless a change is needed. The MCP level can read API keys\n\n## Questions\n\n### Which is better for AI agents, 1upHealth or Terra API?\n\nTerra API scores 65.9 (B) on agent readiness against 1upHealth's 46.8 (D), and leads in 5 of 7 scored categories. 1upHealth leads on transparency \u0026 trust.\n\n### Do 1upHealth and Terra API need an API key?\n\n1upHealth uses an OAuth sign-in. Terra API takes an API key or an OAuth sign-in.\n\n### Can an agent call 1upHealth and Terra API without installing anything?\n\nNo hosted endpoint is listed for 1upHealth. Terra API has a hosted endpoint at https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/1uphealth-vs-terra.json, and with the fewest tokens: https://www.anchorterminal.com/compare/1uphealth-vs-terra.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"1uphealth\", \"b\": \"terra\"}`. From a terminal: `anchor compare 1uphealth terra`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/1uphealth.json and https://www.anchorterminal.com/api/v1/tools/terra.json\n\n## Other comparisons with 1upHealth or Terra API\n\n- [1upHealth vs ROOK](https://www.anchorterminal.com/compare/1uphealth-vs-rook.md)\n- [Aidbox vs Terra API](https://www.anchorterminal.com/compare/aidbox-vs-terra.md)\n- [Health Gorilla vs Terra API](https://www.anchorterminal.com/compare/health-gorilla-vs-terra.md)\n- [Medplum vs Terra API](https://www.anchorterminal.com/compare/medplum-vs-terra.md)\n- [Metriport Medical API vs Terra API](https://www.anchorterminal.com/compare/metriport-vs-terra.md)\n- [Particle Health vs Terra API](https://www.anchorterminal.com/compare/particle-health-vs-terra.md)\n- [Redox vs Terra API](https://www.anchorterminal.com/compare/redox-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- [1upHealth vs Validic Inform](https://www.anchorterminal.com/compare/1uphealth-vs-validic.md)\n- [Medblocks vs Terra API](https://www.anchorterminal.com/compare/medblocks-vs-terra.md)\n- [Terra API vs Zus Health](https://www.anchorterminal.com/compare/terra-vs-zus-health.md)\n- [ROOK vs Terra API](https://www.anchorterminal.com/compare/rook-vs-terra.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 Terra API", "url": "" } ], "description": "Terra scores 65.9 (B) to 1upHealth's 46.8 (D) for fhir servers. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "1upHealth D 46.8", "Terra API B 65.9", "scores" ], "h1": "1upHealth vs Terra API", "image": "https://www.anchorterminal.com/assets/og/compare-1uphealth-vs-terra.png", "path": "/compare/1uphealth-vs-terra", "published": "2026-10-01", "section": "tools", "title": "1upHealth vs Terra for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-terra" }, "tokens": { "markdown": 2300, "slim": 680 }, "version": 1 }