Pancake recipe scaler

Non-positive desired servings fail with invalid_input because a zero or negative pancake count cannot define a meaningful scale.

What pancake recipe scaling means and why batter ratios stay fixed

This pancake recipe calculator accepts a non-empty list of finite numbers as amounts, a strictly positive desired servings or pancake count, and an optional positive base_servings value that defaults to one when omitted so a per-pancake card scales by the desired yield alone. It sets factor equal to servings divided by base servings, then returns both a flat scaled array and an ingredients array that pairs each original amount with its scaled value. Classroom worksheets, meal-prep spreadsheets, and coding kata can assert the same rounded JSON because the arithmetic never depends on the clock or on external data.

How to call the API: inputs, response shape, and validation

Optional names appear at the top level only when at least one label was provided; optional fields are omitted rather than set to null. Prefer numbers rather than pre-formatted unit strings inside amounts; put units in the optional names field instead so one hundred ninety and flour (g) stay separate and machine-readable. Send a JSON body with amounts as a required array of finite numbers—or a comma-separated string on text forms—plus servings for the desired pancake or serving count. servings (aliases pancakes, desired, desired_servings, pancake_count) must be finite and strictly greater than zero; zero, negative, and non-numeric values fail with invalid_input and are never charged. Optional base_servings (aliases original, original_servings, from_servings, yield, recipe_servings, base) is the yield the listed amounts were written for; it defaults to one when omitted and must be strictly positive when provided, because dividing by a non-positive base cannot define a pancake scale. Optional names (aliases labels, ingredients) align string labels with each amount in the same order; extra or missing labels are padded or truncated so the row count always matches. Absolute values must stay within one trillion, and the list length is capped so a Worker can finish quickly. On success the response echoes rounded amounts, scaled values, factor, count, servings, base_servings, ingredients rows with index amount and scaled plus name when present, formula, message, and ordered steps. Failed validation—empty amounts, non-finite numbers, missing servings, or non-positive servings—returns invalid_input. Pricing is a flat $0.002 per successful request with unit item.

Practical tips for brunch batches, limits, and related tools

Near-zero positive values are allowed for tiny salt or vanilla lines if your card uses them, but zero desired servings are always rejected. This landing targets people searching for a pancake recipe, scale pancake ingredients, or pancake servings calculator; it is not a unit converter, not a buttermilk substitute, and not a full meal-plan system. Round-trip checks are easy: recompute each amount times factor by hand and confirm it equals the published scaled entry within the same twelve-decimal rounding, and confirm that changing only the desired servings scales every line proportionally without rewriting the original card. Always reject non-positive servings in client forms before submit when you can; the API will still throw a clear invalid_input message if zero or a negative pancake count slips through, because targeting zero cakes is not a meaningful batch. When scaling a classic eight-pancake card, set base_servings to eight and servings to the number of cakes you plan to pour—twelve for a family breakfast, twenty-four for a small brunch. For a recipe already written as one pancake, omit base_servings (it defaults to one) and set servings to the full stack so factor is the pancake count itself. Keep units consistent across the list: if flour is grams, keep sugar and melted butter in grams too, and put teaspoons or eggs only on lines that truly use those units. Prefer sibling cook tools when you need generic kitchen recipe scaling or cocktail batch yields, then use this endpoint when the intent is pancake batter. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately send servings zero.