Add a certified human coach to your AI fitness app with one API

2026-09-27, Organisations

If you build an AI fitness or nutrition product, the Care MCP API lets your app order a written plan, an evaluation or a plan review from a certified human personal trainer or nutrition coach, in your user's name, with one API key. You create your users as clients under your own ids, post a structured brief, and get a signed webhook when the document is ready. There is no hiring, no scheduling and no subscription: you pay per delivered document from a prepaid balance.

What you get

Your model already talks to your users every day and writes them plans. The API adds a professional where it matters: a certified trainer who writes the plan, or checks the one your model wrote, under a fixed template.

Three kinds of order are available, the same ones an AI assistant sees through our MCP server:

• Plan: a training plan, an eating plan, or both together, for the period ahead.
• Evaluate: an evaluation of a period that passed, from the logs your app already has.
• Review a plan: a professional reviews a plan your model generated and says what to keep and what to change.

Each order names one or more professions, so a trainer and a nutrition coach can write on the same order. Documents start at $15.00, and a plan reviewed by a trainer costs $19.00. Every price is on the pricing page.

The calls, in order

The API is plain HTTP with JSON in and out, and an API key in the Authorization header, the way you already reach a model provider. Here is the whole loop:

POST   /api/public/organisations/sign-up         create the organisation, get a session
POST   /api/org/keys                             create an API key (session only, shown once)
PUT    /api/org/webhook                          set the URL we call on delivery
POST   /api/org/deposits                         start a deposit (session only)
POST   /api/org/clients                          add a user under your own reference
POST   /api/org/clients/:id/orders/plan          order a plan in their name
POST   /api/org/clients/:id/orders/evaluate      or an evaluation
POST   /api/org/clients/:id/orders/review-plan   or a review of your model's plan
GET    /api/org/clients/:id/orders/:orderId      status and price of one order
GET    /api/org/balance                          what is available in the pot

Every endpoint has its own page in the API reference with a complete example request and both schemas. The same spec is published as OpenAPI at https://caremcp.com/openapi.json, so you can generate a client or hand it to a coding agent.

Step by step

1. Sign up and create a key. Sign up as an organisation with a name, an email, a password and your country, accepting the organisation terms and the data processing agreement that comes with them. With the session you get back, create an API key. Keys are stored as hashes, listed by prefix only, and can be revoked at once. A key cannot create other keys.

2. Set your webhook. Give us an https URL. We sign every delivery with a secret shown when you set it, so you can verify the call came from us, and we retry until you answer.

3. Add credit. With the session, not a key, start a deposit; it opens a payment page. The balance is credited when the payment is confirmed, a receipt goes by email, and an organisation with an EU VAT number outside Sweden gets reverse charge. Each delivered document is charged to this one balance, across all your users.

4. Create a client. One call with your own reference for the user (externalRef), their birth date, country and language, and healthConsent: true. That last field means you have obtained the user's explicit consent to our health data notice and hold the record. There is no name, no email and no sign-in for the user. They stay yours.

5. Place an order. Post a brief to the protocol's endpoint, naming the professions. The brief follows published standards: a PAR-Q+ health declaration, SMART goals, session-RPE, a food record, NSCA's needs analysis, FITT-VP and more. The answer is the order with its status, or a refusal that says why.

6. Get the webhook. When a professional delivers, we call your webhook with the order's id and status. Documents usually arrive within two days of a professional taking the order, which is a usual time and not a guarantee.

How it refuses

An API your product depends on should fail clearly. Ours says why and whose fault it is:

An order's status is always one of queued, assigned, reviewed or refused.

The rules run in code before any professional sees an order: adults only, some countries closed to some orders, a PAR-Q+ yes waiting for a clinician, and goals aimed at treating a condition refused. That keeps your product on the wellness side of the line. Our professionals are certified personal trainers and nutrition coaches, not doctors or dietitians, and every document ends with a Referral section pointing to health care when something calls for it.

Data stays clean on your side

You send us a birth date, a country and a language under your own id, and a brief. You see orders per user, their status and their price, never the brief. The professional sees the brief with age and language only. Everything is stored in the EU, briefs and documents are encrypted in the database, and deleting a client through the API erases their briefs and documents.

Our standard data processing agreement is part of the organisation terms: you are the controller, we are the processor. Our guide to GDPR and health data in an AI fitness product covers what that means for you, and why a human in the loop matters covers the product side.

Testing without spending

A test environment runs the same code with test payments. You can create a client, place an order, have it claimed and delivered, and receive the webhook without spending anything. Write to us for a test key.

Your next step

Read the API reference, then sign up on the organisations page and create your first key. Most teams go from key to first order in a day.