Official Japanese chain-restaurant nutrition data, ready for your product.

Name: Japanese restaurant & convenience-store chain nutrition data (Tabecal)
Creator: tabecal
License: https://tabecal.com/en/business/#terms

192 chains, 36,546 rows of nutrition facts, prices, allergens, change history and store coordinates — official published values only, updated every business day. Delivered as a REST API, scheduled CSV/JSON/SQLite drops, or a one-off bulk export. For nutrition apps, dietitian tools, competitive monitoring and research.

Chains: 192
Item × size rows: 36,546
Allergen tables: 75
Store coordinates: 28,936
Version history since: 2026-08-16〜
Updates: Daily

Allergens: 393,896 rows (item × allergen). Prices only where published. null = not published by that chain.

How it is delivered

REST API / MCP

JSON. Try it without a key (200 requests/day). An MCP server for AI agents runs on the same data.

API docs & pricing

Scheduled drops (zip)

CSV, JSON and SQLite with a data dictionary and SHA256 sums. Current values, full version history, change events, allergens and stores. Monthly or weekly.

Download the sample

Menu-change monitor

New, discontinued and changed items, dated. Last 30 days: 2125 new, 2042 discontinued, 2425 changed. Weekly e-mail digests for competitive monitoring.

See the last 30 days

Who uses it

Nutrition & health apps

Skip building a Japanese restaurant menu database. item_key is a stable ID, so daily updates merge into your users’ logs.

Dietitian & health-guidance tools

Evidence for “what to order at the places you actually go” — official values only, so sources can be cited in records.

Chain HQs & food manufacturers

Track competitors’ new items, discontinuations and nutrition/price revisions with dates. Benchmark your own line-up.

Research & education

Free for research and teaching (attribution and a copy of the output requested).

AI agents & indie developers

Use the free API tier and MCP as they are. Choose Developer or above for commercially distributed apps.

Pricing (JPY, tax incl.)

Plan	What you get	Per month
Free	API 200 req/day, 50 rows/req. Attribution required. Trials, hobby, AI agents	¥0
Developer	API 2,000 req/day, 1,000 rows/req. Monthly zip (CSV/JSON/SQLite, full history)	¥3,300
Business	API 10,000 req/day. Weekly zip. Weekly menu-change digest by e-mail (choose chains)	¥22,000
Enterprise	Full bulk export with history, custom extracts (chains, fields, periods), SLA, invoicing	from ¥55,000
One-off reports	Revision & price-change reports, genre benchmarks, full history of named chains (PDF/Excel)	¥5,500–33,000
Research & education	Universities, public research bodies, students. Developer-equivalent, free (attribution, share results)	¥0

Cancel any time. Card or invoice (bank transfer). Paid plans start with a 14-day trial key (500 req/day).

How to start

Tell us your use case, expected volume and plan through the form below (put “Data” in the subject).
Within 1–2 business days you receive a trial key and a sample drop.
After review and payment (card or invoice), the production key and scheduled drops begin.

Data dictionary (main columns)

Column	Meaning
`item_key`	Stable ID per item × size
`chain / chain_slug / genre`	Chain name, URL slug, genre code
`name / size / category`	Item name, size, official menu section
`kcal`	Energy (kcal)
`protein_g / fat_g / carb_g`	Protein / fat / carbohydrate (g)
`fiber_g / sugar_g`	Fiber / sugars (g), where published
`salt_g / sodium_mg`	Salt equivalent (g) / sodium (mg)
`caffeine_mg / weight_g`	Caffeine (mg) / weight (g), where published
`price`	Price incl. tax (JPY), where published
`valid_from / valid_to / last_seen`	Validity window of this version (blank = current) and last verified date
`allergens: allergen / status`	28 Japanese labelling allergens × contains / may_contain / none
`menu_changes: event / field / old / new`	added / removed / changed with old and new values
`stores: lat / lon / addr_* / opening_hours`	Store coordinates, address, opening hours (© OpenStreetMap contributors, ODbL)

null / blank means “not published by that chain”. Nothing is estimated. The full dictionary ships with the sample zip README and DATA_DICTIONARY.md in each drop.

tabecal_sample.zip (94 KB) — 3 chains’ current values and history, last 30 days of changes, one allergen table and 300 store coordinates. Sample change report

Terms (summary)

Values are each chain’s official published figures. Final verification is the user’s responsibility. Not for medical decisions on their own.
Display and analysis inside your app or internal systems is fine. Redistributing or reselling the data itself is not.
Attribution: “Data: Tabecal (tabecal.com) / official published values”. Store coordinates © OpenStreetMap contributors (ODbL).
Chain names and trademarks belong to their owners. We organise published information and are not affiliated with any chain.
If a chain asks us to stop, its data may be removed from drops.
Cancel any time; no pro-rated refunds. 30 days’ notice before any shutdown.

FAQ

Where does the data come from?

Each chain’s official nutrition tables (PDF, HTML or JSON). The sha256 and first/last-seen dates of every source file ship as source_provenance.

How is it different from other databases?

No estimates, a version history (when each value changed), 28 labelling allergens and campaign metadata (new / limited-time / serving hours for Skylark brands).

How often is it updated?

Every business day, all chains are re-fetched and only diffs are recorded. Check meta.data_date or /api/v1/health.

How are gaps handled?

Values a chain does not publish stay null — for example protein is null for chains that publish energy only.

Can I get a custom extract?

Yes — by chain, field, period or genre, in Excel, or the full history of named chains, under Enterprise or as a one-off report.