PT Connect

Add a cadence signal
to your platform.

Continue reads athlete session history and returns a clear read on what is forming underneath. Not times. Not loads. Whether an athlete is building something sustainable — or drifting toward invisible wear before anyone notices.


You already have the data.
Continue adds the read.

Your platform tracks what athletes do. Continue adds a layer that tells coaches what is building underneath that data. One API call. No new app for athletes. No new infrastructure for you.

01

Send sessions

POST a block of recent sessions from your platform. Dates, completions, execution quality, subjective feel.

02

Get the signal

Continue returns a signal type, a headline, and two paragraphs a coach can actually use. Structured JSON.

03

Show your coaches

Render it how you want. Inside your existing interface. No new screens required.


What comes back.

Every response includes a signal type, a short headline, an honest read of what the data is showing, and one specific thing to protect. Here is an example.

rhythm_stable
Race-ready rhythm. Trust the taper.

8 of 10 sessions completed in full over 6 weeks, execution reported as clean in 7 of those. Subjective feel consistently positive — sharp, motivated, strong across the last 3 weeks. Pattern is anchored and the taper is showing as intended reduction, not drift.

Taper is working. Resist the urge to add intensity this week. The rhythm is set.

10 sessions analysed Confidence: high 6-week window
rhythm_stable
Consistent presence, balanced execution, no flags.
cadence_drift
Sessions happening but pattern eroding — gaps widening, execution declining.
load_tolerance_improving
Execution quality rising relative to volume. A signal of adaptation.
recovery_deficit
Showing up but the body isn't catching up. Execution and feel declining.
confidence_rebuilding
Return after a setback. Partial completions giving way to fuller ones.
engagement_declining
Presence there but subjective feel consistently flat or neutral.

One request. No account needed.

POST session data to https://connect.continue.fit/signal. Get back structured JSON. The field names are flexible — Continue normalises common variants automatically.

# Minimal example curl -X POST https://connect.continue.fit/signal \ -H "Content-Type: application/json" \ -d '{ "sport": "swimming", "sessions": [ { "date": "2026-03-20", "completion_status": "full", "duration_minutes": 75 }, { "date": "2026-03-22", "completion_status": "full", "duration_minutes": 60 }, { "date": "2026-03-25", "completion_status": "partial", "duration_minutes": 45, "execution_quality": "forced", "subjective_tags": ["tired", "heavy"] } ] }'

The interactive demo lets you test with real data without writing any code.


Try it with your own data.

The demo runs live against the same API your integration would use. Paste in real sessions and see what comes back.

Test the signal