{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/health-data.wearable-summary/",
    "json": "https://www.anchorterminal.com/niches/health-data.wearable-summary/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/health-data.wearable-summary/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/health-data.wearable-summary/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 3 | 9 | 25 | 9 |\n\n## What counts as done\n\nThe agent reads the person's normalised sleep, activity and body data for the asked range, including sleep stages and HRV where the device records them, and every value comes from the source rather than a truncated sample.\n\nMeasured, for our own tests: a 30-day sleep summary in under 3 calls.\n\nHow agents ask for it: how did I sleep this week; is my HRV trending down; summarise my training load; compare my resting heart rate to last month\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **ROOK (Rookeries Development Corp.)**: Normalised sleep (with stage times), physical and body summaries from Garmin, Oura, Polar, Fitbit, Apple Health and Health Connect can be queried by REST, but ROOK is a backend platform with no MCP or assistant connect route, and REST is a backup capped at 60 requests a minute.\n- **Terra API (Terra Enabling Developers Inc.)**: Terra AI's MCP has get_sleep_data (REM, deep, light, latency, HRV, SpO2), get_daily_data and get_activity_data with field lists, filters and server-side aggregation over a date range; acc-01 relies on Terra to normalise Polar data. But a person needs a developer plan from $499 a month, and the key is environment-wide.\n- **Validic Inform (Validic, Inc.)**: REST reads per user return summaries, sleep (REM, light, awake, total) and measurements in one schema across sources, but there is no documented agent route (the Enterprise MCP is unpublished), HRV is not listed, and the free tier's REST API is a preview on synthetic data.\n\n- not this job: 1upHealth (1upHealth, Inc.): No wearable or phone health-store data.\n- not this job: Aidbox (Health Samurai, Inc.): No wearable connectors.\n- not this job: Health Gorilla (Health Gorilla, Inc.): No wearable data.\n- not this job: Medblocks (Medblocks Inc.): The wearables and mobile page says coming soon.\n- not this job: Medplum (Orangebot, Inc.): No wearable connectors.\n- not this job: Metriport Medical API (Metriport Inc.): The Medical API covers clinical network data only.\n- not this job: Particle Health (Particle Health, Inc.): No wearable data.\n- not this job: Redox (Redox, Inc.): No wearable data.\n- not this job: Zus Health (Zus Health, Inc.): No wearable data.\n\n## What stops agents finishing\n\n- the metric the person wants is not in the provider's API\n- unofficial MCP breaks or is rate limited at sign-in\n- person will not send health data to a hosted model\n\n## Around it\n\nBefore: personal-assistants.connect. After: scheduling.write, messaging.send.\n\n## Where this comes from\n\nWeight 25 of 100 in Health records \u0026 wellness data: 9 of 36 use-case citations across 34 accounts, scaled to 100; most accounts use Garmin, Oura or Apple Health directly, not a listing\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/health-data.wearable-summary.json, or the MCP tool get_use_case with id health-data.wearable-summary. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Answer a person's questions from their wearable data",
        "url": ""
      }
    ],
    "description": "Answer a person's questions from their wearable data: 0 companies fully do it, 3 with a limit, 9 carry the tag. Every listing in Health records \u0026 wellness data with the reason and a source.",
    "facts": null,
    "h1": "Answer a person's questions from their wearable data",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/health-data.wearable-summary/",
    "published": "",
    "section": "agents",
    "title": "Answer a person's questions from their wearable data | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/health-data.wearable-summary/"
  },
  "tokens": {
    "markdown": 1000,
    "slim": 280
  },
  "version": 1
}
