Give your tools the context.
MovePacket's documentation is available as readable pages, Markdown, and an OpenAPI contract. Point your coding assistant at these resources before asking it to build an integration.
Machine-readable resources#
| Resource | Use |
|---|---|
| llms.txt | Guide index for AI tools |
| llms-full.txt | All current guides in one text document |
| openapi.json | OpenAPI 3.0.3 contract for implemented server endpoints |
| Runnable Node.js example | Upload, polling, downloads, and checksum verification |
Every guide also has a Markdown version, linked in the page tools. Documentation is public. Reading it does not grant access to activity data or API credentials.
Start an integration#
Copy this brief into your coding tool:
Read https://movepacket.com/llms.txt and the linked OpenAPI contract.
Build a server-side MovePacket integration using environment secrets.
Upload raw FIT bytes, retain the activity ID, and poll with a bounded wait.
Handle ready and failed states explicitly. Download decoded JSON only
when ready, and verify the original file's SHA-256 before accepting it.
Use only documented endpoints. Do not put API keys in browser code,
URLs, logs, or chat. Check hosted beta availability before live uploads.
API and MCP#
The REST API is the current application interface. A MovePacket MCP server is planned but is not available yet. These documentation resources help AI tools write integrations today; they are not an authenticated MCP connection.
There is no packaged MovePacket SDK yet. The downloadable Node.js example uses standard HTTP calls and can be adapted inside your server application.
Prepare evidence before asking AI to interpret it#
Your application should select relevant activity windows and calculate aggregates before sending long time-series data to a language model. Keep original activity IDs, units, missing-data indicators and calculation versions with the result so it can be traced back. Do not replace unavailable measurements with zero.
MovePacket’s current API returns decoded FIT data; it does not yet provide intent-based retrieval, compressed athlete context or athlete memory. Evidence preparation is a future infrastructure concern. Coaching judgments and recommendations remain your application’s responsibility.
Start with athlete connections and source records. An AI coding assistant cannot create provider access or athlete permission on your behalf.