Sugar intake calculator

The path is pure deterministic arithmetic with no network calls and no random seed, so coaching apps, meal-planning tools, and prepaid API clients receive identical JSON every time.

What the calculator measures and which inputs you need

Send calorie_intake as a positive finite number of kilocalories per day; aliases calories, kcal, energy_kcal, and calorie_intake_kcal are accepted so wellness apps can map existing field names without renaming payloads. Send guideline_percentage as a positive finite number greater than zero and at most one hundred; if you omit it, the engine uses ten, the common WHO and FDA energy-share cap. Aliases percent, pct, sugar_percent, and added_sugar_percent map to the same field. Missing calorie intake, empty strings, non-finite numbers, and any calorie intake that is zero or negative fail with invalid_input and are not billed. Identical inputs always produce identical JSON because the path never touches the network, a language model, a clock, or a random generator.

Reading the response fields and avoiding common mistakes

On success the response echoes calorie_intake_kcal and guideline_percentage, then sugar_kcal (the energy slice allocated to added sugar), max_added_sugar_g (the headline gram ceiling), and teaspoons using four grams per teaspoon so kitchen spoons can be compared with labels. The field kcal_per_gram is always four, unit is always g/day, formula restates grams equals calories times percentage over one hundred over four, and method is always energy_percent_added_sugar so downstream code can branch without sniffing shapes. Use max_added_sugar_g when a meal planner only needs one scalable daily ceiling; use sugar_kcal when education materials must show the energy budget next to the gram number; use teaspoons when talking to people who think in spoons rather than grams. Do not confuse added sugar with total carbohydrate or with naturally occurring sugars in fruit and milk: this endpoint only scales an energy percentage into grams.

API usage, pricing, coaching workflows, and practical limits

Call the free in-browser sugar intake calculator for quick checks, client education, lecture demos, and grocery-label planning without installing a nutrition spreadsheet. Prefer calorie intakes that already match your product’s daily energy estimate—if you only know macros, convert them to kilocalories first before calling. Keep expectations educational: this is a planning and literacy tool, not a diagnostic medical device, and users with atypical needs should follow clinical guidance rather than any single formula alone. Ten percent of two thousand calories is fifty grams; five percent is twenty-five grams; those two checkpoints are the ones most public-health pages quote, and this calculator reproduces them exactly so your interface never disagrees with a label footnote. Send a JSON body with required calorie_intake (or an alias) and, optionally, guideline_percentage. Use the prepaid API when a wellness SaaS, telehealth intake form, school cafeteria planner, or calorie-tracking pipeline needs a stable contract at $0.002 per successful item; validation failures never consume balance after the engine rejects the request. Pair this endpoint with your own food-logging database: compute the gram ceiling here, then score logged added sugars against max_added_sugar_g on the client. Authors shipping SDKs can map max_added_sugar_g, sugar_kcal, and teaspoons into dashboard cards and export CSV columns labeled gram ceiling, sugar energy, and spoons—the same numbers dietitians write by hand when they apply ten percent of calories divided by four on paper.