Warsaw method calculator

Carbohydrate units, fat-protein units, and the dual-wave idea

This endpoint performs that arithmetic only. It does not know your correction factor, active insulin, or glucose target, and it is not a prescription. Identical inputs always yield identical JSON because the algorithm never touches the network, a language model, a wall clock, or a random generator.

Inputs, validation, duration table, and response fields

Example: sixty grams carbohydrate, twenty grams fat, thirty grams protein, and an insulin-to-carb ratio of ten yields six carbohydrate units, three fat-protein units, six immediate units, three extended units, nine total units, and a five-hour square wave. POST a JSON object with four required finite numbers. carbohydrate_g, fat_g, and protein_g are nutrient masses in grams and must be non-negative; a negative gram amount fails with invalid_input and is not billed, because mass cannot be negative. Aliases include carbs, carb_g, carbs_g, and carbohydrate for carbohydrate_g; fat and lipid_g for fat_g; protein and protein_grams for protein_g. icr is the insulin-to-carb ratio in grams of carbohydrate per unit of insulin and must be a finite number greater than zero; aliases insulin_to_carb_ratio, carb_ratio, icr_g, and grams_per_unit are accepted. Values may arrive as JSON numbers or numeric strings; booleans, objects, empty strings, NaN, and Infinity are rejected with the field named in the message. On success the response echoes the cleaned inputs and returns fat_kcal, protein_kcal, fat_protein_kcal, carbohydrate_units, fat_protein_units, carb_equivalent_g (fat-protein kilocalories divided by ten), immediate_units, extended_units, total_units, and extended_hours. The duration table follows the Warsaw School: zero fat-protein units means zero extended hours; up to one fat-protein unit is three hours; up to two is four hours; up to three is five hours; more than three is eight hours. method is always warsaw_pankowska and unit is U for insulin figures.

Where this calculator is used, pricing, and what it does not do

Diabetes education sites, pump onboarding worksheets, and nutrition apps that already store meal macros can call one shared definition instead of re-coding fat-protein unit math in every client. Classroom demos of dual-wave boluses can show immediate versus extended units side by side with the duration band. People with type 1 diabetes, type 2 diabetes on insulin, or other conditions that use mealtime insulin should follow their prescribing clinician and a registered dietitian or diabetes educator. Keep requests small, document your insulin-to-carb ratio source, and treat the numbers as a transparent worksheet of the Warsaw protocol rather than an automated prescription. Research coordinators who log mixed-meal challenges can pin expected JSON because the algorithm is pure arithmetic with no clock, no random seed, and no network. Successful API items bill at $0.002 against KIT balance; invalid_input is not charged. This is not a medical device: it does not adjust for glycemic index, fibre subtraction, alcohol, residual bolus insulin, illness, exercise, or menstrual variation, and it does not choose a basal rate. Extremely large gram values above the isolate safety ceiling are rejected so a Worker stays bounded. Pair the free on-device check with API automation when you need the same units in a backend log, LMS plugin, or coaching dashboard.