Chocolate serving calculator

Zero or negative guests, portions, or bar weights fail with invalid_input because a non-positive figure cannot scale chocolate. Successful API calls are billed at $0.002 per item; validation failures are not charged.

How the chocolate grams-and-bars formula works

Because shops sell whole bars, the response also ceilings that quotient to bars_to_buy, which is four, and leftover_g is the extra forty grams you will have if you buy those four bars. Treat total_grams as the planning target, bars as the exact equivalent, and bars_to_buy as the whole bars to put in the basket.

What you send and what you get back

Zero and negative figures fail because chocolate grams scale from a positive guest list and a positive portion, and a non-positive bar weight cannot convert grams into bars. Example: eight guests at twenty-five grams against a fifty-gram bar yields two hundred grams and four bars with leftover zero. The capability does not accept a cacao-percentage enum, does not convert ounces unless you send grams, and does not return dessert-table serving counts beyond the chocolate gram and bar figures. Send two required fields. guests is a finite number of people strictly greater than zero; the same value may arrive under aliases guest_count, people, party_size, or heads when you reuse party-planner form names. portion_g is the desired chocolate per guest in grams, also strictly greater than zero, with aliases portion, portion_grams, grams_per_guest, serving_g, and per_guest_g. An optional bar_g names the weight of one commercial bar; omit it and the engine uses one hundred grams. Aliases bar, bar_grams, bar_weight, and bar_size map onto that field. Numeric strings such as twelve are accepted; empty strings, missing required keys, and non-finite values fail with invalid_input naming the field. On success the response echoes guests, portion_g, and bar_g, reports total_grams as the product, bars as the exact equivalent, bars_to_buy as the ceiling of that quotient so you never under-order a fraction of a bar, leftover_g as the extra grams from buying whole bars, plus formula and method strings for audit logs. Example: twelve guests at thirty grams each with the default bar yields total_grams three hundred sixty, bars three point six, bars_to_buy four, leftover_g forty. Wire total_grams into a kitchen scale plan and bars_to_buy into a shopping list. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.

Where a chocolate serving calculator shows up in real work

Chocolate-shop estimators can store a headcount and a house portion, then emit bars_to_buy without scraping conflicting Pinterest charts. Content pipelines that normalize buy enough chocolate can replace the vague phrase with numeric total_grams and bars_to_buy fields before they emit localized copy. Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance. Pair the free browser run on this page with the priced API when you need the identical mathematical result inside an automated pipeline without re-implementing the product and the ceiling yourself.