/docs · Vetta Trainer
Documentation
Three technical docs of the product. No marketing — just how it works inside.
How the engine works
No black box. Here's exactly how the Vetta engine builds your week: archetypes, philosophies, periodization, injury prevention. If you understand it, you can argue it with your coach.
Zones: HR, pace, power, CSS
The engine translates each session's intensity into concrete numbers based on your `zone_mode` and available data. Exact formulas below.
13 training philosophies
The Vetta engine resolves each week using a philosophy. Not marketing — each one is a weight profile over the 66 archetypes. Here are the 13 with the context to pick one.
Inventory and real-world constraints
The engine only prescribes what you actually have available. Here's how time-bounded inventory works — key for altitude roster, vacations, borrowed gear and anything 'sometimes yes, sometimes no'.
Public Vetta API v1
Vetta exposes 25+ public endpoints under /api/v1/* for integrators, indexers and third parties. Clean JSON, no auth on public endpoints, standard rate limit.
Race time predictions
Vetta projects your times at 5K, 10K, half, marathon and ultras from your current VDOT. Here's exactly how, which model we use, and where the prediction loses precision.
Strava integration
Vetta reads your Strava to sync activities, compute VDOT and CTL, and build your week. Here's what we import, what we DON'T, and how we handle your data.
Coach model
The Coach plan gives you tools to manage up to 80 athletes. Here's how the link works, what the coach sees of the athlete, what they DON'T, and how we block the "1 coach + friends free" trap.
Load periodization
The Banister model + Coggan's metrics are the basis for how Vetta decides when to ramp you up and when to back off. Formulas and thresholds below.