{
  "data": {
    "a": {
      "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"
      }
    },
    "answer": "Terra API scores 65.9 (B) on agent readiness against Zus Health's 56.6 (C), and leads in 6 of 7 scored categories.",
    "b": {
      "slug": "zus-health",
      "name": "Zus Health",
      "vendor": "Zus Health, Inc.",
      "vendorUrl": "https://www.zushealth.com",
      "kind": "http-api",
      "category": "health-data",
      "summary": "Zus Health assembles a patient's history from CommonWell, Carequality, Surescripts, Quest and ADT networks into the Zus Aggregated Profile, and exposes it through FHIR R4 REST, GraphQL and webhook APIs for care organisations it onboards.",
      "url": "https://www.anchorterminal.com/tools/zus-health",
      "markdownUrl": "https://www.anchorterminal.com/tools/zus-health.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/zus-health.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/zus-health.json",
      "license": "Proprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum",
      "transports": [
        "http"
      ],
      "packages": [],
      "auth": "oauth",
      "authNotes": "OAuth 2.0 bearer tokens valid for one hour. Backend systems use machine-to-machine App Clients created in the Zus app or through the Auth Service API, limited to 200 token requests an hour per client. Apps can exchange an OIDC ID token from their own identity provider for a Zus token, and integration App Clients with the Builder Data Integration role can fetch tokens for users through the proxy-token endpoint. Accounts are provisioned by Zus, with an initial admin per customer.",
      "pricing": "paid",
      "pricingNotes": "No public prices. The Builder Terms set fees in an executed Order Form or pricing list, invoiced monthly. A developer sandbox is requested through a Google Form on the docs site, and its cost is not stated (checked 2026-10-14).",
      "priceSummary": "Paid",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the documentation, llms.txt or the Builder Terms (checked 2026-10-14).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-14"
      },
      "docsUrl": "https://docs.zushealth.com",
      "llmsTxt": "https://docs.zushealth.com/llms.txt",
      "capabilities": [
        "health.records",
        "health.fhir",
        "health.ehr",
        "health.consent"
      ],
      "tags": [
        "hosted",
        "health-records",
        "fhir",
        "graphql",
        "oauth",
        "llms-txt",
        "webhooks",
        "status-page",
        "sla",
        "sales-led"
      ],
      "lastRelease": "2026-10-14",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 56.6,
        "grade": "C",
        "agentReady": false,
        "rank": 669,
        "ranked": true,
        "rankOf": 1076,
        "categoryRank": 7,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 67,
          "maintenance": 64,
          "payments": 5,
          "reliability": 66,
          "schema": 77,
          "security": 49,
          "transparency": 59
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-14"
        },
        "negative": 0,
        "verdict": "FHIR R4 over an aggregated patient profile drawn from CommonWell, Carequality, Surescripts, Quest and ADT networks, with published rate limits, a 99.5 per cent SLA and a dated changelog. Accounts and sandboxes are provisioned by Zus on request, with no public prices, no named security certification and no SDK.",
        "bestFor": "US care organisations and digital health builders that want a shared, continuously refreshed patient profile in FHIR with EHR embedding.",
        "strengths": [
          "One profile per patient from EHR, pharmacy, ADT and lab networks, shared across Zus customers treating the same patient",
          "Rate limits with numbers and a published 99.5 per cent SLA with credits",
          "Conditional writes by identifier and `Zus-If-Match` version checks for safe retries",
          "Dated changelog that announces changes ahead, such as the proxy-token role change on 14 October 2026"
        ],
        "weaknesses": [
          "No public prices, and the sandbox is requested through a Google Form",
          "Four major incidents on the status page between 27 July and 13 August 2026",
          "No named security certification, security.txt or bug bounty",
          "The GraphQL API is beta and no official SDK exists"
        ],
        "agentNotes": [
          "Cache the access token for its hour. More than 200 token requests an hour per App Client returns 429",
          "Request Patient History at most once per patient per 24 hours, and poll the job status endpoint",
          "Use conditional create by identifier so a retried write doesn't duplicate a resource",
          "Send `Zus-If-Match` with the resource's ETag on PUT and PATCH",
          "Set `_count` up to 500 on searches, since the default page is 10"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 56.6
          }
        ],
        "editorialScores": {
          "ergonomics": 67,
          "maintenance": 64,
          "payments": 5,
          "reliability": 66,
          "schema": 77,
          "security": 49,
          "transparency": 46
        },
        "provenanceScore": 71
      },
      "connect": {
        "http": "GET https://api.sandbox.zusapi.com/fhir/Patient?_count=50\nAuthorization: Bearer \u003caccess-token\u003e"
      },
      "letme": {
        "capability": "https://letme.dev/health.records",
        "tool": "https://letme.dev/zus-health"
      },
      "area": "domain-data",
      "provenance": {
        "legalEntity": "Zus Health, Inc.",
        "domain": "zushealth.com",
        "domainRegistered": "2012-02-25",
        "endpointOnVendorDomain": false,
        "terms": "https://www.zushealth.com/builder-terms-of-service",
        "privacy": "https://www.zushealth.com/privacy-policy",
        "statusPage": "https://status.zusapi.com",
        "changelog": "https://docs.zushealth.com/changelog",
        "securityTxt": "none",
        "checked": "2026-10-14",
        "notes": [
          "The APIs answer on zusapi.com, a separate domain from zushealth.com.",
          "The Builder Terms (last updated 11 March 2025) put term changes into effect 30 days after posting and BAA changes after 90 days. The Developer Sandbox Terms (22 January 2024) limit the sandbox to test data. The website lists 1 Lincoln Street, Suite 2900, Boston, MA 02111.",
          "The privacy policy (last updated 24 June 2026) covers the website only and names Google Analytics.",
          "The Builder Security Policy (11 March 2025) names no certification and makes a summary of an annual third-party audit available on request.",
          "www.zushealth.com/.well-known/security.txt returns 404.",
          "RDAP gives zushealth.com a registration date of 2012-02-25."
        ],
        "score": 71
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/zus-health.json",
      "live": {
        "slug": "zus-health",
        "vendorStatus": {
          "page": "https://status.zusapi.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-14T08:54:10.020449939Z"
        },
        "updatedAt": "2026-10-14T08:54:10.020449939Z"
      }
    },
    "facts": [
      {
        "a": "HTTP API",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Terra Enabling Developers Inc.",
        "b": "Zus Health, Inc.",
        "name": "Vendor"
      },
      {
        "a": "https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "HTTP, Streamable HTTP",
        "b": "HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary service under Terra's terms of service. The OpenAPI specs repository is Apache 2.0",
        "b": "Proprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum",
        "name": "Licence"
      },
      {
        "a": "6",
        "b": "none",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "2026-10-13",
        "b": "2026-10-14",
        "name": "Last release"
      },
      {
        "a": "2026-05-01",
        "b": "2025-03-11",
        "name": "Terms last updated"
      },
      {
        "a": "2023-04-20",
        "b": "2026-06-24",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "yes",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "13k npm/wk, 11k PyPI/wk",
        "b": "none",
        "name": "Popularity"
      }
    ],
    "faq": [
      {
        "answer": "Terra API scores 65.9 (B) on agent readiness against Zus Health's 56.6 (C), and leads in 6 of 7 scored categories.",
        "question": "Which is better for AI agents, Terra API or Zus Health?"
      },
      {
        "answer": "Terra API takes an API key or an OAuth sign-in. Zus Health uses an OAuth sign-in.",
        "question": "Do Terra API and Zus Health need an API key?"
      },
      {
        "answer": "Terra API has a hosted endpoint at https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e. No hosted endpoint is listed for Zus Health.",
        "question": "Can an agent call Terra API and Zus Health without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 89 against 77",
          "Agent ergonomics, 78 against 67",
          "Security \u0026 auth, 65 against 49",
          "Payments \u0026 pricing, 20 against 5",
          "Maintenance \u0026 community, 75 against 64"
        ],
        "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"
      },
      {
        "aheadOn": null,
        "also": null,
        "goodFor": "US care organisations and digital health builders that want a shared, continuously refreshed patient profile in FHIR with EHR embedding.",
        "slug": "zus-health",
        "watchFor": "No public prices, and the sandbox is requested through a Google Form"
      }
    ],
    "job": {
      "capability": "health.consent",
      "name": "Patient consent"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/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-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/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/medplum-vs-zus-health.json",
        "title": "Medplum vs Zus Health",
        "url": "https://www.anchorterminal.com/compare/medplum-vs-zus-health"
      },
      {
        "json": "https://www.anchorterminal.com/compare/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-zus-health.json",
        "title": "1upHealth vs Zus Health",
        "url": "https://www.anchorterminal.com/compare/1uphealth-vs-zus-health"
      },
      {
        "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-zus-health.json",
        "title": "Health Gorilla vs Zus Health",
        "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-zus-health"
      },
      {
        "json": "https://www.anchorterminal.com/compare/medblocks-vs-zus-health.json",
        "title": "Medblocks vs Zus Health",
        "url": "https://www.anchorterminal.com/compare/medblocks-vs-zus-health"
      },
      {
        "json": "https://www.anchorterminal.com/compare/metriport-vs-zus-health.json",
        "title": "Metriport Medical API vs Zus Health",
        "url": "https://www.anchorterminal.com/compare/metriport-vs-zus-health"
      },
      {
        "json": "https://www.anchorterminal.com/compare/particle-health-vs-zus-health.json",
        "title": "Particle Health vs Zus Health",
        "url": "https://www.anchorterminal.com/compare/particle-health-vs-zus-health"
      },
      {
        "json": "https://www.anchorterminal.com/compare/medblocks-vs-terra.json",
        "title": "Medblocks vs Terra API",
        "url": "https://www.anchorterminal.com/compare/medblocks-vs-terra"
      },
      {
        "json": "https://www.anchorterminal.com/compare/rook-vs-zus-health.json",
        "title": "ROOK vs Zus Health",
        "url": "https://www.anchorterminal.com/compare/rook-vs-zus-health"
      },
      {
        "json": "https://www.anchorterminal.com/compare/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-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"
      },
      {
        "json": "https://www.anchorterminal.com/compare/redox-vs-zus-health.json",
        "title": "Redox vs Zus Health",
        "url": "https://www.anchorterminal.com/compare/redox-vs-zus-health"
      }
    ],
    "scores": [
      {
        "by": 1,
        "edge": "terra",
        "key": "reliability",
        "name": "Reliability",
        "terra": 67,
        "weight": 16,
        "zus-health": 66
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 12,
        "edge": "terra",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "terra": 89,
        "weight": 13,
        "zus-health": 77
      },
      {
        "by": 11,
        "edge": "terra",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "terra": 78,
        "weight": 13,
        "zus-health": 67
      },
      {
        "by": 16,
        "edge": "terra",
        "key": "security",
        "name": "Security \u0026 auth",
        "terra": 65,
        "weight": 14,
        "zus-health": 49
      },
      {
        "by": 15,
        "edge": "terra",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "terra": 20,
        "weight": 10,
        "zus-health": 5
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 11,
        "edge": "terra",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "terra": 75,
        "weight": 7,
        "zus-health": 64
      },
      {
        "by": 3,
        "edge": "zus-health",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "terra": 56,
        "weight": 7,
        "zus-health": 59
      }
    ],
    "summary": "Terra API scores 65.9 (B) on agent readiness against Zus Health's 56.6 (C), and leads in 6 of 7 scored categories. Both do patient consent.",
    "verdicts": {
      "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.",
      "zus-health": "FHIR R4 over an aggregated patient profile drawn from CommonWell, Carequality, Surescripts, Quest and ADT networks, with published rate limits, a 99.5 per cent SLA and a dated changelog. Accounts and sandboxes are provisioned by Zus on request, with no public prices, no named security certification and no SDK."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/terra-vs-zus-health",
    "json": "https://www.anchorterminal.com/compare/terra-vs-zus-health.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/terra-vs-zus-health.md",
    "slim": "https://www.anchorterminal.com/compare/terra-vs-zus-health.min.md"
  },
  "markdown": "Terra API scores 65.9 (B) on agent readiness against Zus Health's 56.6 (C), and leads in 6 of 7 scored categories. Both do patient consent.\n\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- Zus Health: grade C, 56.6/100, rank #669 of 1076. Markdown https://www.anchorterminal.com/tools/zus-health.md · JSON https://www.anchorterminal.com/api/v1/tools/zus-health.json\n- Best health record and wellness data APIs for AI agents: https://www.anchorterminal.com/best/health-data/index.md\n- All 63 health comparisons: https://www.anchorterminal.com/compare/health-data/index.md\n\n## Which one, for what\n\n### 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- Schema \u0026 documentation, 89 against 77\n- Agent ergonomics, 78 against 67\n- Security \u0026 auth, 65 against 49\n- Payments \u0026 pricing, 20 against 5\n- Maintenance \u0026 community, 75 against 64\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### Zus Health (C)\n\nGood for: US care organisations and digital health builders that want a shared, continuously refreshed patient profile in FHIR with EHR embedding.\n\nWatch for: No public prices, and the sandbox is requested through a Google Form\n\n\n## Score by category\n\n| Category | Weight | Terra API | Zus Health | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 67 | 66 | Terra API +1 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 89 | 77 | Terra API +12 |\n| Agent ergonomics | 13% (16.2 this run) | 78 | 67 | Terra API +11 |\n| Security \u0026 auth | 14% (17.5 this run) | 65 | 49 | Terra API +16 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 5 | Terra API +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 64 | Terra API +11 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 56 | 59 | Zus Health +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **65.9 · B** | **56.6 · C** | |\n\n## Facts side by side\n\n| Fact | Terra API | Zus Health |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Terra Enabling Developers Inc. | Zus Health, Inc. |\n| Hosted endpoint | `https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e` | no (local only) |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Pay per use | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Terra's terms of service. The OpenAPI specs repository is Apache 2.0 | Proprietary service under the Zus Builder Terms of Service (last updated 11 March 2025), the Developer Sandbox Terms and the Zus Business Associate Addendum |\n| Tools exposed | 6 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-13 | 2026-10-14 |\n| Terms last updated | 2026-05-01 | 2025-03-11 |\n| Privacy policy last updated | 2023-04-20 | 2026-06-24 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 13k npm/wk, 11k PyPI/wk | none |\n\n## Verdicts\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**Zus Health.** FHIR R4 over an aggregated patient profile drawn from CommonWell, Carequality, Surescripts, Quest and ADT networks, with published rate limits, a 99.5 per cent SLA and a dated changelog. Accounts and sandboxes are provisioned by Zus on request, with no public prices, no named security certification and no SDK.\n\n## Before you call either\n\n### 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### Zus Health\n\n1. Cache the access token for its hour. More than 200 token requests an hour per App Client returns 429\n2. Request Patient History at most once per patient per 24 hours, and poll the job status endpoint\n3. Use conditional create by identifier so a retried write doesn't duplicate a resource\n4. Send `Zus-If-Match` with the resource's ETag on PUT and PATCH\n5. Set `_count` up to 500 on searches, since the default page is 10\n\n## Questions\n\n### Which is better for AI agents, Terra API or Zus Health?\n\nTerra API scores 65.9 (B) on agent readiness against Zus Health's 56.6 (C), and leads in 6 of 7 scored categories.\n\n### Do Terra API and Zus Health need an API key?\n\nTerra API takes an API key or an OAuth sign-in. Zus Health uses an OAuth sign-in.\n\n### Can an agent call Terra API and Zus Health without installing anything?\n\nTerra API has a hosted endpoint at https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e. No hosted endpoint is listed for Zus Health.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/terra-vs-zus-health.json, and with the fewest tokens: https://www.anchorterminal.com/compare/terra-vs-zus-health.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"terra\", \"b\": \"zus-health\"}`. From a terminal: `anchor compare terra zus-health`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/terra.json and https://www.anchorterminal.com/api/v1/tools/zus-health.json\n\n## Other comparisons with Terra API or Zus Health\n\n- [1upHealth vs Terra API](https://www.anchorterminal.com/compare/1uphealth-vs-terra.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- [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- [Medplum vs Zus Health](https://www.anchorterminal.com/compare/medplum-vs-zus-health.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 Zus Health](https://www.anchorterminal.com/compare/1uphealth-vs-zus-health.md)\n- [Health Gorilla vs Zus Health](https://www.anchorterminal.com/compare/health-gorilla-vs-zus-health.md)\n- [Medblocks vs Zus Health](https://www.anchorterminal.com/compare/medblocks-vs-zus-health.md)\n- [Metriport Medical API vs Zus Health](https://www.anchorterminal.com/compare/metriport-vs-zus-health.md)\n- [Particle Health vs Zus Health](https://www.anchorterminal.com/compare/particle-health-vs-zus-health.md)\n- [Medblocks vs Terra API](https://www.anchorterminal.com/compare/medblocks-vs-terra.md)\n- [ROOK vs Zus Health](https://www.anchorterminal.com/compare/rook-vs-zus-health.md)\n- [Validic Inform vs Zus Health](https://www.anchorterminal.com/compare/validic-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- [Redox vs Zus Health](https://www.anchorterminal.com/compare/redox-vs-zus-health.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-14",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Terra API vs Zus Health",
        "url": ""
      }
    ],
    "description": "Terra scores 65.9 (B) to Zus Health's 56.6 (C) for patient consent. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Terra API B 65.9",
      "Zus Health C 56.6",
      "scores"
    ],
    "h1": "Terra API vs Zus Health",
    "image": "https://www.anchorterminal.com/assets/og/compare-terra-vs-zus-health.png",
    "path": "/compare/terra-vs-zus-health",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Terra vs Zus Health for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-14",
    "url": "https://www.anchorterminal.com/compare/terra-vs-zus-health"
  },
  "tokens": {
    "markdown": 2300,
    "slim": 680
  },
  "version": 1
}
