Mix material breakdown
API · /concrete-api
Concrete Mix API
healthy
4,345 Subscribers
Concrete mix-design maths as an API, computed locally and deterministically. The mix endpoint breaks down a volume of concrete into its materials from a nominal mix ratio (cement:sand:aggregate, for example 1:2:4): it applies the 1.54 dry-volume allowance, then returns the cement in cubic metres, kilograms and 50 kg bags, the sand and aggregate volumes and masses, and the water from the water-cement ratio — the complete batch for the pour. The quantity endpoint computes the concrete volume of a slab, footing, or round or square column from its dimensions, adds a wastage allowance and gives the dry material volume. The watercement endpoint solves the water-cement ratio, the water or the cement from the other two — the single most important number for concrete strength and durability. Densities used are cement 1440, sand 1600 and aggregate 1450 kg/m³, with a 50 kg cement bag. Everything is computed locally and deterministically, so it is instant and private. Ideal for construction, estimating and site-engineering tools, material take-off and ordering, DIY and builder apps, and civil-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is nominal volume-batch concrete estimating; for retaining-wall earth pressure use an earth-pressure API.
api.oanor.com/concrete-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 72 ms
- Server probes · 24h
- Subscribers
- 4,345
- active
- Total calls
- 80
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 2,000 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- Nominal mix breakdown (cement, sand, aggregate, water)
- Metric and imperial volume units
- 2 requests/sec, 2,000 calls/month
Starter
€9.00 /month
- 15,000 calls / month
- 5 requests / second
- Hard cap (429 above quota, no overage)
- All nominal mix ratios (M5–M25)
- Per-bag cement and water-cement ratio output
- Wastage allowance factor
- 5 requests/sec, 15,000 calls/month
Pro
€24.00 /month
- 80,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- Design-mix proportioning beyond nominal grades
- Material quantities scaled to batch volume
- Density and yield checks
- 15 requests/sec, 80,000 calls/month
Mega
€75.00 /month
- 400,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- High-volume batching and estimation pipelines
- Full grade range with admixture-adjusted ratios
- Priority deterministic compute, no rate spikes
- 40 requests/sec, 400,000 calls/month
Built by
Related APIs
Other APIs with overlapping tags.
Rebar Calculator API
Reinforcement-steel (rebar) maths as an API, computed locally and deterministically. The area endpoint computes the cross-sectional area of a reinforcing bar, a = π/4·d², its mass per metre (a·7850/1e6, steel ρ = 7850 kg/m³), the total area and mass for a number of bars, and — given a required steel area — the number of bars needed and the area provided. The spacing endpoint lays out bars across a section: from the width, the cover, the bar diameter and either a centre-to-centre spacing or a bar count it returns the other, n = floor((width − 2·cover − d)/spacing) + 1, the total steel area and the area per metre of width. The ratio endpoint computes the reinforcement ratio ρ = As/(b·d) of a section from the steel area (or the bars) and the section width and effective depth, as a fraction and a percentage, the single number that governs whether a beam is under- or over-reinforced. Everything is computed locally and deterministically, so it is instant and private. Ideal for structural and site-engineering tools, reinforced-concrete detailing, bar-bending schedules and steel take-off, and civil-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is rebar geometry and quantities; for concrete mix proportions use a concrete API.
api.oanor.com/rebar-api
Construction Calculator API
Construction and material estimating as an API — the everyday "how much do I need to buy" maths for building and renovation jobs, computed locally and deterministically from standard geometry and trade rules of thumb. The paint endpoint works out the litres and number of cans for a surface, allowing for the number of coats and the paint's coverage and deducting doors and windows. The tile endpoint computes how many tiles (and full boxes) a floor or wall area needs from the tile dimensions and a wastage allowance. The concrete endpoint gives the concrete volume in cubic metres, cubic yards and litres — and the number of pre-mix bags — for a slab, footing, wall or round column, with an optional batch quantity. The bricks endpoint computes how many bricks a wall needs from the brick size and mortar joint (default 215×65 mm brick with a 10 mm joint ≈ 60 bricks per square metre). Everything is computed locally and deterministically, so it is instant and private. Ideal for builders' merchants and trade apps, DIY and home-improvement tools, quoting and estimating software, and project planners. Pure local computation — no key, no third-party service, instant. Live, nothing stored. Estimates are guidance — allow for site conditions and follow the manufacturer's stated figures. 4 endpoints. This is materials estimating; for plain unit conversion use a unit-conversion API and for tyre or drivetrain maths use a tyre API.
api.oanor.com/buildcalc-api
Handrail & Baluster API
Railing and baluster layout maths as an API, computed locally and deterministically — the baluster-count, spacing and post numbers a deck builder, fabricator or balustrade designer sets a guardrail out with. The baluster-count endpoint gives the smallest number of balusters that keeps every gap within the safety limit: between two posts n balusters leave n+1 gaps, so the count = ceil((rail length − max gap) ÷ (baluster width + max gap)). The usual guardrail limit is a 100 mm (4-inch) sphere — a child-safety rule — so a 2000 mm rail with 40 mm balusters needs 14 of them at even 96 mm gaps; round up, because one fewer opens the gaps past the limit. The layout endpoint sets out a known count evenly: the gap = (rail length − total baluster width) ÷ (count + 1), the centre-to-centre pitch = baluster width + gap, and the first baluster's centre sits one gap plus half a baluster from the post face, so you mark the first centre and step off the pitch with the last gap landing equal to the first. The post-count endpoint sizes the frame: a run needs one more post than spans, spans = ceil(run ÷ max post spacing), posts = spans + 1, even spacing = run ÷ spans — a 6 m run at a 1.8 m max takes 4 spans and 5 posts at a tidy 1.5 m. Everything is computed locally and deterministically, so it is instant and private. Ideal for deck and balustrade design tools, fabrication and estimating apps, and building calculators. Pure local computation — no key, no third-party service, instant. Uses the common 100 mm infill rule — confirm your local code. 3 compute endpoints. For stair rise and run use a stair API; for fence pickets a fence API.
api.oanor.com/handrail-api
Arch Geometry API
Circular-segment arch geometry as an API, computed locally and deterministically — the radius, arc-length and set-out numbers a mason, joiner, stonemason or CAD user lays a segmental arch out with. A segmental arch is an arc of a circle struck through the two springings and the crown: the from-span-rise endpoint takes the span and the rise (the height of the crown above the springing line) and returns the radius = (span²/4 + rise²) ÷ (2·rise), the central angle it subtends, the arc length along the curve, and the segment area of the void below it — flatter arches with a small rise have surprisingly huge radii. The from-radius-angle endpoint inverts it, returning the chord (span), the rise (sagitta), the arc length and the area from a known radius and central angle, the way a curve struck with a trammel or a router on a pivot is described. The setout-ordinates endpoint gives the practical numbers to mark a template: the rise of the arc above a straight base line at equally spaced stations across the span (y = √(R² − x²) − (R − rise)), so you can plot the heights, connect them and cut a plywood former or bend a batten without a giant compass — the ends come out zero at the springings and the middle equals the rise at the crown. Everything is computed locally and deterministically, so it is instant and private. Ideal for masonry and joinery layout tools, stair and window-head design, and CAD and woodworking calculators. Pure local computation — no key, no third-party service, instant. Segmental (up to a semicircle) arcs. 3 compute endpoints. For road curves use a horizontal- or vertical-curve API; for plain shape areas a geometry API.
api.oanor.com/arch-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Concrete Mix API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Concrete Mix API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Concrete Mix API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Concrete Mix API cost?
Concrete Mix API has a free tier with 100 calls / month. Paid plans start at €9.00 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Concrete Mix API GDPR-compliant?
All requests to Concrete Mix API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.
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/concrete-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/concrete-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/concrete-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/concrete-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
📌 Pinned
🔒 Locked
·
·
·
-
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.