oanor
Iscriviti gratis
Mercata Prezzi Caratteristiche Accedi

API · /prandtl-api

API de Números de Transferencia de Calor

salutare 3,766 Abbonati

Números adimensionales de transferencia de calor por convección como una API, calculados local y determinísticamente. El endpoint prandtl calcula el número de Prandtl Pr = μ·cp/k (o ν/α), la relación entre la difusividad de momento y térmica que determina el grosor relativo de las capas límite de velocidad y térmica — el aire es aproximadamente 0.71 y el agua alrededor de 7 a 20 °C. El endpoint grashof calcula el número de Grashof Gr = g·β·|ΔT|·L³/ν², flotabilidad versus fuerzas viscosas en convección natural (para un gas ideal el coeficiente de expansión térmica β ≈ 1/T). El endpoint rayleigh proporciona el número de Rayleigh Ra = Gr·Pr, ya sea a partir de Gr y Pr o de las entradas completas de convección natural, que gobierna el inicio de la convección (crítico ≈ 1708 para una capa horizontal calentada). El endpoint peclet calcula el número de Péclet Pe = Re·Pr = v·L/α, advección versus difusión de calor. El endpoint biot calcula el número de Biot Bi = h·L/k e indica si se aplica el modelo transitorio de capacitancia concentrada (Bi < 0.1). Todas las entradas están en SI. Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Ideal para desarrolladores de aplicaciones de ingeniería térmica, HVAC, refrigeración electrónica, CFD, ingeniería de procesos y educación en transferencia de calor, herramientas de convección natural y conducción transitoria, y software de simulación. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 5 endpoints. Estos son grupos de transferencia de calor por convección; para el número de Reynolds solo, use una API de Reynolds y para números de tensión superficial, una API de Weber.

#prandtl #heat-transfer #grashof #rayleigh #biot #developer-tools
api.oanor.com/prandtl-api
Ottieni una chiave API Prova nel parco giochi → Contatta provider

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

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

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

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
3,766
attiva
Chiamate totali
30
ultimi 7 giorni
status Pagina di stato completa → · 36 sonde/24h

Prezzi

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

Free

Gratis

  • 3,700 chiamate/mese
  • 2 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 3,700 calls/month
  • 2 req/sec
  • Prandtl + Grashof + Rayleigh + Péclet + Biot
  • No credit card
Accedi per abbonarti

Starter

€6.80 /mese

  • 35,000 chiamate/mese
  • 6 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 35,000 calls/month
  • 6 req/sec
  • Natural convection, lumped-capacitance
  • Email support
Accedi per abbonarti

Pro

€20.50 /mese

  • 172,000 chiamate/mese
  • 15 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 172,000 calls/month
  • 15 req/sec
  • CFD & electronics-cooling pipelines
  • Priority support
Accedi per abbonarti

Mega

€63.00 /mese

  • 1,040,000 chiamate/mese
  • 40 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 1,040,000 llamadas/mes
  • 40 req/seg
  • Escala de plataforma
  • SLA dedicado
Accedi per abbonarti

Costruito da

P
PremiumApi

Correlato APIs

Altro APIs con tag sovrapposti.

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

Optical Resolution API

Optical resolution by the Rayleigh criterion as an API, computed locally and deterministically. The angular endpoint gives the smallest angle two points can be apart and still be told apart through a circular aperture, θ = 1.22·λ/D — the diffraction limit set by the wavelength and the aperture diameter — in radians, degrees, arcminutes and arcseconds (a 100 mm telescope resolves about 1.4 arcseconds in green light), and solves the aperture needed for a target resolution. The distance endpoint turns that angle into a real separation at a distance, s = θ·L = 1.22·λ·L/D — how far apart two objects must be to be resolved at a given range. The microscope endpoint computes resolving power from the numerical aperture: the Rayleigh limit d = 0.61·λ/NA and the Abbe limit d = λ/(2·NA), with NA = n·sin(θ) from a refractive index and half-angle, and the maximum useful magnification. Wavelength defaults to 550 nm (visible) and can be set in metres, nanometres or micrometres. Everything is computed locally and deterministically, so it is instant and private. Ideal for astronomy, telescope and binocular tools, microscopy and imaging-system design, camera and optics apps, and physics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is the diffraction-limited resolving power; for thin-lens imaging use a lens API and for slit and grating diffraction use a diffraction API.

api.oanor.com/resolution-api

Rotational Grazing API

Rotational-grazing maths as an API, computed locally and deterministically — the animal-unit, grazing-day and acreage numbers a rancher or homesteader moves a herd by. It all hangs on the animal unit: a 1000-pound cow eating about 26 pounds of dry matter a day. The animalunits endpoint converts a mixed herd to that common basis — a cow is 1.0 AU, a cow-calf pair 1.3, a horse 1.25, a sheep 0.2, a goat 0.17 — so ten cows and fifty sheep are 20 AU demanding 520 pounds of forage a day; pass a weight instead and it scales by weight ÷ 1000. The days endpoint works out how long a paddock lasts: grazing days = (acres × forage per acre × utilization) ÷ (animal units × 26), where the classic “take half, leave half” puts utilization near 50 %, so five acres yielding 3,000 lb at 50 % feeds 10 AU for about 29 days. The acres endpoint sizes the paddock the other way — acres = (AU × 26 × days) ÷ (forage × utilization) — so 20 AU for a 30-day move needs about 10.4 acres. Everything is computed locally and deterministically, so it is instant and private. Ideal for ranching, regenerative-agriculture, homesteading and farm-management app developers, paddock-planner and stocking-rate tools, and grazing-chart software. Pure local computation — no key, no third-party service, instant. US units; forage yield varies with season — measure it. Live, nothing stored. 3 compute endpoints.

api.oanor.com/grazing-api

Egg Incubation API

Egg-incubation maths as an API, computed locally and deterministically — the hatch timeline, conditions and brooder numbers a hatchery or backyard chicken-keeper raises a clutch by. The hatch endpoint turns the set day (day 0) into the schedule by species: it knows the incubation period — chicken 21 days, duck 28, quail 17, goose 30, turkey 28, Muscovy 35 and more — and gives the lockdown day, about three days before hatch, when you stop turning the eggs, raise the humidity and leave the lid shut; pass a custom incubation_days for anything else. The conditions endpoint gives the targets: a forced-air incubator at 99.5 °F (still-air a degree or two higher at the top of the eggs), with humidity around 45–55 % through incubation and 65–75 % at lockdown so the membrane stays soft. The brooder endpoint schedules the chicks after they hatch — 95 °F under the lamp in week one, dropping 5 °F a week until they reach room temperature around 70 °F and are feathered enough to leave it. Everything is computed locally and deterministically, so it is instant and private. Ideal for poultry, hatchery, homesteading and farm app developers, incubation-timer and brooder tools, and 4-H / education software. Pure local computation — no key, no third-party service, instant. Guidance — candle the eggs and watch the chicks. Live, nothing stored. 3 compute endpoints.

api.oanor.com/incubation-api

Domande frequenti

Risposte rapide su prezzi, quote e integrazione.

Come ottengo una chiave API per API de Números de Transferencia de Calor?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama API de Números de Transferencia de Calor con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di API de Números de Transferencia de Calor?
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 Números de Transferencia de Calor?
API de Números de Transferencia de Calor ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €6.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.
API de Números de Transferencia de Calor è conforme al GDPR?
Tutte le richieste a API de Números de Transferencia de Calor 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/prandtl-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/prandtl-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/prandtl-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/prandtl-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.