Nom JSON API
Nom’s full catalog — 3,537 fast food items across 31 chains, every size the chains publish, each with complete nutrition and its A–F Nom Score — is available through the Nom JSON API.
Base URL https://nom.now/api/v1
GET only · JSON responses · CORS *. Every response carries source, data_date
(the newest date any chain’s figures were checked against its own source), and canonical nom.now URLs
so you can cite it.
Payment
Each IP address gets 3 free lookups per day across the JSON API and MCP server. The allowance resets at midnight UTC. Additional lookups cost $0.01 in USDC.e on Tempo through the Machine Payments Protocol.
- Send your GET request. After the free lookups, Nom returns HTTP
402with a payment challenge inWWW-Authenticate. - Authorize the payment with a compatible Tempo wallet. Retry the same request with that credential in
Authorization. - The response includes the JSON result and a
Payment-Receiptheader.
If the request times out or returns 503 after you authorize payment, retry the same request
with the same credential before the challenge expires.
Endpoints
Optional query params: limit (search, healthiest, compare) and restaurant (scopes
search/healthiest to one chain by slug). diet accepts vegan, vegetarian,
or gluten-free, and keeps only items whose claim is true.
Item fields
dietary holds three claims, vegetarian, vegan and
gluten_free, each in one of three states:
true: the chain’s own data supports it, through its own vegetarian or vegan mark or its own ingredient and allergen statements. Forgluten_free, the chain lists wheat in none of what the item contains, may contain or may pick up from shared equipment and, where it publishes an ingredient statement, that names no other gluten grain. That is what the chain’s data lists, not a gluten-free claim:gluten_statementthen carries the chain’s own words on gluten or cross-contact, where it has any.false: the item’s own data rules it out: an animal ingredient, a milk or egg allergen, meat in its name, or forgluten_freewheat in any of those three statements.null: no claim either way. The chain publishes nothing that settles it (forgluten_free, no allergen data for the item).nullis notfalse.
on_national_menu: false for an item the chain still publishes figures
for but no longer sells on its current national menu (regional, seasonal or retired). healthiest never
returns one.
data_checked: the date (YYYY-MM-DD) this item’s figures were checked
against the chain’s own source, or null where none is recorded, as for chains whose figures come from a
third-party site.
data_edition, present only when data_checked is null because the
figures carry the chain document’s own edition date instead (Raising Cane’s July 2025 guide): that date.
less_than_one, present only when the chain prints a figure as “<1”: the
nutrition fields printed that way. Their number is 0.5, a midpoint for totals and scores;
show them as “<1”.
less_than, present only when the chain prints a figure as “<N” for another N (Raising
Cane’s prints “< 5 mg” cholesterol): each such nutrition field with its N. Its number is N / 2, the same
kind of midpoint; show it as “<N”.
On /restaurants, item_count counts every item the API serves for the chain, each size
separately and off-menu items included; product_count counts each product on the national menu once, as
the site does.
Example
tempo request --max-spend 0.01 https://nom.now/api/v1/item/mc-big-mac
{
"id": "mc-big-mac",
"name": "Big Mac",
"category": "Burgers",
"restaurant": { "id": "mcdonalds", "name": "McDonald's" },
"nutrition": {
"calories": 580, "total_fat": 34, "saturated_fat": 11,
"sodium": 1060, "total_carbs": 45, "dietary_fiber": 3,
"sugars": 7, "protein": 25
},
"nom_score": {
"overall": 63, "grade": "C", "summary": "Watch the sodium.",
"components": [
{ "component": "sodium", "per_100_cal": 182.8, "unit": "mg", "rating": "poor" },
{ "component": "protein", "per_100_cal": 4.3, "unit": "g", "rating": "good" }
]
},
"dietary": { "vegetarian": false, "vegan": false, "gluten_free": false },
"on_national_menu": true,
"data_checked": "2026-11-15",
"url": "https://nom.now/mcdonalds/mc-big-mac",
"source": "Nom — fast food nutrition + A–F health scores (nom.now)",
"data_date": "2026-11-16"
}
Rate limits & fair use
The API allows 20 HTTP requests per minute per IP, including payment retries.
If you receive HTTP 429, wait for the time in Retry-After. Keep the attribution included in
each result and follow our Terms when using the data.
Need more than that? If you’re building an app, pulling bulk data, or using Nom commercially, the public limit won’t cut it — email contact@reindexventures.com and we’ll set you up with higher-volume or commercial access.
Wiring this into an AI assistant? The Nom MCP server exposes this same data as tools for clients that support Tempo payments.