GOFA AI services

GOFA AI services are authenticated, client-scoped features for user-facing applications. The routes in this section use a Firebase ID token and derive the client from the request host. The relevant module must also be enabled for the client.

Use the product guide that matches the feature you are integrating:

• AI Move — exercise catalog and per-user exercise sessions.
• AI Nutrition — meal analysis, food logs, plans, and nutrition chat.
• AI Training — plans, routine queues, and routine runs.
• Water Intake — hydration logs, goals, and history.
• Wellness Chat — a streaming 1CARE wellness assistant.

Authentication

Sign the user in with Firebase and send the resulting ID token on each API request:

Authorization: Bearer <firebase-id-token>

See User authentication for the Firebase sign-in and token handoff flows. These routes are separate from the Commercial API key documented in Authentication, and from the backend ClientToken used by client directory routes.

Client and module boundaries

The server derives clientId from the request hostname and checks the feature module before serving data. A user token only accesses data belonging to the authenticated user and its client. Do not put Firebase tokens in URLs or browser source code.

This public section covers the user runtime and approved user-facing handoffs. Admin record queries, B2B authoring/catalog management, provider proxy routes, and other operator-only surfaces are outside this API reference.