Food databelongs toeveryone.
Search it. Verify it. Add what is missing.
Reuse it anywhere.
01 / Explore
Find the food.
See the source.
Food records should show where the information came from, what it describes, and how confidently it can be reused.
Look up public food knowledge without creating an account.
Preparations, portions, locale, and uncertainty stay attached.
Sources, versions, licenses, and contributors remain visible.
02 / Commons
A commons earns trust in public.
Accepted changes will become movement: new foods, verified portions, source additions, and published packs—drawn only from real repository events.
No accepted changes in the last 24 hours.Most recently verified: Haldiram's Baklava Mix Dry Fruit Tart, en-IN, on September 14, 2026.
- Food
- Accepted new record
- Source
- Evidence attached
- Portion
- Verified serving
- Pack
- Version published
03 / Contribute
What is missing
belongs here too.
This beta is operated and reviewed by the project owner. Suggest a missing food with a public source; accepted changes are published with their review history.
- Chapter 01Name + context
Describe the food, preparation, and locale in your own words.
- Chapter 02Ingredients + portions
Keep original units while nutrition is calculated in canonical grams.
- Chapter 03Sources + review
The owner reviews the source and publishes accepted records. Submission alone does not publish a food.
04 / Build
Take the data.
Make it useful.
The schema, packs, API, and code are inspectable. The tracker is one proof—not the boundary of what can be built.
The commons begins with what we can document together.