Bags needed for a volume
API · /mulch-api
Mulch & Material Volume API
Landscape-material volume estimating as an API, computed locally and deterministically. The volume endpoint computes how much mulch, topsoil, compost or gravel a bed needs as area × depth — from an explicit area or from length × width or a circular diameter/radius, with the depth given in metres, centimetres, feet or inches — and reports the result in cubic metres, cubic yards, cubic feet and litres; a 10 m × 5 m bed at 7.5 cm (3 in) deep needs 3.75 m³, about 4.9 cubic yards, and pass a bag size to also get the number of bags (75 fifty-litre bags). The coverage endpoint inverts it: the area a known volume covers at a chosen depth — one cubic yard at 2 inches deep covers about 15 m² (162 sq ft). The bags endpoint returns how many bags of a given litre size supply a required volume. Lengths use unit=m (default) or unit=ft, and depth also accepts depth_cm or depth_inches. Everything is computed locally and deterministically, so it is instant and private. Ideal for landscaping, gardening, home-improvement, nursery, hardscape and contractor-estimating app developers, mulch-and-soil calculators and material-ordering tools, and trade software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is loose-material volume by geometry; for structural concrete mixes use a concrete API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 86 ms
- Server probes · 24h
- Subscribers
- 3,782
- active
- Total calls
- 20
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 6,800 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 6,800 calls/month
- 2 req/sec
- Volume + coverage + bag counts
- No credit card
Starter
€4.30 /month
- 68,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 68,000 calls/month
- 6 req/sec
- Metric & imperial, circular beds
- Email support
Pro
€11.80 /month
- 300,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 300,000 calls/month
- 15 req/sec
- Estimating & material-ordering pipelines
- Priority support
Mega
€37.00 /month
- 1,620,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,620,000 calls/month
- 40 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Landscaping Material API
Landscaping material estimating as an API — the "how much mulch, soil or gravel do I need" maths, computed locally and deterministically. The coverage endpoint works out the volume to cover an area at a depth — in cubic yards, cubic metres, cubic feet and litres — and, given a material or a custom bulk density, the weight in US tons, tonnes and kilograms, plus the number of bags for a given bag size. The area can be entered directly or as a rectangular, circular or triangular bed, and depth in inches, centimetres, feet or metres. The depth endpoint is the inverse: it works out the depth that an available volume (or a number of bags) gives over an area — handy when you already have a load of material. The material endpoint is a reference of typical bulk densities (mulch, compost, topsoil, gravel, sand) and how much area one cubic yard covers at 1 to 4 inch depths. Everything is computed locally and deterministically, so it is instant and private. Densities are typical values and bulk material varies with moisture and compaction, so order around 5–10% extra. Ideal for landscaping and garden-centre tools, hardscaping and bulk-material retailers, and DIY and yard-project planners. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is landscaping-material estimating; for paint, tiles, concrete and bricks use a construction-calculator API.
api.oanor.com/landscape-api
Irrigation Design API
Irrigation-design maths as an API, computed locally and deterministically — the sprinkler numbers a landscaper, irrigation tech or gardener sizes a system with. The precip-rate endpoint gives the precipitation rate in inches per hour from the flow and spacing: PR = 96.25 × GPM per head ÷ the area each head waters (head spacing × row spacing in feet), where 96.25 is the in/hr one gallon-per-minute makes over a square foot — three-GPM heads on a 15 × 15 ft grid lay down about 1.28 in/hr. The runtime endpoint turns a target water depth into a run-time: depth ÷ precipitation rate, divided by the system efficiency because no system is perfectly even, so applying a half-inch at 1.28 in/hr takes about 23 minutes at full efficiency, longer with real-world uniformity. The zone endpoint sizes a valve zone: maximum heads = available flow ÷ each head's GPM, rounded down so you never starve the line — 13 GPM drives five 2.6-GPM heads with nothing to spare. Everything is computed locally and deterministically, so it is instant and private. Ideal for irrigation and landscaping apps, sprinkler-design and contractor tools, smart-controller schedulers, and garden-planning sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For evapotranspiration or weather use a weather API; for material volume use a mulch API.
api.oanor.com/irrigation-api
Garden Pond API
Garden and koi-pond maths as an API, computed locally and deterministically — the numbers behind a backyard water feature, so you do not have to guess at the hose. The volume endpoint turns length, width and average depth into the water volume in cubic feet, US gallons and litres, applying a shape factor (rectangular 1.0, oval or round 0.79, irregular 0.85) because a liner pond never holds the full bounding box: an 8 × 6 ft pond two feet deep is about 96 cubic feet, or 718 gallons. The liner endpoint sizes the flexible liner to fit a pond — length equals the pond length plus twice the maximum depth plus twice the overlap to anchor under the edging stones (same for width), so that same 8 × 6 pond at two feet deep with a one-foot overlap needs a 14 × 12 ft liner and matching underlayment. The stock endpoint turns a water volume into a safe fish load and the pump you need: roughly one koi per 250 gallons (they grow large and dirty) or one goldfish per 20, plus the pump flow in gallons per hour to turn the whole pond over at least once an hour for koi — 718 gallons holds about two koi and wants a ~720 GPH pump before head-height losses. Everything is computed locally and deterministically, so it is instant and private. Ideal for landscaping and pond-installer tools, garden-design and home-improvement apps, koi and water-garden hobbyist sites, and aquascaping calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For pool chemistry use a pool API; for indoor fish tanks use an aquarium API.
api.oanor.com/pond-api
Blackjack Strategy API
Blackjack maths as an API, computed locally and deterministically and exactly — the hand value, the textbook basic-strategy play and the dealer odds, the numbers that hold the house edge to half a percent. The hand-value endpoint scores a hand the way the table does: aces count 11 unless that busts, then 1, so it reports the best total, whether it is soft (an ace still counting 11, safe to hit) or hard, whether it busts, and whether two cards make a blackjack. The strategy endpoint gives the correct basic-strategy action — hit, stand, double or split — for any hand against the dealer's upcard, for the standard 4-to-8-deck game where the dealer stands on soft 17 with double-after-split allowed: 16 against a 10 hits, a pair of 8s always splits, soft 18 doubles against a 6 but hits against a 9, and 11 doubles against everything but an ace. The dealer-odds endpoint gives the dealer's bust probability by upcard — a 5 or 6 busts about 42 % of the time, an ace only 12 % — the reason you stand on stiffs against weak upcards. Everything is computed locally and deterministically, so it is instant and exact. Ideal for blackjack trainers and strategy apps, card-game and casino-game tools, learning aids, and game back-ends. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Educational — not betting advice; the house always keeps an edge.
api.oanor.com/blackjack-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Mulch & Material Volume API?
What's the rate limit for Mulch & Material Volume API?
How much does Mulch & Material Volume API cost?
Can I cancel my subscription anytime?
Is Mulch & Material Volume API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/mulch-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/mulch-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/mulch-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/mulch-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.