# Tredict

> GDPR-compliant endurance sports training planning and activity analysis platform for runners, cyclists, and triathletes. Supports integration with Garmin, Coros, Polar, Strava, and other devices, and offers a REST API for personal use through Personal Access Tokens.

The guides under "Consumer Skills" are written for athletes and coaches who want to script against the Tredict API directly. They complement the API reference with unit conventions, common pitfalls, and complete examples, and apply to Personal API tokens and OAuth2 applications alike, since the endpoints and data structures are almost identical. How to create and use a Personal API token is described in the [API reference](https://www.tredict.com/blog/oauth_docs/#personal_api_token). The examples are language-agnostic and use JSON plus pseudocode, so they translate into Python, JavaScript, Bash, or any other language.

## API Reference

- [Full API reference](https://www.tredict.com/blog/oauth_docs/): Complete endpoint documentation with all parameters, scopes, response shapes, and OAuth2 details.

## Consumer Skills

- [Structured workouts](https://www.tredict.com/skills/workouts.md): Build workouts and training plans with steps, repetitions, and target zones (range vs. padding, FTPa, FTP, hrMax).
- [Activities](https://www.tredict.com/skills/activities.md): List, fetch, upload, update, and download activities. Unit conventions and time series.

## Further Reading for Humans

- [OAuth2 API documentation](https://www.tredict.com/blog/oauth_docs/): Integration guide for third-party app developers using OAuth2.
- [MCP Server documentation](https://www.tredict.com/blog/mcp_server_docs/): Setup and usage of the Tredict MCP Server with AI assistants.

## Optional

- [Tredict MCP Server](https://www.tredict.com/api/mcp/v2): For users who prefer not to script themselves, Tredict provides a Model Context Protocol server that exposes the same data through tool calls. Compatible with Claude and other MCP-aware assistants.