oanor
Iscriviti gratis
Mercata Prezzi Caratteristiche Accedi

API · /hvac-api

API de calculadora de BTU para HVAC

salutare 4,645 Abbonati

Matemáticas de dimensionamiento de HVAC como API, calculadas local y determinísticamente a partir de factores estándar de regla general. El endpoint de refrigeración estima la carga del aire acondicionado para una habitación — en BTU por hora, toneladas de refrigeración y kilovatios — a partir del área del piso (en pies cuadrados o metros, o largo × ancho) usando una línea base de aproximadamente 20 BTU/h por pie cuadrado, con ajustes por el número de ocupantes, una cocina, exposición solar y altura del techo. El endpoint de calefacción estima la carga de calefacción a partir del área y una zona climática (templada a muy fría) o un BTU personalizado por pie cuadrado. El endpoint de conversión convierte entre BTU por hora, toneladas de refrigeración, kilovatios y vatios (una tonelada = 12,000 BTU/h ≈ 3.517 kW). Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Estas son estimaciones de regla general al estilo EnergyStar — se recomienda un cálculo de carga Manual J adecuado que tenga en cuenta el aislamiento, las ventanas y el clima local para una instalación real. Ideal para herramientas de HVAC y mejoras del hogar, guías de dimensionamiento de aires acondicionados y calefactores, aplicaciones de hogar inteligente y energía, y cotizaciones para contratistas. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 3 endpoints. Esto es dimensionamiento de HVAC; para el costo de funcionamiento de electrodomésticos, use una API de costo de energía.

#hvac #btu #air-conditioning #heating #cooling #developer-tools
api.oanor.com/hvac-api
Ottieni una chiave API Prova nel parco giochi → Contatta provider

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

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

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

API de calculadora de BTU para HVAC — live data on the oanor API marketplace

API salute

salutare
Tempo di attività
100.00%
Sondaggi del server · 24 ore su 24
Latenza media
82 ms
Sondaggi del server · 24 ore su 24
Abbonati
4,645
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

  • 11,235 chiamate/mese
  • 2 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 11,235 calls/month
  • 2 req/sec
  • Cooling + heating + convert
  • No credit card
Accedi per abbonarti

Starter

€12.75 /mese

  • 20,850 chiamate/mese
  • 8 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 20.85k calls/month
  • 8 req/sec
  • Occupant / sun / ceiling factors
  • Email support
Accedi per abbonarti

Pro

€32.65 /mese

  • 258,500 chiamate/mese
  • 20 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 258.5k calls/month
  • 20 req/sec
  • HVAC / quoting pipelines
  • Priority support
Accedi per abbonarti

Mega

€70.65 /mese

  • 1,335,000 chiamate/mese
  • 50 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 1.335M calls/month
  • 50 req/sec
  • Platform scale
  • Dedicated 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 API de calculadora de BTU para HVAC?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama API de calculadora de BTU para HVAC con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di API de calculadora de BTU para HVAC?
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 API de calculadora de BTU para HVAC?
API de calculadora de BTU para HVAC ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €12.75 / 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.
API de calculadora de BTU para HVAC è conforme al GDPR?
Tutte le richieste a API de calculadora de BTU para HVAC 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/hvac-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/hvac-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/hvac-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/hvac-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.