Carb intake calculator

It multiplies them to allocate carb calories, then divides by the standard Atwater factor of four kilocalories per gram to yield a clear daily carb_g figure you can put next to grocery lists, training logs, or coaching dashboards. The free on-device tool and the API share the same contract; successful API items bill at $0.002 against KIT balance while validation failures are not charged.

What the calculator measures and which inputs you need

Daily carbohydrate intake in grams is the amount of digestible carbohydrate that matches a chosen share of total daily energy under the Atwater metabolizable-energy convention used on food labels and in many nutrition textbooks. The formula is simple and transparent: carb calories equal total calories times carb percent divided by one hundred; carb grams equal those carb calories divided by four, because one gram of carbohydrate contributes four kilocalories on the general Atwater scale. Percentages above one hundred also fail validation because a percentage of total energy cannot exceed the whole. Send calories as a positive finite number in kilocalories per day; aliases total_calories, kcal, energy_kcal, calorie_intake, and calorie_intake_kcal are accepted so products that already store energy under another key do not need a translation layer. Send carb_percent as a positive finite percentage of total energy from carbohydrate, at most one hundred; aliases carbohydrate_percent, carbs_percent, carb_pct, percent, and pct map to the same field. The engine echoes the normalized calories and carb_percent, then returns carb_calories_kcal, carb_g, kcal_per_gram fixed at four, unit set to g/day, a formula string you can display in UI help, and method equal to atwater_carb_4kcal_g so clients can branch without sniffing shapes. If either field is missing, non-finite, zero, or negative, the request fails with invalid_input and is not charged. Identical inputs always yield identical JSON because the algorithm never touches the network, a language model, a wall clock, or a random generator—exactly the contract automation and homework-style demos need.

Reading the response fields and common pitfalls

Do not treat the output as a medical prescription: people with diabetes, renal disease, glycogen storage disorders, or clinical diets need professional guidance. On success the response includes calories and carb_percent as cleaned echoes so clients can confirm what was computed without re-parsing free-text forms. The headline planning number is carb_g in grams per day: that is the amount of carbohydrate that would deliver the requested energy share at four kilocalories per gram. The field carb_calories_kcal shows the intermediate energy allocation, which is useful when a dashboard already displays protein and fat calorie columns and needs a consistent third column. kcal_per_gram is always four, unit is always g/day, formula restates carb_g equals calories times carb_percent over one hundred over four, and method is always atwater_carb_4kcal_g for stable versioning of the Atwater carbohydrate path. Use carb_g when a meal planner only needs a daily gram budget; use carb_calories_kcal when you are painting macro pie charts in energy units rather than mass. Extremely large calorie intakes above the published isolate safety ceiling are rejected to keep Worker work bounded. Remember that alcohol and sugar alcohols are outside this endpoint; if your product tracks ethanol energy separately, subtract that before calling or treat this calculator as the carbohydrate slice only of a broader macro plan.

API usage, pricing, coaching workflows, and practical limits

Call the free in-browser carbohydrate intake calculator for quick checks, client education, lecture demos, and grocery-list planning without installing a nutrition spreadsheet. Prefer calorie intakes that already match your product’s daily energy estimate—if you only know BMR or TDEE, resolve that first, then choose a carb percentage appropriate to the goal (for example higher for high-volume endurance blocks, moderate for balanced maintenance, lower for deliberate low-carb experiments). Keep expectations educational: this is a planning and literacy tool, not a diagnostic medical device, and users with atypical clinical needs should follow professional guidance rather than any single formula alone. Send a JSON body with required calories and carb_percent (or their aliases). Use the prepaid API when a wellness SaaS, telehealth intake form, sports nutrition pipeline, or calorie-tracking app needs a stable contract under KIT balance 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 target here, then score logged carbohydrate against carb_g on the client. Authors shipping SDKs can map carb_g and carb_calories_kcal into dashboard cards and CSV export columns labeled daily carbs and carb calories—the same numbers a coach writes by hand when they apply percent-of-calories times four on paper.