Decision impact
Skip unless it explains something
No food log is required for the coach call by default.
Leave this blank unless food, fluid, gut, hydration, heat, energy, or recovery explains how you feel or would change the plan.
Decision impact
Skip unless it explains something
No food log is required for the coach call by default.
Log only if
Energy, gut, heat, hydration, or recovery is relevant
The fastest useful note is the one that explains how you feel or what should change next.
Coach uses
No log needed
Confirmed logs improve fuel, recovery, and Copilot answers. Estimates do not count until saved.
Pick the smallest useful capture method. Estimates and notes only affect coaching after you save or confirm them.
Import from a nutrition app
Use this only if you already track food elsewhere. Imports stay optional and only affect coaching after logs are saved.
Server-to-server connection
Connect nutrition apps without manual copy/paste
Endpoint
POST /api/v1/nutrition/connected-ingestUse either X-Nutrition-Ingest-Token: <NUTRITION_INGEST_TOKEN>. The real token stays on the server and is never shown here.
Loading nutrition connection...
What it changes
Updates fuel notes and rolling nutrition coverage.
Refreshes daily brief, fuel notes, recovery nutrition, and Copilot answers.
Accepted shapes
At least one calorie, macro, fluid, or sodium value is required.
Sample payload
{
"provider": "cronometer",
"logs": [
{
"external_id": "meal-2026-06-19-breakfast",
"logged_at": "2026-06-19T07:30:00-03:00",
"meal_type": "breakfast",
"summary": "Oats, banana, yoghurt, electrolyte bottle",
"calories": 620,
"carbs": 82,
"protein": 31,
"fat": 18,
"water_ml": 500,
"sodium_mg": 700
}
]
}Recent nutrition logs
Confirmed logs are what count. Estimates do not change coaching until reviewed and saved.
Loading recent logs...