Theoretical stack-effect draft
API · /chimney-api
Chimney & Flue API
Chimney and flue sizing maths as an API, computed locally and deterministically — the draft and dimension numbers a stove installer, sweep or builder runs so a fire pulls cleanly and safely. The flue-size endpoint gives the minimum flue cross-section for a fireplace opening: at least a tenth of the opening area for a square or rectangular liner, a twelfth for a round one (which draws better) — a 36 × 30 inch opening needs about 108 square inches of rectangular flue, or a 10.7-inch round. The draft endpoint gives the theoretical draft from the stack effect, ΔP ≈ 3465 × height × (1/T_outside − 1/T_flue) with temperatures in kelvin, so a 6-metre chimney with 200 °C flue gas on a freezing day pulls about 32 pascals (0.13 inches of water column) — taller and hotter draws harder. The height endpoint applies the 3-2-10 rule: a chimney must finish at least 3 feet above where it pierces the roof and at least 2 feet above anything within 10 feet, whichever is higher. Everything is computed locally and deterministically, so it is instant and private. Ideal for hearth and stove-installer apps, chimney-sweep and inspection tools, building-design calculators, and DIY-safety sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Educational estimates — verify against your appliance listing and adopted code.
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 81 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 3,284
- attiva
- Chiamate totali
- 4
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 420 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 420 Aufrufe/Monat
- 2 req/sec
- Flue size + draft + height
- Keine Kreditkarte
Starter
€5.25 /mese
- 11,000 chiamate/mese
- 6 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 11.000 Aufrufe/Monat
- 6 req/sec
- Kamineffekt-Zug
- E-Mail-Support
Pro
€17.20 /mese
- 72,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 72.000 Aufrufe/Monat
- 15 req/sec
- Installations- und Inspektions-Pipelines
- Prioritäts-Support
Mega
€51.60 /mese
- 245,000 chiamate/mese
- 36 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 245.000 Aufrufe/Monat
- 36 req/sec
- Plattform-Skalierung
- Dedizierte SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Industrial Coatings API
Industrial and protective-coatings maths as an API, computed locally and deterministically — the film-build numbers a coatings inspector, painter or estimator works to, the ones simple paint estimating skips. The coverage endpoint gives theoretical and practical coverage from the coating's volume solids and the target dry film thickness: coverage = 1604 × the volume-solids fraction ÷ the DFT in mils, where 1604 is the square feet a gallon covers at one mil — so a 50 %-solids coating at 2 mils dry covers about 401 ft² per gallon, less a loss factor for overspray and surface profile. The film-thickness endpoint converts between wet and dry film thickness through the volume solids: WFT = DFT ÷ the solids fraction, because the solvent flashes off and the film shrinks, so a 50 %-solids coating laid 4 mils wet dries to 2 mils — the number you check with a wet-film comb as you spray. The transfer-efficiency endpoint gives the real material needed: theoretical gallons ÷ the transfer efficiency, since conventional spray lands only ~25 % on the part, HVLP ~65 %, electrostatic up to ~95 %. Everything is computed locally and deterministically, so it is instant and private. Ideal for coatings-estimating and inspection apps, industrial-painting and protective-coating tools, NACE/SSPC study aids, and spec calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For simple wall-paint area estimating use a paint API.
api.oanor.com/coating-api
HVAC Ductwork API
HVAC-Kanaldimensionierungsmathematik als API, lokal und deterministisch berechnet – die Kanalabmessungen, mit denen ein Installateur oder Planer ein System dimensioniert, damit die Luft leise und effizient strömt. Der Rundkanal-Endpunkt gibt den runden Kanal für einen Luftstrom bei einer Zielgeschwindigkeit aus: Fläche = Luftstrom ÷ Geschwindigkeit (CFM ÷ ft/min = ft²), dann Durchmesser = √(4·Fläche/π) – 400 CFM bei einer Hauptgeschwindigkeit von 700 ft/min benötigt etwa einen 10,2-Zoll-Rundkanal, aufgerundet auf die nächste handelsübliche Größe von 12 Zoll. Der Geschwindigkeits-Endpunkt gibt die Luftgeschwindigkeit in einem Kanal aus Luftstrom und Größe an, rund oder rechteckig – 400 CFM durch einen 12 × 8 Kanal laufen mit 600 ft/min, angenehm leise, während die gleiche Luft in einem 10-Zoll-Rundkanal mit 733 ft/min strömt. Der Äquivalenz-Endpunkt gibt den äquivalenten runden Durchmesser eines rechteckigen Kanals nach der ASHRAE-Beziehung De = 1,30 · (a·b)^0,625 ÷ (a+b)^0,25 an, sodass ein 12 × 8 rechteckiger Kanal die gleiche Luft mit dem gleichen Reibungsverlust wie ein 10,7-Zoll-Rundkanal führt – so können Sie mit einer runden Reibungstabelle dimensionieren und an den verfügbaren Platz anpassen. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für HVAC-Design- und Installateur-Apps, Kanaldimensionierungs- und Auslegungswerkzeuge, Gebäudetechnik-Rechner und Berufsschulhilfen. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Live, nichts wird gespeichert. 3 Compute-Endpunkte. Für Raumluftwechsel verwenden Sie eine Lüftungs-API; für die Kühl-/Heizlast verwenden Sie eine HVAC-API.
api.oanor.com/ductwork-api
Plumbing Code API
Plumbing-code sizing maths as an API, computed locally and deterministically — the fixture-unit and pipe-sizing numbers a plumber, designer or inspector runs from the code book. The dfu endpoint totals drainage fixture units for a set of fixtures (IPC Table 709.1): pass a list like toilet:2,lavatory:3,shower:1,kitchen_sink:1 and it weights each by its discharge — a toilet is 3, a lavatory 1, a tub or shower 2 — for a total of 13, with a grouped full bathroom counting as 6 rather than the sum of its parts. The pipe-size endpoint gives the minimum building-drain size for a DFU load at a slope (IPC Table 710.1(1)): the smallest pipe whose capacity meets the load, so 50 DFU at a quarter-inch-per-foot fall needs a 4-inch drain, with the reminder that any drain carrying a water closet is a 3-inch minimum. The supply-gpm endpoint reads probable peak water demand off the Hunter curve: diversity means 100 supply fixture units draws only about 54 GPM, not the sum of every fixture running at once — the number you size the water service against. Everything is computed locally and deterministically, so it is instant and private. Ideal for plumbing-design and estimating apps, code-check and permit tools, MEP-engineering calculators, and trade-school aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Based on the IPC — verify against the code adopted in your jurisdiction.
api.oanor.com/plumbing-api
Caulk Coverage API
Caulk and sealant coverage maths as an API, computed locally and deterministically — the linear-feet-per-tube and how-many-tubes numbers a builder, glazier or DIYer buys sealant by. A bead of caulk is essentially a thin cylinder, so the coverage endpoint works out the feet a cartridge lays from the bead width: volume per foot ≈ (π/4 × width²) × 12 inches, and a standard 10.1 fl oz cartridge (18.2 in³) lays about 30 feet of a quarter-inch bead, 13 feet of a fat three-eighths or 55 of a fine three-sixteenths — pass cartridge_oz for sausage packs or 28-oz tubes, and a tube count to total it. The tubes endpoint runs it backwards: cartridges needed = (joint length × a waste factor) ÷ feet per cartridge, rounded up, so a 100-foot run of quarter-inch bead with 10 % waste takes four tubes. Everything is computed locally and deterministically, so it is instant and private. Ideal for construction, glazing, weatherproofing and home-improvement app developers, material-estimator and shopping-list tools, and contractor software. Pure local computation — no key, no third-party service, instant. Inches and feet; estimates — tooling and waste vary. Live, nothing stored. 2 compute endpoints.
api.oanor.com/caulk-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Chimney & Flue API?
Qual è il limite di velocità di Chimney & Flue API?
Quanto costa Chimney & Flue API?
Posso cancellare l'abbonamento in qualsiasi momento?
Chimney & Flue 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/chimney-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/chimney-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/chimney-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/chimney-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.