oanor
Iscriviti gratis
Mercata Prezzi Caratteristiche Accedi

API · /ductwork-api

HVAC Ductwork API

salutare 3,153 Abbonati

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.

#hvac #ductwork #duct-sizing #airflow #construction #developer-tools
api.oanor.com/ductwork-api
Ottieni una chiave API Prova nel parco giochi → Contatta provider

Specifica leggibile dalle macchine, così gli agenti AI possono integrare questa API.

/api/ductwork-api/openapi.json
/api/ductwork-api/llms.txt

Individuazione: GET /api/index.json elenca ogni API.

HVAC Ductwork API — live data on the oanor API marketplace

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,153
attiva
Chiamate totali
76
ultimi 7 giorni
status Pagina di stato completa → · 12 sonde/24h

Prezzi

Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.

Free

Gratis

  • 450 chiamate/mese
  • 2 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 450 Aufrufe/Monat
  • 2 req/sec
  • Rundkanal + Geschwindigkeit + äquivalent
  • Keine Kreditkarte
Accedi per abbonarti

Starter

€5.80 /mese

  • 12,000 chiamate/mese
  • 6 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 12.000 Aufrufe/Monat
  • 6 req/sec
  • ASHRAE-Äquivalentdurchmesser
  • E-Mail-Support
Accedi per abbonarti

Pro

€18.10 /mese

  • 78,000 chiamate/mese
  • 15 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 78.000 Aufrufe/Monat
  • 15 req/sec
  • Design- & Takeoff-Pipelines
  • Prioritäts-Support
Accedi per abbonarti

Mega

€53.40 /mese

  • 255,000 chiamate/mese
  • 36 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 255.000 Aufrufe/Monat
  • 36 req/sec
  • Plattform-Skalierung
  • Dedizierte SLA
Accedi per abbonarti

Costruito da

P
PremiumApi

Correlato APIs

Altro APIs con tag sovrapposti.

HVAC Air-Side Load API — oanor API marketplace

HVAC Air-Side Load API

HVAC air-side heat maths as an API, computed locally and deterministically with the classic standard-air factors — the sensible, latent and airflow numbers a mechanical engineer or HVAC technician sizes ducts and equipment with. The sensible endpoint gives the sensible heat an airflow carries to change temperature: Qs = 1.08 × CFM × ΔT (dry-bulb difference), where the 1.08 bundles standard-air density and specific heat — 2,000 CFM across a 20 °F difference is 43,200 BTU/hr, 3.6 tons — with the result in BTU/hr, tons and kW. The latent endpoint gives the latent (moisture) heat: Ql = 0.68 × CFM × ΔW, where ΔW is the humidity-ratio difference in grains of water per pound of dry air, the dehumidification part of a cooling load that runs high in humid climates and from people and cooking, and why air conditioners are sized on total, not just temperature. The airflow endpoint inverts the sensible relation: CFM = sensible load ÷ (1.08 × ΔT), the supply air needed at a chosen supply-to-room temperature difference (comfort cooling runs ~18–22 °F below room), the number that sets fan and duct size — sanity-checked against ~400 CFM per ton. Everything is computed locally and deterministically, so it is instant and private. Ideal for HVAC-design and load-calc tools, mechanical-estimating and commissioning utilities, and building-engineering apps. Pure local computation — no key, no third-party service, instant. Standard-air factors — adjust for altitude. 3 compute endpoints. For room rule-of-thumb sizing use an HVAC API; for moist-air properties a psychrometric API; for duct sizing a ductwork API.

api.oanor.com/hvacload-api

 Electric Motor FLA API — oanor API marketplace

Electric Motor FLA API

Electric-motor electrical maths as an API, computed locally and deterministically — the full-load-current, NEC-sizing and starting-current numbers an electrician, panel designer or estimator runs for every motor circuit. The full-load-amps endpoint gives the motor current from its power, voltage and phase: FLA = (output ÷ efficiency) ÷ (√3 × volts × power factor) for three-phase (drop the √3 for single-phase) — a 10 hp, 460 V, three-phase motor at 90 % efficiency and 0.85 power factor draws about 12.2 A — and it also returns the input kW and kVA. The sizing endpoint applies NEC Article 430 from the full-load current: branch-circuit conductors at 125 %, overload protection at 115–125 % by service factor, and branch-circuit short-circuit/ground-fault protection up to 250 % for an inverse-time breaker or 175 % for a time-delay fuse — the larger protection lets the inrush pass while the overload guards the windings. The starting endpoint gives the locked-rotor (inrush) current, about six times full-load for an across-the-line start, the figure that sets the voltage dip and why soft starters and VFDs exist. Everything is computed locally and deterministically, so it is instant and private. Ideal for electrical-design and estimating tools, panel-builder and field utilities, and engineering calculators. Pure local computation — no key, no third-party service, instant. Calculated values — use the NEC FLC tables for code work. 3 compute endpoints. For general three-phase power use a three-phase API; for conduit fill a conduit API.

api.oanor.com/motorfla-api

 Heat Pump COP API — oanor API marketplace

Heat Pump COP API

Heat-pump and refrigeration performance maths as an API, computed locally and deterministically — the efficiency numbers an HVAC engineer, energy auditor or heat-pump installer actually works with. The cop endpoint gives the coefficient of performance and the US EER rating from the thermal capacity and the electrical power: a unit moving 7 kW of heat on 2 kW of electricity has a COP of 3.5 (an EER of 12), meaning 3.5 units of heating or cooling for every unit of electricity — which is why a heat pump beats resistance heating, where the COP is exactly 1. The carnot endpoint gives the unbeatable ideal limit set only by the absolute temperatures — heating = Th ÷ (Th − Tc), cooling = Tc ÷ (Th − Tc) in kelvin, where heating COP always equals cooling COP plus one — and, given a real COP, the second-law efficiency that says how close the machine runs to that ceiling; the smaller the temperature lift, the higher the limit, which is why ground-source and low-temperature systems beat air-source on a cold day. The capacity endpoint turns electrical power and a COP into the delivered heating or cooling in kilowatts, BTU per hour and tons of refrigeration — the extra energy over the electricity is pulled from the outside air, ground or water. Everything is computed locally and deterministically, so it is instant and private. Ideal for HVAC and refrigeration engineers, energy auditors, heat-pump and building-performance tools, and sustainability dashboards. Pure local computation — no key, no third-party service, instant. Estimates at the stated conditions — real COP falls as the temperature lift rises. 3 compute endpoints. For room sizing use an HVAC BTU API; for moist-air properties use a psychrometric API.

api.oanor.com/heatpump-api

 Steam Boiler API — oanor API marketplace

Steam Boiler API

Steam-boiler engineering maths as an API, computed locally and deterministically — the three numbers a boiler operator, plant engineer or steam-system designer actually works with. The boiler-hp endpoint converts a required heat output into boiler horsepower (heat ÷ 33,475 BTU/hr, the standard definition), the equivalent steam output in pounds per hour "from and at" 212 °F (34.5 lb/hr per BHP) and the output in kilowatts — a 1,000,000 BTU/hr load is about 29.9 BHP or 1,031 lb/hr of steam. The factor-of-evaporation endpoint gives the real capacity for your feedwater: the factor = (the total heat of the steam − the feedwater heat) ÷ 970.3, always greater than one because the boiler must add the sensible heat to bring water up to boiling, so a boiler rated "from and at" 212 °F actually makes less with 60 °F feedwater — which is exactly why preheating feedwater with an economiser raises capacity and saves fuel. The blowdown endpoint gives the continuous blowdown rate to hold the boiler water within its dissolved-solids limit: blowdown = steam × feedwater TDS ÷ (boiler limit − feedwater TDS), with the cycles of concentration and the blowdown as a percentage of feedwater — better feedwater means more cycles, less blowdown and less wasted hot water. Everything is computed locally and deterministically, so it is instant and private. Ideal for boiler operators, steam-plant and HVAC engineers, energy auditors, water-treatment specialists and process-engineering tools. Pure local computation — no key, no third-party service, instant. Engineering estimates — verify against the manufacturer data and local code. 3 compute endpoints. For moist-air properties use a psychrometric API; for compressed air use a compressor API.

api.oanor.com/boiler-api

Domande frequenti

Risposte rapide su prezzi, quote e integrazione.

Come ottengo una chiave API per HVAC Ductwork API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama HVAC Ductwork API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di HVAC Ductwork API?
Il piano gratuito consente 1 richiesta al secondo. I piani a pagamento arrivano fino a 50 richieste al secondo nel piano Mega. I limiti rigorosi restituiscono HTTP 429 oltre la quota — nessuna spesa imprevista.
Quanto costa HVAC Ductwork API?
HVAC Ductwork API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €5.80 / mese con quote più alte e limiti di velocità più rapidi.
Posso cancellare l'abbonamento in qualsiasi momento?
Sì. I piani sono fatturati mensilmente e puoi cancellare in qualsiasi momento dalla dashboard di fatturazione. Nessun contratto a lungo termine e nessuna penale di cancellazione.
HVAC Ductwork API è conforme al GDPR?
Tutte le richieste a HVAC Ductwork API passano attraverso il nostro gateway in UE. La tua chiave upstream non lascia mai il nostro server e nessun dato personale viene condiviso con il fornitore upstream oltre alla richiesta inviata.

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/ductwork-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/ductwork-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/ductwork-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/ductwork-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.

Accedi

Nuova discussione

/ 4000

📌 Fissato 🔒 Bloccato

·

· ·

/ 4000

🔒 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.

Accedi

Apri nuovo ticket

Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.

  • Nessun ticket per questa API.

Abbonamento attivo: le chiamate possono iniziare subito.

Invia la tua prima richiesta —

Abbonamento attivo: copia uno snippet e avvia la tua prima chiamata.