{ "data": { "a": { "slug": "redox", "name": "Redox", "vendor": "Redox, Inc.", "vendorUrl": "https://redoxengine.com", "kind": "http-api", "category": "health-data", "summary": "Redox connects software vendors to hospital EHRs and clinical networks, translating HL7v2, C-CDA, X12 and DICOM into FHIR or Redox data models, with a FHIR API, a Platform API and a hosted MCP server for managing integrations.", "url": "https://www.anchorterminal.com/tools/redox", "markdownUrl": "https://www.anchorterminal.com/tools/redox.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/redox.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/redox.json", "license": "Proprietary service under Redox's Cloud Services Agreement, EULA and SLA (version 2016.1)", "transports": [ "http" ], "remoteUrl": "https://api.redoxengine.com/mcp", "packages": [], "auth": "oauth", "authNotes": "Data exchange uses OAuth API keys. The client signs a JWT assertion with a private key whose public half Redox holds (generated in the dashboard, pasted as a JWKS entry, or served from a JWKS URL), then exchanges it for a bearer token. Keys can be rotated, legacy API keys can be migrated, and user-level API keys exist for the Platform API. Each user connects to the MCP server through OAuth in their AI client after an organisation owner opts the organisation in.", "pricing": "paid", "pricingNotes": "Annual plans. Sandbox starts at $15,000 a year (a development environment with a FHIR sandbox and simulated patients, for organisations under 500 employees), Core starts at $35,000 a year, and Advanced is priced by sales. Consumption is billed on anticipated transaction volume, with no unit rates published. Anyone can create a dashboard account without a card, but what it can call before a plan is not stated (checked 2026-10-14).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the MCP server page or the pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": 107, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.redoxengine.com", "capabilities": [ "health.ehr", "health.fhir", "health.records" ], "tags": [ "hosted", "ehr-integration", "fhir", "hl7v2", "mcp", "oauth", "status-page", "sla", "bug-bounty", "hitrust", "soc2", "sales-led" ], "graded": true, "anchor": { "graded": true, "score": 58.3, "grade": "C", "agentReady": false, "rank": 618, "ranked": true, "rankOf": 1076, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 31, "payments": 15, "reliability": 85, "schema": 56, "security": 78, "transparency": 59 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Redox connects to EHRs and clinical networks behind a FHIR API, with signed-JWT OAuth keys, a 99.95 per cent SLA, a HackerOne bug bounty and a hosted MCP server for managing integrations. The MCP server exposes 107 tools at once with write and delete tools unconfirmed, OpenAPI files sit behind login, and the sandbox plan costs $15,000 a year.", "bestFor": "Health software vendors integrating with many hospital EHRs and networks, and integration teams who want an agent to manage Redox configuration.", "strengths": [ "OAuth API keys signed with the client's own private key, with JWKS URL support and rotation guidance", "Hosted MCP server with per-user OAuth and an organisation-level opt-in", "Published SLA of 99.95 per cent and a 40-minute incident on 8 September 2026 with a postmortem", "HITRUST r2, SOC 2 Type 2 and a public HackerOne bug bounty" ], "weaknesses": [ "The MCP server loads 107 tools in one set, including write and delete tools with no confirmation step", "OpenAPI files and Postman collections are behind the dashboard login, and llms.txt is missing", "No public changelog or dated releases", "The cheapest plan with a sandbox starts at $15,000 a year" ], "agentNotes": [ "Name the environment in every MCP prompt and try configuration changes in staging first, as Redox advises", "Stay under 7,500 requests per IP per five minutes, and back off exponentially on 5XX", "Sign the token request with the private key whose public key is registered on the OAuth API key", "Ask an organisation owner to enable the MCP server before connecting a client", "Treat log payloads returned through MCP as PHI and as untrusted text" ], "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": 58.3 } ], "editorialScores": { "ergonomics": 54, "maintenance": 31, "payments": 15, "reliability": 85, "schema": 56, "security": 78, "transparency": 37 }, "provenanceScore": 80 }, "connect": { "http": "https://api.redoxengine.com/mcp" }, "letme": { "capability": "https://letme.dev/health.ehr", "tool": "https://letme.dev/redox" }, "area": "domain-data", "provenance": { "legalEntity": "Redox, Inc.", "domain": "redoxengine.com", "domainRegistered": "2014-07-23", "endpointOnVendorDomain": true, "terms": "https://redoxengine.com/legal/terms-of-use/", "privacy": "https://redoxengine.com/legal/privacy-policy/", "statusPage": "https://status.redoxengine.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The website terms of use (version 2014.1, last updated 17 October 2015) name Redox, Inc., 25 West Main Street, Suite 500, Madison, WI 53703, and forbid crawling that impairs a system. Service use falls under a Cloud Services Agreement and the EULA, which we did not read.", "The SLA page is version 2016.1, dated 13 February 2016.", "The privacy policy (last updated 18 January 2023) covers the website and says it doesn't govern data Redox processes for customers.", "redoxengine.com/.well-known/security.txt returns 404. The platform security page points to a HackerOne bug bounty.", "docs.redoxengine.com/llms.txt returns the HTML site rather than an llms.txt file. No public changelog was found.", "RDAP gives redoxengine.com a registration date of 2014-07-23." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/redox.json", "live": { "slug": "redox", "probe": { "target": "https://api.redoxengine.com/mcp", "method": "get", "lastAt": "2026-10-14T09:42:04.293207713Z", "lastOk": true, "lastStatus": 401, "lastMs": 251, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 265, "p95ms24h": 428, "samples24h": 17, "samples30d": 17, "days": [ { "date": "2026-10-14", "probes": 17, "ok": 17 } ] }, "vendorStatus": { "page": "https://status.redoxengine.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:39.154707608Z" }, "updatedAt": "2026-10-14T09:42:04.293207713Z" } }, "answer": "Terra API scores 65.9 (B) on agent readiness against Redox's 58.3 (C), and leads in 4 of 7 scored categories. Redox leads on reliability and security \u0026 auth.", "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": "Redox, Inc.", "b": "Terra Enabling Developers Inc.", "name": "Vendor" }, { "a": "https://api.redoxengine.com/mcp", "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 Redox's Cloud Services Agreement, EULA and SLA (version 2016.1)", "b": "Proprietary service under Terra's terms of service. The OpenAPI specs repository is Apache 2.0", "name": "Licence" }, { "a": "107", "b": "6", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-13", "name": "Last release" }, { "a": "2015-10-17", "b": "2026-05-01", "name": "Terms last updated" }, { "a": "2023-01-18", "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": "not found in the text", "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 Redox's 58.3 (C), and leads in 4 of 7 scored categories. Redox leads on reliability and security \u0026 auth.", "question": "Which is better for AI agents, Redox or Terra API?" }, { "answer": "Redox uses an OAuth sign-in. Terra API takes an API key or an OAuth sign-in.", "question": "Do Redox and Terra API need an API key?" }, { "answer": "Yes. Redox has a hosted endpoint at https://api.redoxengine.com/mcp and Terra API at https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e.", "question": "Can an agent call Redox and Terra API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 85 against 67", "Security \u0026 auth, 78 against 65" ], "also": null, "goodFor": "Health software vendors integrating with many hospital EHRs and networks, and integration teams who want an agent to manage Redox configuration.", "slug": "redox", "watchFor": "The MCP server loads 107 tools in one set, including write and delete tools with no confirmation step" }, { "aheadOn": [ "Schema \u0026 documentation, 89 against 56", "Agent ergonomics, 78 against 54", "Payments \u0026 pricing, 20 against 15", "Maintenance \u0026 community, 75 against 31" ], "also": null, "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-terra.json", "title": "1upHealth vs Terra API", "url": "https://www.anchorterminal.com/compare/1uphealth-vs-terra" }, { "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-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-redox.json", "title": "Medplum vs Redox", "url": "https://www.anchorterminal.com/compare/medplum-vs-redox" }, { "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-rook.json", "title": "Redox vs ROOK", "url": "https://www.anchorterminal.com/compare/redox-vs-rook" }, { "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/health-gorilla-vs-redox.json", "title": "Health Gorilla vs Redox", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/medblocks-vs-redox.json", "title": "Medblocks vs Redox", "url": "https://www.anchorterminal.com/compare/medblocks-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/metriport-vs-redox.json", "title": "Metriport Medical API vs Redox", "url": "https://www.anchorterminal.com/compare/metriport-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/particle-health-vs-redox.json", "title": "Particle Health vs Redox", "url": "https://www.anchorterminal.com/compare/particle-health-vs-redox" }, { "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" }, { "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": 18, "edge": "redox", "key": "reliability", "name": "Reliability", "redox": 85, "terra": 67, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 33, "edge": "terra", "key": "schema", "name": "Schema \u0026 documentation", "redox": 56, "terra": 89, "weight": 13 }, { "by": 24, "edge": "terra", "key": "ergonomics", "name": "Agent ergonomics", "redox": 54, "terra": 78, "weight": 13 }, { "by": 13, "edge": "redox", "key": "security", "name": "Security \u0026 auth", "redox": 78, "terra": 65, "weight": 14 }, { "by": 5, "edge": "terra", "key": "payments", "name": "Payments \u0026 pricing", "redox": 15, "terra": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 44, "edge": "terra", "key": "maintenance", "name": "Maintenance \u0026 community", "redox": 31, "terra": 75, "weight": 7 }, { "by": 3, "edge": "redox", "key": "transparency", "name": "Transparency \u0026 trust", "redox": 59, "terra": 56, "weight": 7 } ], "summary": "Terra API scores 65.9 (B) on agent readiness against Redox's 58.3 (C), and leads in 4 of 7 scored categories. Redox leads on reliability and security \u0026 auth. Both do fhir servers.", "verdicts": { "redox": "Redox connects to EHRs and clinical networks behind a FHIR API, with signed-JWT OAuth keys, a 99.95 per cent SLA, a HackerOne bug bounty and a hosted MCP server for managing integrations. The MCP server exposes 107 tools at once with write and delete tools unconfirmed, OpenAPI files sit behind login, and the sandbox plan costs $15,000 a year.", "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/redox-vs-terra", "json": "https://www.anchorterminal.com/compare/redox-vs-terra.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/redox-vs-terra.md", "slim": "https://www.anchorterminal.com/compare/redox-vs-terra.min.md" }, "markdown": "Terra API scores 65.9 (B) on agent readiness against Redox's 58.3 (C), and leads in 4 of 7 scored categories. Redox leads on reliability and security \u0026 auth. Both do fhir servers.\n\n- Redox: grade C, 58.3/100, rank #618 of 1076. Markdown https://www.anchorterminal.com/tools/redox.md · JSON https://www.anchorterminal.com/api/v1/tools/redox.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### Redox (C)\n\nGood for: Health software vendors integrating with many hospital EHRs and networks, and integration teams who want an agent to manage Redox configuration.\n\nAhead on:\n- Reliability, 85 against 67\n- Security \u0026 auth, 78 against 65\n\nWatch for: The MCP server loads 107 tools in one set, including write and delete tools with no confirmation step\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 56\n- Agent ergonomics, 78 against 54\n- Payments \u0026 pricing, 20 against 15\n- Maintenance \u0026 community, 75 against 31\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 | Redox | Terra API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 85 | 67 | Redox +18 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 56 | 89 | Terra API +33 |\n| Agent ergonomics | 13% (16.2 this run) | 54 | 78 | Terra API +24 |\n| Security \u0026 auth | 14% (17.5 this run) | 78 | 65 | Redox +13 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 20 | Terra API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 31 | 75 | Terra API +44 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 59 | 56 | Redox +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **58.3 · C** | **65.9 · B** | |\n\n## Facts side by side\n\n| Fact | Redox | Terra API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Redox, Inc. | Terra Enabling Developers Inc. |\n| Hosted endpoint | `https://api.redoxengine.com/mcp` | `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 Redox's Cloud Services Agreement, EULA and SLA (version 2016.1) | Proprietary service under Terra's terms of service. The OpenAPI specs repository is Apache 2.0 |\n| Tools exposed | 107 | 6 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | none | 2026-10-13 |\n| Terms last updated | 2015-10-17 | 2026-05-01 |\n| Privacy policy last updated | 2023-01-18 | 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 | not found in the text | 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**Redox.** Redox connects to EHRs and clinical networks behind a FHIR API, with signed-JWT OAuth keys, a 99.95 per cent SLA, a HackerOne bug bounty and a hosted MCP server for managing integrations. The MCP server exposes 107 tools at once with write and delete tools unconfirmed, OpenAPI files sit behind login, and the sandbox plan costs $15,000 a year.\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### Redox\n\n1. Name the environment in every MCP prompt and try configuration changes in staging first, as Redox advises\n2. Stay under 7,500 requests per IP per five minutes, and back off exponentially on 5XX\n3. Sign the token request with the private key whose public key is registered on the OAuth API key\n4. Ask an organisation owner to enable the MCP server before connecting a client\n5. Treat log payloads returned through MCP as PHI and as untrusted text\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, Redox or Terra API?\n\nTerra API scores 65.9 (B) on agent readiness against Redox's 58.3 (C), and leads in 4 of 7 scored categories. Redox leads on reliability and security \u0026 auth.\n\n### Do Redox and Terra API need an API key?\n\nRedox uses an OAuth sign-in. Terra API takes an API key or an OAuth sign-in.\n\n### Can an agent call Redox and Terra API without installing anything?\n\nYes. Redox has a hosted endpoint at https://api.redoxengine.com/mcp and Terra API 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/redox-vs-terra.json, and with the fewest tokens: https://www.anchorterminal.com/compare/redox-vs-terra.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"redox\", \"b\": \"terra\"}`. From a terminal: `anchor compare redox terra`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/redox.json and https://www.anchorterminal.com/api/v1/tools/terra.json\n\n## Other comparisons with Redox or Terra API\n\n- [1upHealth vs Terra API](https://www.anchorterminal.com/compare/1uphealth-vs-terra.md)\n- [Aidbox vs Redox](https://www.anchorterminal.com/compare/aidbox-vs-redox.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 Redox](https://www.anchorterminal.com/compare/medplum-vs-redox.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 ROOK](https://www.anchorterminal.com/compare/redox-vs-rook.md)\n- [1upHealth vs Redox](https://www.anchorterminal.com/compare/1uphealth-vs-redox.md)\n- [Health Gorilla vs Redox](https://www.anchorterminal.com/compare/health-gorilla-vs-redox.md)\n- [Medblocks vs Redox](https://www.anchorterminal.com/compare/medblocks-vs-redox.md)\n- [Metriport Medical API vs Redox](https://www.anchorterminal.com/compare/metriport-vs-redox.md)\n- [Particle Health vs Redox](https://www.anchorterminal.com/compare/particle-health-vs-redox.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- [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": "Redox vs Terra API", "url": "" } ], "description": "Terra scores 65.9 (B) to Redox's 58.3 (C) for fhir servers. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Redox C 58.3", "Terra API B 65.9", "scores" ], "h1": "Redox vs Terra API", "image": "https://www.anchorterminal.com/assets/og/compare-redox-vs-terra.png", "path": "/compare/redox-vs-terra", "published": "2026-10-01", "section": "tools", "title": "Redox vs Terra for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/redox-vs-terra" }, "tokens": { "markdown": 2250, "slim": 680 }, "version": 1 }