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.
Stop building your own calorie counter: one SDK for food logging
Calorie tracking looks like a feature and behaves like a product. Four TypeScript packages put logging and nutrition screens inside your app, under your brand.
Letting AI agents add nutrition tracking: MCP and llms.txt
Agents now sign up for developer tools. An llms.txt front door and a three-tool MCP let them request SDK access for a human, and never hand them credentials.
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.
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.