Web app API
The product's own API surface — chat, vitals, calendar, documents, scan, and more.
The web app API is where the real product lives. It's session-authenticated (see Authentication), follows the shared conventions, and is consumed by the web, mobile, and watch clients alike.
This page is a map, not an exhaustive spec — it groups the surface so you know
where to look. All endpoints are under /api.
Identity & profile
| Endpoint | Purpose |
|---|---|
/api/auth/* | Sign-in, sign-up, password reset, OAuth, session |
/api/profile | Read/update your profile and provider toggles |
/api/account/delete | Full account + data teardown |
/api/memory | List and delete the AI's long-term memories |
AI & knowledge
| Endpoint | Purpose |
|---|---|
/api/chat | Streaming AI chat with tool-calling |
/api/chat/history | List, rename, and delete past chats |
/api/chat/suggestions | Contextual follow-up chips |
/api/documents | Upload, list, view, and delete documents (RAG) |
/api/websearch | Web search tool backing |
Voice & avatars
| Endpoint | Purpose |
|---|---|
/api/speech, /api/tts/stream | Text-to-speech (single + streamed) |
/api/transcribe | Speech-to-text |
/api/voice | Available voices |
/api/avatar/*, /api/tavus/* | Real-time video avatar sessions |
Health domain
| Endpoint | Purpose |
|---|---|
/api/vitals, /api/vitals/summary | Normalized vital readings |
/api/wearables | Connected device registry |
/api/scan, /api/deepaffex/* | AverScan capture + analysis |
/api/nutrition, /api/water | Meal and hydration logging |
/api/fitness/workouts | Deliberate workout logging |
/api/menstrual/*, /api/peptides/*, /api/symptoms, /api/journal | Module logging |
Scheduling & care
| Endpoint | Purpose |
|---|---|
/api/calendar | Calendar CRUD + Google two-way sync |
/api/integrations/google | Calendar sync kill-switch |
/api/telemedicine/*, /api/appointments | Find, book, and manage visits |
/api/notifications | In-app notification feed |
Platform & watch
| Endpoint | Purpose |
|---|---|
/api/watch/* | Watch credentials, chat, and vitals intake |
/api/blob | Authenticated proxy for private files |
/api/install/* | App install availability (TestFlight / APK) |
/api/admin/* | Scoped admin backoffice (requires admin scopes) |
Webhook intake endpoints (e.g. build and telemedicine webhooks) verify a signed secret on every call and are not meant for direct client use.
Working with the chat endpoint
The chat endpoint is the most powerful — and the most representative of the platform's style:
Send the conversation
POST the message history. The server injects your profile and memories, then selects an appropriate model and tool set.
Read the stream
The response streams back text, tool calls, and tool results as they happen.
Persist happens server-side
Chats and messages are saved for you; the history API lets you manage them later.
Mode changes the tools
The same chat endpoint behaves differently by mode: a document-viewer request swaps document-navigation in for general search, and voice requests trim the tool set to what makes sense out loud. One endpoint, several personalities.