If you've asked ChatGPT or Claude about your training before, you'll know it can give genuinely useful advice in seconds. The catch is a later conversation can lose important context or carry forward something that's no longer true, leaving you re-explaining yourself and pasting in screenshots.
Athmex fixes that. Build your athlete profile once and connect Athmex to Claude or ChatGPT. When the assistant uses Athmex, it can pull in an accurate, dated picture of you instead of guessing.
Add the numbers you train to: things like threshold pace or power, max and threshold heart rate, current PBs, height and weight.
Each value is stored with the date it became current. When a number changes, the old one is retired rather than overwritten, so your history stays intact and nothing gets averaged into a guess by your AI.
Add your races with dates, distance and priorities, plus what goals you are training towards - your AI can then plan your training properly around what matters and when.
After a race is over or a goal is reached, Claude and ChatGPT will ask for the results or fetch them for you, analyse them and add them back into Athmex automatically. Your races results really matter, especially when the AI is helping you plan for the next one.
With Athmex your AI can see how previous races and goals actually went rather than what it might choose to remember or assumptions it makes.
Record recurring injuries and what triggers them, the hours you realistically have to train each week, and the gear you use to train and race.
This context can have a huge impact on an AI generated training plans but without Athmex it’s often completely missed by both Claude and ChatGPT.
Connect Athmex to Claude with one just one click when your profile is created and that’s it! It’s available on all Claude account types, even the free ones.
ForChatGPT, a paid account is needed and setup takes 3 minutes to complete.
From then on, your AI can think properly when making decisions about your training, races and results.
The reason the Athmex layer beats blasting a big paragraph or pasting loads of screenshots into Claude or ChatGPT is that its consistent structure is designed for use by AI.
Athmex holds multiple kinds of fact, each deliberate shaped so an AI model can use it without guessing about you.
Threshold pace, FTP, heart-rate figures and body metrics, each versioned with the date it became current and the date it was superseded. Your assistant always reads today's number, and can see how it moved.
Distance, time and date for each personal best, so a training benchmark taken from a PB set in the last few months is never confused with one from three seasons ago that is totally stale.
Just because you set a PB 3 years ago doesn’t mean it should form the basis of your next session!
What you are working towards and by when, so advice can be measured against a deadline rather than offered in the abstract.
Your race calendar with dates, distances, priorities and results so past performances inform the next training plan or session.
Recurring niggles, what sets them off, current clinical guidance and how much you can train around them. Dated, so a resolved problem stops being quoted back at you.
The gear you train and race in, which changes pacing advice and recovery time more than most athletes expect. Let the AI think it through for you and adapt your training accordingly.
Claude or ChatGPT does the reasoning and produces the plans. Athmex only supplies the athlete facts they use.
Athmex doesn't connect to, read from or store activities from Strava, Garmin, COROS or Apple Health. Nothing syncs in the background.
Close the loop instead. Connect a supported activity platform like Strava or COROS, and your AI can see how a prescribed session actually went.
Build your profile once, and every conversation after starts from your real numbers.
Claude and ChatGPT both work with Athmex, but not equally. On Claude, every plan including the free one gets full read-and-write access to your Athmex context. On ChatGPT, Developer Mode currently gives Pro accounts read and fetch access only, so you can use your Athmex context in a conversation but can't update it directly from ChatGPT; full read-and-write access on ChatGPT currently needs a Business, Enterprise or Edu workspace. Plus is not currently listed. Strava's connector supports Claude only.
You never write any code, but the two assistants are not equally quick. Claude takes about two minutes: you paste a link we give you and approve the connection. ChatGPT is more involved, roughly nine steps, including creating a custom app and selecting permission scopes, all of which we spell out one at a time. Allow ten minutes for ChatGPT, and use Claude if you would rather it were simple.
As of 6 August 2026, two. COROS publishes an official MCP server, and Strava offers an official Claude connector through Claude's built-in directory. Garmin, WHOOP, Oura, Polar, Suunto, Wahoo and Apple do not publish official AI connectors. Community-built servers exist for most of them, but they are unaffiliated with the manufacturer and carry no guarantee of maintenance.
Athmex serves your context only through your private connection. Once it reaches Claude or ChatGPT, that provider handles it under its own terms and privacy settings. Athmex does not sell it or use it for advertising.
A few minutes of setup, and every conversation after it starts from your real numbers. If Claude or ChatGPT notices a change in your key numbers or a race date has arrived, they’ll then chat to you and post to Athmex automatically to keep everything up to date for you.