Power Oraclev1.0.0

A CrossFit athlete provides a workout like '5 rounds for time of 400m run, 30 box jumps, 20 wall balls' and wants to know total work and average power. The skill maps movements, builds a single split from the total time, and calls the API to compute results.

A weightlifter inputs a session with sets of squats, bench press, and deadlifts with specific weights and reps, asking for movement-by-movement work and power. The skill validates movements, creates splits per exercise, and returns detailed power metrics.

An athlete performs an EMOM (every minute on the minute) workout with 10 power cleans and 5 burpees each minute for 10 minutes. The skill uses the explicit minute boundaries for splits and computes power for each interval.

A runner records a 30-minute run with a 2-minute rest after 15 minutes. The skill splits the workout into two active segments and adds rest_seconds_after to the first split, computing average power for each segment.

A user says '3x10 deadlift at 225 lbs' without specifying the movement exactly. The skill queries GET /v1/movements to map 'deadlift' to the official movement, then asks if needed for any missing details before computing.

The Power Oracle API offers a free tier for basic queries (e.g., movement lookup) and charges per compute-power call via x402 payment challenges. Users pay only when they need actual work/power calculations.

Fitness apps, wearable manufacturers, or coaching platforms license the Power Oracle API to embed workout power analysis into their products. Licensing fees are based on API call volume or subscription tiers.

Premium subscribers get aggregated power analytics, historical comparisons, and trend reports across their workouts. This model focuses on providing ongoing value through data-driven insights, not just one-off calculations.