Blocks + mortar for a wall
API · /masonry-api
Masonry Estimating API
Masonry estimating maths as an API, computed locally and deterministically — the brick, block and mortar counts a bricklayer, builder or estimator works to. The brick endpoint computes how many bricks a wall needs from its area (or length × height in feet): bricks per square foot = 144 / ((brick length + joint) × (brick height + joint)), so a standard modular brick with a 3/8-inch mortar joint works out to the well-known 6.86 bricks per square foot — a 100 ft² wall is 686 bricks, plus a waste allowance and the mortar bags (about 7 per 1000 bricks). The block endpoint does the same for concrete masonry units: a standard 16×8-inch CMU with a 3/8-inch joint is 1.125 blocks per square foot, with roughly 2.5 mortar bags per 100 blocks. Both endpoints take custom unit face dimensions and joint thickness, add a configurable waste percentage and round up to whole units. Everything is computed locally and deterministically, so it is instant and private. Ideal for construction, masonry-contractor, building-supply and home-improvement app developers, takeoff and material-estimating tools, and trade calculators. Pure local computation — no key, no third-party service, instant. Imperial units (inches and square feet). Live, nothing stored. 2 compute endpoints. This is brick/block and mortar estimating; for poured-concrete volume use a concrete API and for drywall use a drywall API.
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 74 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 3,732
- attiva
- Chiamate totali
- 57
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 5,150 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 5,150 calls/month
- 2 req/sec
- Brick + block + mortar estimating
- No credit card
Starter
€3.95 /mese
- 52,000 chiamate/mese
- 6 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 52,000 calls/month
- 6 req/sec
- Custom units, joints, waste %
- Email support
Pro
€11.10 /mese
- 218,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 218,000 llamadas/mes
- 15 solicitudes/segundo
- Pipelines de despegue y estimación
- Soporte prioritario
Mega
€35.00 /mese
- 1,310,000 chiamate/mese
- 40 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1,310,000 llamadas/mes
- 40 req/seg
- Escala de plataforma
- SLA dedicado
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
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
Block Time API
Konvertieren Sie einen Zeitstempel oder ein Datum in die Blocknummer, die zu diesem Zeitpunkt auf einer von über 100 Blockchains live war, schlüssellos. On-Chain-Analysten, Indexierer und Dashboards benötigen ständig „Welcher Block war Chain X zum Zeitpunkt T“, um den historischen Zustand abzufragen, und „Welche Blöcke decken dieses Zeitfenster ab“, um einen Zeitraum zu scannen. Diese API beantwortet beides – für einen einzelnen Moment und für einen Datumsbereich (Rückgabe des Start- und Endblocks sowie der Blockanzahl und der durchschnittlichen Blockzeit). Live, nichts wird gespeichert. Die Timestamp-to-Block-Ebene für EVM- und Nicht-EVM-Chains gleichermaßen. Unterstützt durch die offene DeFiLlama Coins API.
api.oanor.com/blocktime-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
Mobile Crane Lift API
Mobile-Crane-Lift-Planungsmathematik als API, lokal und deterministisch berechnet – die Lastmoment-, Kippkapazitäts- und Abstützplattenzahlen, die ein Kranführer, Liftplaner oder Rigging-Ingenieur bei einem Hub überprüft. Der Lastmoment-Endpunkt gibt die Last × ihren Arbeitsradius (den horizontalen Abstand vom Drehzentrum zum Haken), die einzelne Zahl, die der Tragfähigkeitsbegrenzer eines Krans überwacht: Eine 5-Tonnen-Last bei 8 m ergibt ein Moment von 40 Tonnenmetern, dasselbe wie 10 Tonnen bei 4 m, weshalb die Diagrammkapazität steil abfällt, wenn der Ausleger ausfährt – das Moment, nicht das Gewicht, kippt den Kran. Der Kapazitätsendpunkt gibt eine vereinfachte Kippbilanz um den Drehpunkt: Die Last, die gerade kippt = Gegengewicht × sein Radius ÷ Lastradius, und die zulässige sichere Last ist ein Stabilitätsbruchteil davon (~75 % auf Abstützungen, ~66 % auf Raupen gemäß den Normen) – eine Lehr-/Plausibilitätszahl, die den Ausleger und das Überbaugerät ignoriert, niemals ein Ersatz für das Lastdiagramm. Der Abstützplattenendpunkt dimensioniert die Tellerplatte: Erforderliche Plattenfläche = Abstützbeinlast ÷ zulässiger Bodendruck (und die Seite einer quadratischen Matte), da Überlastung von schwachem Boden eine Hauptursache für Umkippen ist – ein 30-Tonnen-Bein auf 200 kPa benötigt etwa eine 1,2 m quadratische Matte. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Liftplanungs- und Rigging-Tools, Bau- und Kranbetriebs-Apps sowie Baustellensicherheitsdienstprogramme. Reine lokale Berechnung – kein Key, kein Drittanbieterdienst, sofort. Vereinfacht – verwenden Sie immer das Lastdiagramm des Herstellers. 3 Compute-Endpunkte. Verwenden Sie für Anschlag- und WLL-Lasten eine Rigging-API.
api.oanor.com/crane-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Masonry Estimating API?
Qual è il limite di velocità di Masonry Estimating API?
Quanto costa Masonry Estimating API?
Posso cancellare l'abbonamento in qualsiasi momento?
Masonry Estimating API è conforme al GDPR?
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo slug.
curl https://api.oanor.com/masonry-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/masonry-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/masonry-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/masonry-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.