Conversation
A coach your users can talk to. Replies are grounded in the person's current context and your content, never invented.
POST /v1/threads/{ref}/turns
Kinellect talks with your users, builds safe workouts from your own exercise catalog, and decides what each person should do today. Your app keeps its users, its content and its brand.
Early access opens soon. First integrations are onboarding now.
POST /v1/threads/{ref}/turns202 durable Operationconnector context, exercisescompleted validated replyEnable only what your product needs. Every capability follows the same pattern: ask, receive an Operation, poll the result.
A coach your users can talk to. Replies are grounded in the person's current context and your content, never invented.
POST /v1/threads/{ref}/turns
Workouts assembled only from exercises in your catalog, validated against the person's constraints before you see them.
POST /v1/workout-drafts
A clear decision for today: train, rest or mobility. Deterministic, explainable, and aware of recent activity and recovery.
POST /v1/daily-plans
When a user approves a workout, Kinellect asks your system to save or schedule it and reports only what your system confirmed.
POST /v1/workout-acceptances
Report a finished workout and get a short, relevant coach reaction, plus recovery signals that shape the next sessions.
POST /v1/events
Preferences a person states in conversation, remembered with their source so coaching stays consistent over time.
source-linked preferences
Kinellect never reads your database. Everything it knows arrives through the context you send and one small service you host.
These rules are enforced in code and covered by tests. They are not settings you have to remember to switch on.
Row-level security on every tenant table. A reference from another tenant behaves exactly like one that does not exist.
Workouts use exercises your connector returned. Text is rendered from verified sources and recorded outcomes.
Pain, injury and equipment constraints you send are enforced before a workout is ever proposed.
One call erases a person's coaching data and blocks accidental re-registration. Nothing lingers in the application.
Every write takes an idempotency key. Long work runs as durable Operations that survive restarts.
Per-capability token and cost ceilings, per Operation and per day, reserved before each model call.
A strict, typed API with a guide written for people and for machines.
# Ask the coach a question for one of your users curl -X POST https://api.kinellect.com/v1/threads/$THREAD/turns \ -H "Authorization: Bearer $KINELLECT_TOKEN" \ -H "Idempotency-Key: $(uuidgen)" \ -H "Content-Type: application/json" \ -d '{"message": "My knee felt sore after squats. What now?"}' # 202 Accepted { "operation_ref": "0f6e7b1c-…", "state": "queued" } # Poll until it is done curl https://api.kinellect.com/v1/operations/0f6e7b1c-… \ -H "Authorization: Bearer $KINELLECT_TOKEN" { "state": "completed", "result": { "role": "assistant", "message": "Let's ease off loaded knee work today…" } }
We are onboarding the first fitness and physiotherapy products now. Leave your work email and we will contact you when a place opens.