{ "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": "Redox scores 58.3 (C) on agent readiness against ROOK's 54.9 (C), and leads in 4 of 7 scored categories. ROOK leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "rook", "name": "ROOK", "vendor": "Rookeries Development Corp.", "vendorUrl": "https://www.tryrook.io", "kind": "http-api", "category": "health-data", "summary": "ROOK Connect, from Rookeries Development Corp., collects health data from wearables and phone health stores, normalises it into sleep, physical and body summaries and events, and sends it by webhook or a REST API.", "url": "https://www.anchorterminal.com/tools/rook", "markdownUrl": "https://www.anchorterminal.com/tools/rook.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/rook.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/rook.json", "repo": "https://github.com/RookeriesDevelopment", "license": "Proprietary service under ROOK's Terms and Conditions for ROOK services", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "react-native-rook-sdk" }, { "registry": "npm", "name": "capacitor-rook-sdk" } ], "auth": "api-key", "authNotes": "A person registers an organisation in the ROOK Portal, which enables a Sandbox project, then generates a client UUID and secret key. The secret is shown once. Calls use HTTP Basic auth with the UUID as username and the secret as password. Production needs new credentials, an active plan and signed agreements. No scopes or key rotation were found. End users authorise each data source through ROOK's authoriser pages, the mobile SDKs or the ROOK App.", "pricing": "paid", "pricingNotes": "Core $399 a month for up to 750 active users, Core+ $999 for 5,000, Business $1,999 for 15,000, Enterprise custom. Add-ons cost $79 to $499 a month. A Sandbox is available before buying a plan. The standard term is 12 months with 30 days' notice to cancel (checked 2026-10-14).", "priceSummary": "$399 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-14" }, "docsUrl": "https://docs.tryrook.io", "llmsTxt": "https://docs.tryrook.io/llms.txt", "openapi": "https://docs.tryrook.io/redocusaurus/plugin-redoc-0.yaml", "capabilities": [ "health.wearables", "health.consent", "health.fhir" ], "tags": [ "hosted", "wearables", "health-data", "api-key", "openapi", "llms-txt", "sandbox", "webhooks", "status-page", "hipaa" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 54.9, "grade": "C", "agentReady": false, "rank": 718, "ranked": true, "rankOf": 1076, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 49, "maintenance": 73, "payments": 25, "reliability": 75, "schema": 74, "security": 32, "transparency": 55 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Graded on the REST API. A public OpenAPI file, a free Sandbox from the self-serve portal, published plan prices and a dated changelog. Credentials are one client UUID and secret per environment with no scopes, 429 handling isn't documented, the API is meant for occasional queries rather than bulk reads, and no SOC 2 report or security contact was found.", "bestFor": "A wellness, insurance, corporate wellness or remote monitoring product that wants normalised wearable data pushed to its backend, with plan prices it can see up front.", "strengths": [ "OpenAPI 3.0.3 file with 29 operations and production and sandbox servers, linked from the API reference", "A self-serve portal enables a Sandbox on registration, and the pricing FAQ says it can be tested before buying a plan", "Plan prices are public, from $399 a month for 750 active users, with add-on prices listed", "Data webhooks carry an X-ROOK-HASH HMAC header and are retried on a published schedule", "Dated changelog with five entries between 25 August and 7 October 2026, and SDK LTS releases with a six-month support period" ], "weaknesses": [ "Credentials are one client UUID and secret per environment, sent by Basic auth, with no scopes or rotation documented", "Typical limits of 60 requests a minute and 10,000 a day vary by plan, and no 429 or Retry-After behaviour is documented", "No server-side SDK. The official SDKs are mobile libraries for iOS, Android, Flutter, React Native and Capacitor", "The services terms cite an SLA page that isn't linked or published, and no SOC 2 or ISO 27001 report was found", "A WAF blocks requests without a User-Agent header and parameters containing localhost or SQL-like text" ], "agentNotes": [ "Send HTTP Basic auth with client_uuid as the username and the secret key as the password, plus a User-Agent header, or the WAF returns 403", "Use https://api.rook-connect.review for Sandbox and https://api.rook-connect.com for production. Each has its own credentials", "Read health data from the data webhook. Use the API only for occasional queries, and stay under 60 requests a minute", "Deduplicate summaries on document_version and datetime. ROOK resends a summary with a higher document_version when it changes", "Call POST /api/v1/user_id/{user_id}/data_sources/revoke_auth to end a connection. Some providers take hours to stop sending data" ], "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": 54.9 } ], "editorialScores": { "ergonomics": 49, "maintenance": 73, "payments": 25, "reliability": 75, "schema": 74, "security": 32, "transparency": 52 }, "provenanceScore": 58 }, "connect": { "http": "curl https://api.rook-connect.review/api/v1/client/users/status \\\n -u \u003cclient_uuid\u003e:\u003csecret_key\u003e \\\n -H 'User-Agent: MyApp/1.0.0'" }, "letme": { "capability": "https://letme.dev/health.wearables", "tool": "https://letme.dev/rook" }, "area": "domain-data", "unitPrices": [ { "item": "Core plan, up to 750 active users", "unit": "month", "usd": 399, "note": "tryrook.io/pricing, 2026-10-14" }, { "item": "Business plan, up to 15,000 active users, all add-ons", "unit": "month", "usd": 1999, "note": "tryrook.io/pricing, 2026-10-14" } ], "provenance": { "legalEntity": "Rookeries Development Corp.", "domain": "tryrook.io", "domainRegistered": "", "endpointOnVendorDomain": false, "terms": "https://www.tryrook.io/terms-rook-connect/", "privacy": "https://www.tryrook.io/privacy-policy/", "statusPage": "https://rook.statuspage.io", "changelog": "https://rook.canny.io/changelog", "securityTxt": "none", "checked": "2026-10-14", "notes": [ "The Terms and Conditions for ROOK services (last updated August 2026) and the website terms (4 June 2026) name Rookeries Development Corp., 224 NE 59th St, Miami, FL 33137.", "The website terms forbid robots, spiders and page scraping to acquire, copy or monitor any part of the site. robots.txt on www.tryrook.io and docs.tryrook.io allows all paths, and we read public pages only.", "The API answers at api.rook-connect.com and api.rook-connect.review, which are not on tryrook.io.", "rookmotion.com, the domain in the founder's list, did not load (expired certificate). The current site is www.tryrook.io.", "www.tryrook.io/.well-known/security.txt returns 404." ], "score": 58 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/rook.json", "live": { "slug": "rook", "vendorStatus": { "page": "https://rook.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:39.74478552Z" }, "updatedAt": "2026-10-14T09:39:39.74478552Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Redox, Inc.", "b": "Rookeries Development Corp.", "name": "Vendor" }, { "a": "https://api.redoxengine.com/mcp", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "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 ROOK's Terms and Conditions for ROOK services", "name": "Licence" }, { "a": "107", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-07", "name": "Last release" }, { "a": "2015-10-17", "b": "2026-08-01", "name": "Terms last updated" }, { "a": "2023-01-18", "b": "2026-05-28", "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": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Redox scores 58.3 (C) on agent readiness against ROOK's 54.9 (C), and leads in 4 of 7 scored categories. ROOK leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Redox or ROOK?" }, { "answer": "Redox uses an OAuth sign-in. ROOK needs an API key.", "question": "Do Redox and ROOK need an API key?" }, { "answer": "Redox has a hosted endpoint at https://api.redoxengine.com/mcp. No hosted endpoint is listed for ROOK.", "question": "Can an agent call Redox and ROOK without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 85 against 75", "Agent ergonomics, 54 against 49", "Security \u0026 auth, 78 against 32" ], "also": [ "A hosted endpoint, with nothing to install" ], "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, 74 against 56", "Payments \u0026 pricing, 25 against 15", "Maintenance \u0026 community, 73 against 31" ], "also": null, "goodFor": "A wellness, insurance, corporate wellness or remote monitoring product that wants normalised wearable data pushed to its backend, with plan prices it can see up front.", "slug": "rook", "watchFor": "Credentials are one client UUID and secret per environment, sent by Basic auth, with no scopes or rotation documented" } ], "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-redox.json", "title": "Aidbox vs Redox", "url": "https://www.anchorterminal.com/compare/aidbox-vs-redox" }, { "json": "https://www.anchorterminal.com/compare/aidbox-vs-rook.json", "title": "Aidbox vs ROOK", "url": "https://www.anchorterminal.com/compare/aidbox-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/health-gorilla-vs-rook.json", "title": "Health Gorilla vs ROOK", "url": "https://www.anchorterminal.com/compare/health-gorilla-vs-rook" }, { "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-rook.json", "title": "Medplum vs ROOK", "url": "https://www.anchorterminal.com/compare/medplum-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/metriport-vs-rook.json", "title": "Metriport Medical API vs ROOK", "url": "https://www.anchorterminal.com/compare/metriport-vs-rook" }, { "json": "https://www.anchorterminal.com/compare/particle-health-vs-rook.json", "title": "Particle Health vs ROOK", "url": "https://www.anchorterminal.com/compare/particle-health-vs-rook" }, { "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-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-rook.json", "title": "Medblocks vs ROOK", "url": "https://www.anchorterminal.com/compare/medblocks-vs-rook" }, { "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/rook-vs-terra.json", "title": "ROOK vs Terra API", "url": "https://www.anchorterminal.com/compare/rook-vs-terra" }, { "json": "https://www.anchorterminal.com/compare/rook-vs-validic.json", "title": "ROOK vs Validic Inform", "url": "https://www.anchorterminal.com/compare/rook-vs-validic" }, { "json": "https://www.anchorterminal.com/compare/redox-vs-zus-health.json", "title": "Redox vs Zus Health", "url": "https://www.anchorterminal.com/compare/redox-vs-zus-health" } ], "scores": [ { "by": 10, "edge": "redox", "key": "reliability", "name": "Reliability", "redox": 85, "rook": 75, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 18, "edge": "rook", "key": "schema", "name": "Schema \u0026 documentation", "redox": 56, "rook": 74, "weight": 13 }, { "by": 5, "edge": "redox", "key": "ergonomics", "name": "Agent ergonomics", "redox": 54, "rook": 49, "weight": 13 }, { "by": 46, "edge": "redox", "key": "security", "name": "Security \u0026 auth", "redox": 78, "rook": 32, "weight": 14 }, { "by": 10, "edge": "rook", "key": "payments", "name": "Payments \u0026 pricing", "redox": 15, "rook": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 42, "edge": "rook", "key": "maintenance", "name": "Maintenance \u0026 community", "redox": 31, "rook": 73, "weight": 7 }, { "by": 4, "edge": "redox", "key": "transparency", "name": "Transparency \u0026 trust", "redox": 59, "rook": 55, "weight": 7 } ], "summary": "Redox scores 58.3 (C) on agent readiness against ROOK's 54.9 (C), and leads in 4 of 7 scored categories. ROOK leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community. 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.", "rook": "Graded on the REST API. A public OpenAPI file, a free Sandbox from the self-serve portal, published plan prices and a dated changelog. Credentials are one client UUID and secret per environment with no scopes, 429 handling isn't documented, the API is meant for occasional queries rather than bulk reads, and no SOC 2 report or security contact was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/redox-vs-rook", "json": "https://www.anchorterminal.com/compare/redox-vs-rook.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/redox-vs-rook.md", "slim": "https://www.anchorterminal.com/compare/redox-vs-rook.min.md" }, "markdown": "Redox scores 58.3 (C) on agent readiness against ROOK's 54.9 (C), and leads in 4 of 7 scored categories. ROOK leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community. 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- ROOK: grade C, 54.9/100, rank #718 of 1076. Markdown https://www.anchorterminal.com/tools/rook.md · JSON https://www.anchorterminal.com/api/v1/tools/rook.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 75\n- Agent ergonomics, 54 against 49\n- Security \u0026 auth, 78 against 32\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: The MCP server loads 107 tools in one set, including write and delete tools with no confirmation step\n\n### ROOK (C)\n\nGood for: A wellness, insurance, corporate wellness or remote monitoring product that wants normalised wearable data pushed to its backend, with plan prices it can see up front.\n\nAhead on:\n- Schema \u0026 documentation, 74 against 56\n- Payments \u0026 pricing, 25 against 15\n- Maintenance \u0026 community, 73 against 31\n\nWatch for: Credentials are one client UUID and secret per environment, sent by Basic auth, with no scopes or rotation documented\n\n\n## Score by category\n\n| Category | Weight | Redox | ROOK | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 85 | 75 | Redox +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 56 | 74 | ROOK +18 |\n| Agent ergonomics | 13% (16.2 this run) | 54 | 49 | Redox +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 78 | 32 | Redox +46 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 25 | ROOK +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 31 | 73 | ROOK +42 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 59 | 55 | Redox +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **58.3 · C** | **54.9 · C** | |\n\n## Facts side by side\n\n| Fact | Redox | ROOK |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Redox, Inc. | Rookeries Development Corp. |\n| Hosted endpoint | `https://api.redoxengine.com/mcp` | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | OAuth | API key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under Redox's Cloud Services Agreement, EULA and SLA (version 2016.1) | Proprietary service under ROOK's Terms and Conditions for ROOK services |\n| Tools exposed | 107 | none |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | none | 2026-10-07 |\n| Terms last updated | 2015-10-17 | 2026-08-01 |\n| Privacy policy last updated | 2023-01-18 | 2026-05-28 |\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 | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\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**ROOK.** Graded on the REST API. A public OpenAPI file, a free Sandbox from the self-serve portal, published plan prices and a dated changelog. Credentials are one client UUID and secret per environment with no scopes, 429 handling isn't documented, the API is meant for occasional queries rather than bulk reads, and no SOC 2 report or security contact was found.\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### ROOK\n\n1. Send HTTP Basic auth with client_uuid as the username and the secret key as the password, plus a User-Agent header, or the WAF returns 403\n2. Use https://api.rook-connect.review for Sandbox and https://api.rook-connect.com for production. Each has its own credentials\n3. Read health data from the data webhook. Use the API only for occasional queries, and stay under 60 requests a minute\n4. Deduplicate summaries on document_version and datetime. ROOK resends a summary with a higher document_version when it changes\n5. Call POST /api/v1/user_id/{user_id}/data_sources/revoke_auth to end a connection. Some providers take hours to stop sending data\n\n## Questions\n\n### Which is better for AI agents, Redox or ROOK?\n\nRedox scores 58.3 (C) on agent readiness against ROOK's 54.9 (C), and leads in 4 of 7 scored categories. ROOK leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Redox and ROOK need an API key?\n\nRedox uses an OAuth sign-in. ROOK needs an API key.\n\n### Can an agent call Redox and ROOK without installing anything?\n\nRedox has a hosted endpoint at https://api.redoxengine.com/mcp. No hosted endpoint is listed for ROOK.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/redox-vs-rook.json, and with the fewest tokens: https://www.anchorterminal.com/compare/redox-vs-rook.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"redox\", \"b\": \"rook\"}`. From a terminal: `anchor compare redox rook`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/redox.json and https://www.anchorterminal.com/api/v1/tools/rook.json\n\n## Other comparisons with Redox or ROOK\n\n- [1upHealth vs ROOK](https://www.anchorterminal.com/compare/1uphealth-vs-rook.md)\n- [Aidbox vs Redox](https://www.anchorterminal.com/compare/aidbox-vs-redox.md)\n- [Aidbox vs ROOK](https://www.anchorterminal.com/compare/aidbox-vs-rook.md)\n- [Health Gorilla vs ROOK](https://www.anchorterminal.com/compare/health-gorilla-vs-rook.md)\n- [Medplum vs Redox](https://www.anchorterminal.com/compare/medplum-vs-redox.md)\n- [Medplum vs ROOK](https://www.anchorterminal.com/compare/medplum-vs-rook.md)\n- [Metriport Medical API vs ROOK](https://www.anchorterminal.com/compare/metriport-vs-rook.md)\n- [Particle Health vs ROOK](https://www.anchorterminal.com/compare/particle-health-vs-rook.md)\n- [Redox vs Terra API](https://www.anchorterminal.com/compare/redox-vs-terra.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 ROOK](https://www.anchorterminal.com/compare/medblocks-vs-rook.md)\n- [ROOK vs Zus Health](https://www.anchorterminal.com/compare/rook-vs-zus-health.md)\n- [ROOK vs Terra API](https://www.anchorterminal.com/compare/rook-vs-terra.md)\n- [ROOK vs Validic Inform](https://www.anchorterminal.com/compare/rook-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 ROOK", "url": "" } ], "description": "Redox scores 58.3 (C) to ROOK's 54.9 (C) for fhir servers. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Redox C 58.3", "ROOK C 54.9", "scores" ], "h1": "Redox vs ROOK", "image": "https://www.anchorterminal.com/assets/og/compare-redox-vs-rook.png", "path": "/compare/redox-vs-rook", "published": "2026-10-01", "section": "tools", "title": "Redox vs ROOK for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/redox-vs-rook" }, "tokens": { "markdown": 2200, "slim": 630 }, "version": 1 }