# Log what a person ate and read their food diary

> Log what a person ate and read their food diary: 0 companies fully do it, 2 with a limit, 8 carry the tag. Every listing in Cooking, recipes & meal planning with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/cooking.log-food/
- Markdown: https://www.anchorterminal.com/niches/cooking.log-food/index.md (~800 tokens)
- Slim: https://www.anchorterminal.com/niches/cooking.log-food/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/cooking.log-food/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 2 | 8 | 24 | 9 |

## What counts as done

The entry written to the person's own diary through the API with the serving and nutrients, readable back by day, and no duplicate if the call is retried.

How agents ask for it: log two eggs and toast for breakfast; scan this barcode and add it; how much protein did I have this week

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **fatsecret Platform API (fatsecret)**: food_entry.create writes food_id, serving_id, units, meal and date to the person's diary under 3-legged OAuth and food_entries.get reads by day (acc-15), but no idempotency key exists and barcode and NLP need Premier (acc-16).
- **LogMeal (AIGecko Technologies S.L.)**: Manual intakes, barcode intakes and Intakes History by date exist per APIUser on Monitor and above, but the diary is LogMeal's, not one the person already keeps, and intake writes have no idempotency key.

- not this job: Eat This Much Partner API (Eat This Much, Inc.): No diary endpoints in the Partner API; it generates and renders plans only.
- not this job: Edamam (Edamam): Edamam has no per-user food diary; the APIs search and analyse foods and recipes only.
- not this job: Nutritionix API (Syndigo LLC): No diary endpoints: the API parses and looks up foods, including UPCs, but writes nothing to a person's food log.
- not this job: spoonacular (skycraft GmbH): No food diary endpoints; user endpoints cover meal plans and shopping lists only.

## What stops agents finishing

- barcode or natural-language search only on a quote-priced tier
- diary write rights not granted by default
- no idempotency, so a retry logs twice

## Around it

Before: cooking.photo-to-nutrition, cooking.recipe-nutrition. After: health-data.write-nutrition, personal-assistants.daily-summary.

## Where this comes from

Weight 24 of 100 in Cooking, recipes & meal planning: 9 of 27 accounts; most are FatSecret diaries and barcodes, plus one sales-only Nutritionix price

As data: https://www.anchorterminal.com/api/v1/use-cases/cooking.log-food.json, or the MCP tool get_use_case with id cooking.log-food. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
