Paver gravel base calculator

Zero or negative area or depth are rejected with a clear invalid_input error instead of inventing a delivery ticket from impossible sizes.

How cubic yards of gravel base are computed

The product is the bare geometric volume of the compacted base layer only; it does not add the thin bedding sand course under pavers, does not convert metric square metres or millimetres, and does not look up density to quote tons unless you apply a supplier conversion after the call. On success the response echoes the rounded inputs, publishes cubic_feet and cubic_yards, waste fields, cubic_yards_order for the purchase ticket, formula as the string yd3 equals area times depth over three hundred twenty-four, message as a short English summary, and steps as an ordered array of substitution lines you can assert in tests or show to a client.

How to call the API and what comes back

All numeric fields must be finite; string forms of numbers are accepted when they match a strict finite numeric pattern. Prefer sending numbers rather than pre-formatted strings when you control the client; when you must send strings, avoid unit suffixes or thousand separators that would fail the finite-number pattern. Typical compacted base depths for pedestrian paver patios fall roughly between four and six inches; driveway and light-vehicle slabs often call for six to eight inches or more—always follow local code and the paver manufacturer sheet rather than a generic web default. Send a JSON body with two required fields: area in square feet (aliases plan_area, patio_area, surface, sq_ft, square_feet, A) and depth in inches of compacted base (aliases base_depth, compacted_depth, depth_inches, thickness, base_inches, D). Optionally include waste_percent in the closed interval from zero to one hundred (aliases waste, overage, waste_allowance, spoil); when omitted it defaults to zero so the order volume matches the bare geometric yards. On success the response sets area, depth, depth_ft as depth divided by twelve, waste_percent and waste_factor, cubic_feet, cubic_yards, waste_cubic_yards, cubic_yards_order, unit labels for area depth and volume, formula and message as described above, and steps as the substitution log. Failed validation—missing fields, non-finite numbers, zero or negative area or depth, waste outside zero to one hundred, or values outside absolute limits—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item and zero marginal unit price.

Practical tips, limits, and related searches

Measure plan area from drawings or by length times width of the rectangle you will pave, and depth as the finished compacted base thickness the engineer or manufacturer specifies, using square feet and inches as this calculator expects. Keep inputs inside the published absolute range so products cannot overflow into non-finite results the solver must reject. Prefer this capability when you already know the square footage and the compacted base depth in inches and only need yards to order; if your source is metric, convert to square feet and inches first, then call. If the quarry quotes rock by the ton, multiply cubic_yards_order by the bulk density they publish after the call; this tool intentionally returns yards so quotes stay transparent in the unit suppliers use for loose aggregate tickets. When teaching or writing tests, pair a simple two-hundred-square-foot patio at four inches with a second case that includes ten percent waste, and include a deliberate zero depth to prove the invalid_input path. This landing targets people searching for a paver gravel base calculator, cubic yards of base for patio pavers, compacted aggregate under slabs, or area and depth to yards online; it is not a general gravel weight tool with free-form density, not a count of individual paver stones, not a concrete bag estimator for the slab itself, and not a drainage design check for pipe bedding. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when you deliberately send a zero area to verify error handling. Round-trip checks are easy: recompute area times depth over three hundred twenty-four by hand and confirm cubic_yards matches within the same twelve-decimal rounding used for all numeric fields.