# MovePacket

> Sports data infrastructure. Private beta. Check https://movepacket.com/site-status.json for hosted API availability before live uploads.

## Guides

- [Overview](https://movepacket.com/docs/index.md): The MovePacket developer guide: original FIT files, structured activity data, and one API.
- [Quickstart](https://movepacket.com/docs/quickstart.md): Upload a FIT activity, retrieve decoded data, and verify the original with Node.js.
- [Authentication](https://movepacket.com/docs/authentication.md): Keep API keys on your server and activity data scoped to your workspace.
- [Athlete connections](https://movepacket.com/docs/connections.md): Available FIT intake, athlete-authorised connection roadmap, and existing coaching platforms.
- [Records & responsibility](https://movepacket.com/docs/records.md): Inspect source records, verify originals, export metadata and understand the current access boundary.
- [Activities](https://movepacket.com/docs/activities.md): Upload, list, filter, and retrieve sports activities.
- [Processing & reliability](https://movepacket.com/docs/processing.md): Handle asynchronous decoding, retries, duplicates, and terminal failures.
- [Data model](https://movepacket.com/docs/data-model.md): Understand the activity envelope and decoded Garmin FIT messages.
- [Errors & recovery](https://movepacket.com/docs/errors.md): API and processing error codes with practical recovery steps.
- [API reference](https://movepacket.com/docs/api-reference.md): The implemented MovePacket REST API, generated from its OpenAPI contract.
- [Build with AI](https://movepacket.com/docs/ai-tools.md): Machine-readable docs, OpenAPI, and examples for AI coding tools.

## Contracts and examples

- [OpenAPI](https://movepacket.com/openapi.json): Implemented server endpoints; bearer authentication.
- [Full guides](https://movepacket.com/llms-full.txt)
- [Node.js quickstart](https://movepacket.com/examples/movepacket-quickstart.mjs)

Webhooks, device connections, MCP, and packaged SDKs are planned, not implemented. Never include credentials in chat or browser code.