Power Oracle

Power Oracle is a split-aware work and power analysis API that computes mechanical work and power from structured workouts.

The current public contract is versioned under /v1.

It is built for athletes, coaches, software teams, and agents that need machine-readable workout analysis instead of scores alone.

For example, instead of storing only "Fran in 3:00," a client can send the session structure, preserve where time was spent, and get back session metrics, split metrics, summary output, movement rollups, and denominator notes that software can reason about directly.

Start here: New to Power Oracle? Go straight to the Quickstart and make your first successful compute request.

Why It Is Useful

Workout scores and finish times tell you what happened at a high level, but not how output was produced. Power Oracle preserves session elapsed time, split active time, and recovery so clients can distinguish steady pacing from collapse, active work from rest, and grouped work from isolated work instead of flattening everything into one denominator.

What You Send

• Athlete identity and evaluation context
• Session elapsed time at the top level
• Athlete measurements with explicit units
• Ordered splits[] that describe meaningful work segments
• Movement entries with reps plus any required movement-specific inputs

What You Get Back

• results.session for whole-session work and elapsed-power metrics
• results.splits[] for per-split work and active-power metrics
• results.summary for peak, minimum, mean, dropoff, and consistency across splits
• results.movement_rollups[] for session-level movement totals
• notes for denominator and modeling clarifications

Who This Is For

• Agent developers who need structured compute plus a reliable payment flow
• Coaching or workout software that wants more signal than scores and rounds alone
• Analysts and programmers building custom reporting or experiments
• Athletes who want to test requests manually before automating anything

What Power Oracle Is Not

• It is not a workout logger.
• It is not a leaderboard.
• It is not a wearable integration.
• It is not general health advice.

Make Your First Successful Compute Request

1. Read /.well-known/api-catalog or the Quickstart.
2. Inspect supported movements with GET /v1/movements.
3. Build a minimal split-aware request for POST /v1/compute-power.
4. Handle the 402 Payment Required challenge with x402 or L402.
5. Interpret results.session, results.splits, results.summary, and notes.

Read Next

• Quickstart: follow the shortest path to a successful paid compute request.
• Compute Model: learn the session-first, split-aware model and split rules.
• Worked Examples: see complete request and response examples with interpretation.
• Calling from a Client: use the practical curl, pseudo-flow, and Python client integration path.

Direction

Power Oracle is the first WorkCapacity product and the current public entrypoint. It is part of a larger measurement infrastructure, but the public docs should let you use Power Oracle immediately without needing the larger platform story first.

If you need help using Power Oracle, visit Contact or email workcapacity.io@agentmail.to.