Carnot maximum efficiency
API · /carnot-api
Carnot Heat Engine API
salutare
3,359 Abbonati
Heat-engine efficiency and coefficient of performance as an API, computed locally and deterministically. The efficiency endpoint gives the Carnot maximum efficiency of any heat engine working between two temperatures, η = 1 − Tc/Th (in kelvin) — the absolute upper limit no real engine can beat — and, given a heat input, the maximum work it could produce and the heat it must reject. The heat-pump endpoint gives the Carnot coefficient of performance of a heat pump, COP = Th/(Th − Tc), and of a refrigerator or air conditioner, COP = Tc/(Th − Tc), and the heat moved for a given work input. The engine endpoint analyses a real engine from its heat balance: from any two of the heat input, the work output, the efficiency or the heat rejected it returns the rest using η = W/Qh and Qc = Qh − W, and — given the reservoir temperatures — compares it to the Carnot limit and reports the second-law (exergy) efficiency. Temperatures accept kelvin, Celsius or Fahrenheit. Everything is computed locally and deterministically, so it is instant and private. Ideal for thermodynamics-education tools, engine, turbine and HVAC design, refrigeration and heat-pump apps, and energy-systems software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is heat-engine and refrigeration-cycle efficiency; for sensible heat use a specific-heat API and for heat-exchanger LMTD use a heat-exchanger API.
api.oanor.com/carnot-api
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 90 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 3,359
- attiva
- Chiamate totali
- 36
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 3,000 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 19,035 calls/month
- 2 req/sec
- Efficiency + heat-pump + engine
- No credit card
Starter
€5.00 /mese
- 40,000 chiamate/mese
- 5 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 30.35k calls/month
- 8 req/sec
- COP, second-law efficiency, K/°C/°F
- Email support
Pro
€15.00 /mese
- 250,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 337.5k calls/month
- 20 req/sec
- Engine / HVAC design pipelines
- Priority support
Mega
€49.00 /mese
- 1,510,000 chiamate/mese
- 40 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1.73M llamadas/mes
- 50 req/seg
- Escala de plataforma
- SLA dedicado
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Vapor Pressure API
Vapor-pressure thermodynamics as an API, computed locally and deterministically. The clausius-clapeyron endpoint predicts the vapor pressure of a substance at a new temperature from a known reference point and the molar enthalpy of vaporization, using ln(P2/P1) = -ΔHvap/R·(1/T2 - 1/T1) with temperatures in kelvin — so from water boiling at 101.325 kPa at 373.15 K and ΔHvap ≈ 40.66 kJ/mol it returns about 42.6 kPa at 350 K. The enthalpy endpoint inverts the same relation: given two pressure/temperature points it solves for the molar enthalpy of vaporization, ΔHvap = -R·ln(P2/P1)/(1/T2 - 1/T1), in J/mol and kJ/mol. The antoine endpoint evaluates the Antoine equation log10(P) = A - B/(C + T) both ways — supply a temperature to get the vapor pressure, or a pressure to get the boiling temperature — defaulting to the water constants (°C and mmHg, so water reads 760 mmHg at 100 °C) but accepting any A, B, C for other substances. The gas constant R = 8.314462618 J/(mol·K). Everything is computed locally and deterministically, so it is instant and private. Ideal for chemical-engineering, process-simulation, distillation, HVAC, meteorology and chemistry-education app developers, boiling-point and phase-equilibrium tools, and lab software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is vapor pressure and boiling point; for humidity and dew point use a psychrometric API and for ideal-gas state use a gas-law API.
api.oanor.com/vaporpressure-api
Newton Cooling & Convection API
Newton's law of cooling and convective heat transfer as an API, computed locally and deterministically. The convection endpoint applies the convective-heat-transfer rate Q = h·A·ΔT — the heat carried away from a surface equals the convection coefficient times the area times the temperature difference between the surface and the fluid — and solves for whichever of the heat rate, the coefficient, the area or the temperature difference you leave out, with typical coefficients for natural and forced air, water, boiling and condensing built in. The cooling endpoint applies Newton's law of cooling, T(t) = T_env + (T0 − T_env)·e^(−k·t): from an initial temperature, the ambient temperature and a cooling constant (or time constant τ = 1/k) it gives the temperature after a time, or the time to reach a target temperature, or it solves the cooling constant from a measured temperature at a known time — the maths behind how a hot drink, a forensic body or a cooling casting approaches room temperature. The coefficient endpoint links the cooling constant to the physical properties, k = h·A/(m·c), and the thermal time constant. Everything is computed locally and deterministically, so it is instant and private. Ideal for thermal-engineering and HVAC tools, food-safety and forensic cooling apps, electronics-cooling and process-control software, and physics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is convection and transient cooling; for steady conduction through walls use a U-value API and for thermal radiation use a Stefan-Boltzmann API.
api.oanor.com/cooling-api
API de LMTD para Intercambiadores de Calor
Matemáticas de LMTD y efectividad-NTU para intercambiadores de calor como una API, calculadas local y determinísticamente. El endpoint lmtd calcula la diferencia de temperatura media logarítmica, LMTD = (ΔT1 − ΔT2)/ln(ΔT1/ΔT2), la temperatura de conducción promedio real de un intercambiador de calor, a partir de las temperaturas de entrada y salida de los flujos caliente y frío para una disposición de flujo en contracorriente o en paralelo, y señala un cruce de temperatura. El endpoint duty aplica Q = U·A·LMTD·F — el deber térmico es igual al coeficiente global de transferencia de calor por el área por el LMTD por un factor de corrección opcional — y resuelve para cualquiera de los parámetros (deber, coeficiente, área o LMTD) que se omita, tomando el LMTD directamente o a partir de las cuatro temperaturas. El endpoint effectiveness utiliza el método de efectividad-NTU: a partir de las tasas de capacidad calorífica del flujo caliente y frío (dadas directamente o como flujo másico por calor específico) y el número de unidades de transferencia NTU = U·A/Cmin, devuelve la relación de capacidades, la efectividad para la disposición y — dadas las temperaturas de entrada — el deber térmico máximo y real y las temperaturas de salida. Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Ideal para herramientas de ingeniería de procesos, química y mecánica, HVAC, refrigeración y diseño térmico, y educación en ingeniería. Cálculo puramente local — sin clave, sin servicio de terceros, instantáneo. En vivo, no se almacena nada. 3 endpoints. Este es un análisis de intercambiador de calor de dos flujos; para el calor sensible de un solo flujo Q = m·c·ΔT, use una API de calor específico.
api.oanor.com/lmtd-api
API de Calor Latente y Entalpía
Calor latente y entalpía de cambio de fase como una API, calculados local y determinísticamente. El endpoint de calor latente aplica Q = m·L — el calor para fundir, congelar, hervir o condensar una sustancia es igual a su masa multiplicada por el calor latente — y resuelve para cualquiera de los valores (calor, masa o calor latente) que omitas, tomando el calor latente de fusión o vaporización directamente o de una tabla de sustancias incorporada (agua, etanol, mercurio, plomo, aluminio, hierro, nitrógeno, oxígeno). El endpoint de cambio de fase calcula la entalpía total de calentar o enfriar una sustancia de una temperatura a otra, combinando automáticamente el calor sensible m·c·ΔT dentro de cada fase con el calor latente en cada transición de fusión y ebullición que cruce, y devuelve un desglose paso a paso — por lo que puede decirte, por ejemplo, la energía total para convertir hielo a −10 °C hasta vapor a 110 °C, usando el calor específico correcto para el sólido, el líquido y el gas. El endpoint de sustancias enumera los calores latentes y los calores específicos por fase. El calor se reporta en julios, kilojulios, vatios-hora y kilocalorías. Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Ideal para herramientas de termodinámica y HVAC, refrigeración, calefacción y aplicaciones de ingeniería de procesos, ciencia de alimentos y materiales, y educación en física. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 3 endpoints. Esto es calor latente y cambio de fase; para calor sensible solo (Q = m·c·ΔT sin cambio de fase) usa una API de calor específico.
api.oanor.com/enthalpy-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Carnot Heat Engine API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Carnot Heat Engine API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Carnot Heat Engine 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 Carnot Heat Engine API?
Carnot Heat Engine API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €5.00 / 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.
Carnot Heat Engine API è conforme al GDPR?
Tutte le richieste a Carnot Heat Engine 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/carnot-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/carnot-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/carnot-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/carnot-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
📌 Fissato
🔒 Bloccato
·
·
·
-
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.