Write a review

Head to head · Wearable and health app data · October 2026 research run

ROOK vs Terra API

Terra API scores 65.9 (B) on agent readiness against ROOK's 54.9 (C), and leads in 5 of 7 scored categories. ROOK leads on reliability and payments & pricing. Both do wearable and health app data.

Best health record and wellness data APIs for AI agents · All 63 health comparisons

ROOKRookeries Development Corp. · HTTP API C54.9/100#718 of 1076 Terra APITerra Enabling Developers Inc. · HTTP API B65.9/100#327 of 1076

Which one, for what

ROOK C

Best 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.

Ahead on

  • Reliability, 75 against 67
  • Payments & pricing, 25 against 20

Watch for

Credentials are one client UUID and secret per environment, sent by Basic auth, with no scopes or rotation documented

Terra API B

Best 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.

Ahead on

  • Schema & documentation, 89 against 74
  • Agent ergonomics, 78 against 49
  • Security & auth, 65 against 32

Also in its favour

  • A hosted endpoint, with nothing to install

Watch 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

Score by category

CategoryWeight this runROOKTerra APIEdge
Reliability16%207567ROOK +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27489Terra API +15
Agent ergonomics13%16.24978Terra API +29
Security & auth14%17.53265Terra API +33
Payments & pricing10%12.52520ROOK +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87375Terra API +2
Transparency & trust7%8.85556Terra API +1
Negative events≤1500
TotalC 54.9/100B 65.9/100

Facts side by side

FactROOKTerra API
KindHTTP APIHTTP API
VendorRookeries Development Corp.Terra Enabling Developers Inc.
Hosted endpointno (local only)https://access.tryterra.co/api/v2/mcp/<user_id>
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPaidPay per use
x402nono
LicenceProprietary service under ROOK's Terms and Conditions for ROOK servicesProprietary service under Terra's terms of service. The OpenAPI specs repository is Apache 2.0
Tools exposednone6
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-072026-10-13
Terms last updated2026-08-012026-05-01
Privacy policy last updated2026-05-282023-04-20
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesyes
Popularitynone13k npm/wk, 11k PyPI/wk

Verdicts

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.

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.

Before you call either

ROOK

  1. 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
  2. Use https://api.rook-connect.review for Sandbox and https://api.rook-connect.com for production. Each has its own credentials
  3. Read health data from the data webhook. Use the API only for occasional queries, and stay under 60 requests a minute
  4. Deduplicate summaries on document_version and datetime. ROOK resends a summary with a higher document_version when it changes
  5. Call POST /api/v1/user_id/{user_id}/data_sources/revoke_auth to end a connection. Some providers take hours to stop sending data

Terra API

  1. Send dev-id and x-api-key headers on every Unified API and Terra AI call. A missing header returns 401 problem+json
  2. 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
  3. Pass either fields or select to Terra AI tools, never both and never neither, or the call fails with a validation error
  4. Expect data by webhook after a user connects through the widget session. REST reads are for backfills and on-demand queries
  5. Use the Read only access level for the admin MCP server unless a change is needed. The MCP level can read API keys

Questions

Which is better for AI agents, ROOK or Terra API?

Terra API scores 65.9 (B) on agent readiness against ROOK's 54.9 (C), and leads in 5 of 7 scored categories. ROOK leads on reliability and payments & pricing.

Do ROOK and Terra API need an API key?

ROOK needs an API key. Terra API takes an API key or an OAuth sign-in.

Can an agent call ROOK and Terra API without installing anything?

No hosted endpoint is listed for ROOK. Terra API has a hosted endpoint at https://access.tryterra.co/api/v2/mcp/<user_id>.

Other comparisons with ROOK or Terra API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report