# Push a planned workout or route to a person's device

> Push a planned workout or route to a person's device: 1 companies fully do it, 0 with a limit, 3 carry the tag. Every listing in Health records & wellness data with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/health-data.device-workouts/
- Markdown: https://www.anchorterminal.com/niches/health-data.device-workouts/index.md (~800 tokens)
- Slim: https://www.anchorterminal.com/niches/health-data.device-workouts/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/health-data.device-workouts/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 0 | 3 | 3 | 1 |

## What counts as done

The workout or route appears on the person's device platform with its steps, targets and date, through a documented write endpoint for that platform.

How agents ask for it: put tomorrow's interval session on my watch; schedule this training plan on Garmin; send this route to my bike computer

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Terra API (Terra Enabling Developers Inc.)**: The Planned Workouts API creates workouts on Garmin, COROS, Wahoo, Suunto, TrainingPeaks, Huawei, Zepp, Hevy and Apple, with coercion warnings when a provider can't represent a step, and the Routes API pushes GPS routes to Garmin, COROS, Wahoo and Hammerhead. It is a paid add-on.

- not this job: 1upHealth (1upHealth, Inc.): No device write path.
- not this job: Aidbox (Health Samurai, Inc.): No device write path.
- not this job: Health Gorilla (Health Gorilla, Inc.): No device write path.
- not this job: Medblocks (Medblocks Inc.): No device write path.
- not this job: Medplum (Orangebot, Inc.): No device write path.
- not this job: Metriport Medical API (Metriport Inc.): No device write path.
- not this job: Particle Health (Particle Health, Inc.): No device write path.
- not this job: Redox (Redox, Inc.): No device write path.
- not this job: ROOK (Rookeries Development Corp.): Collects data from devices; no documented write of workouts or routes to a device.
- not this job: Validic Inform (Validic, Inc.): Reads from devices; no workout or route write endpoint.
- not this job: Zus Health (Zus Health, Inc.): No device write path.

## What stops agents finishing

- workout types the agent needs (swim, gym) are not supported
- device platform write access needs a partner agreement

## Around it

Before: health-data.wearable-summary. After: scheduling.write.

## Where this comes from

Weight 3 of 100 in Health records & wellness data: 1 of 36 use-case citations across 34 accounts, scaled to 100; one account plus Terra's Planned Workouts and Routes pages, a floor

As data: https://www.anchorterminal.com/api/v1/use-cases/health-data.device-workouts.json, or the MCP tool get_use_case with id health-data.device-workouts. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
