Nutrition numbers you can actually trust to be exact

Most restaurants that publish nutrition information publish it as a PDF, or as a slow official app buried a few taps deep, or as a chart of whole pre-built menu items that doesn't tell you what happens when you swap the bread, skip the cheese, or add a second scoop of guac. If you actually wanted to know what your specific order costs — not the "regular" version, yours — you were stuck doing the arithmetic yourself from a PDF, or trusting a random blog's rough estimate.

Third-party "nutrition calculators" often make this worse: they average a handful of menu items into a single number, or extrapolate calories from a photo, or just guess. That's fine for a ballpark, but it isn't the same as knowing what's actually in your food.

The idea behind this site: when a restaurant publishes real per-ingredient nutrition data, there's no reason a calculator should still be guessing. Build the exact order, sum the exact ingredients, get the exact number.

1. Source directly from the restaurant. Each brand's own published nutrition data — an official PDF, nutrition-facts chart, or public data endpoint — not a third-party estimate.
2. Store it at ingredient level. Every bread, meat, scoop and topping is its own row with its own calories, fat, sodium, carbs and protein — not one number per finished item.
3. Sum only what's actually selected. A build's total is the sum of whichever ingredients are switched on, which is why changing one topping updates every number on the page, not just the calorie count.
4. Verify against known figures. Before a calculator ships, standard builds are checked against the brand's own published totals for common orders. If the math doesn't match, the data gets fixed before the page goes live.
5. Skip brands that don't publish enough detail. If a restaurant only publishes per-item totals with no ingredient breakdown, there's no calculator for it yet — a guess dressed up as a precise number is worse than no number at all.