Topic

For Developers

Building nutrition tracking into another product: the BurnWeek SDK and estimation API, calorie ranges as an API contract, integration case studies and agent-ready developer access.

More on For Developers
A terminal fetching llms.txt and calling a developer MCP that returns a calorie estimate.
For Developers

Letting AI agents add nutrition tracking: MCP and llms.txt

Agents now set up developer tools. An llms.txt front door and a three-tool MCP point them at free self-serve API keys, and never hand them the key.

September 29, 20267 min read
An illustrative JSON estimate with low, likely and high calories beside BurnWeek's per-component estimate review.
For Developers

Why calorie estimates should be ranges: honest uncertainty as an API feature

A single calorie number hides portion and label error. Return low, likely and high, and user corrections become cheap and easy to act on.

September 29, 20269 min read
An illustrative signed day_close webhook payload beside a BurnWeek Today screen marked Kitchen closed.
For Developers

Case study: photo and voice food logging inside a fitness marketplace

A fitness marketplace wanted food logging in its own app, in Estonian, with closed days feeding its loyalty programme. How the embed, login and rewards fit.

September 29, 20269 min read