Your swing, measured.
Feel isn't fact — most swing flaws are invisible at full speed. One phone video becomes measured 3D motion, compared against 400 tour swings, so you practice on numbers instead of guesses.
- Pose overlay
- 3D replay
- Tour-reference metrics
- A coach grounded in your data
MP4 or MOV, up to 200 MB. Analysis runs on the real cloud pipeline and usually takes 2–3 minutes.
Your swings
Analyses from this browser. Processing happens in the cloud — you can leave and come back; links to a result can be shared.
This month
For developers API
Everything on this page runs on a public HTTP API — the same endpoints are open for integration. Upload a video, poll for artifacts, done.
| POST /upload-url | Request a presigned S3 upload slot →
{job_id, url, fields} |
| POST (S3 form) | Send the video bytes straight to storage using
url + fields |
| GET results | /03_outputs/<job_id>/metrics.json ·
explanation.json · replay_3d.json · overlay.mp4 appear when analysis
completes (~2–3 min). Private during the pilot — pass the
dev access code as ?t=<code> (or the mc_dev
cookie). |
Results are edge-gated while we pilot with real players. Per-developer API keys, rate limits and a job-status endpoint are on the roadmap.
Analyzing your swing
- Reading the videoPulling frames from the clip
- Finding the bodyPlacing 2D markers on every joint, every frame
- Steadying the motionSmoothing jitter between frames
- Splitting the swingDetecting address, top, impact and follow-through
- Adding depthEstimating the motion a flat video can't show
- Building the replayRendering a 3D skeleton
- Reading the swingTranslating the numbers into plain English
Running the real 3D pipeline in the cloud — this usually takes 2–3 minutes. Your result opens automatically when it's ready, and also lands under “Your swings” if you leave this page.
Answers are grounded in this swing's measured data — the coach describes what was measured against the tour reference and never prescribes fixes.