Convert cord / stere / m³
API · /firewood-api
Firewood Calculator API
salutare
4,795 Abbonati
Firewood maths as an API, computed locally and deterministically. The volume endpoint turns a wood-stack's length, height and depth (in feet or metres) into its volume in cubic feet and cubic metres, full cords, face cords and steres — a full cord being 128 cubic feet (a 4×4×8 ft stack) and a face cord being an 8×4 ft stack by the piece (log) length. The convert endpoint converts a quantity between cords, face cords, steres, cubic metres and cubic feet, using the piece length for the face-cord relationship. The heat endpoint estimates the heating value of a number of cords by wood species — returning the millions of BTU and the equivalent gallons of heating oil, therms of natural gas and kilowatt-hours — from a built-in table of typical seasoned-wood values (oak, hickory, maple, ash, birch, pine and more) or a custom figure. Everything is computed locally and deterministically, so it is instant and private. Heat values are typical seasoned figures (around 20% moisture) and vary with species, dryness and stove efficiency. Ideal for firewood sellers and delivery tools, heating and homestead apps, and forestry and woodlot calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is firewood volume and energy; for general volume or unit conversion use a unit-conversion API.
api.oanor.com/firewood-api
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 83 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,795
- attiva
- Chiamate totali
- 40
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 11,035 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 11,035 calls/month
- 2 req/sec
- Volume + convert + heat
- No credit card
Starter
€12.55 /mese
- 20,650 chiamate/mese
- 8 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 20.65k calls/month
- 8 req/sec
- Face cords + species heat values
- Email support
Pro
€32.45 /mese
- 256,500 chiamate/mese
- 20 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 256.5k calls/month
- 20 req/sec
- Firewood / forestry pipelines
- Priority support
Mega
€70.45 /mese
- 1,325,000 chiamate/mese
- 50 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1.325M llamadas/mes
- 50 req/seg
- Escala de plataforma
- SLA dedicado
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Degree Day API
Heating and cooling degree-day maths as an API, computed locally and deterministically. The daily endpoint computes the heating degree days, HDD = max(0, base − mean), and the cooling degree days, CDD = max(0, mean − base), for a single day from a base temperature and the daily mean — or the minimum and maximum, since the mean is taken as their average. The period endpoint sums the degree days over a list of daily temperatures (means or min/max pairs), returning the total HDD and CDD, the count of heating and cooling days and the average temperature — the standard way to characterise a heating or cooling season. The energy endpoint turns degree days into an energy estimate: the heat delivered is UA·DD·24/1000 kWh from the building heat-loss coefficient, the fuel or electricity input is that divided by the boiler efficiency (or a heat-pump COP), and — with an energy price — the cost. Everything is computed locally and deterministically, so it is instant and private. Ideal for building-energy, HVAC and facilities tools, heating-bill and fuel-budget estimation, weather-normalisation and energy-benchmarking apps, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is degree-day demand estimation; for U-value and heat-loss fabric calculations use a U-value API.
api.oanor.com/degreeday-api
API de calculadora de BTU para HVAC
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.
api.oanor.com/hvac-api
Log Scaling & Timber API
Log-Scaling- und Holzmathematik als API, lokal und deterministisch berechnet – die Brettfuß-Ausbeute und das Kubikvolumen, die ein Holzfäller, Säger oder Förster mit einem Rundholz skaliert. Der Boardfeet-Endpunkt führt die drei klassischen Log-Regeln gleichzeitig aus, basierend auf dem kleinen Enddurchmesser unter Rinde und der Länge: Doyle = ((D − 4) ÷ 4)² × L, Scribner Decimal C ≈ (0,79·D² − 2·D − 4) × L ÷ 16 und die Internationale ¼-Zoll-Regel durch exakte Vier-Fuß-Segmente mit einem halben Zoll Toleranz für die Verjüngung, gerundet auf die nächsten 5 Brettfuß – so ergibt ein 20-Zoll-, 16-Fuß-Log 256 BF nach Doyle, 272 nach Scribner und 320 nach International, was deutlich zeigt, dass Doyle kleine Logs unterschätzt, International am genauesten ist und Scribner dazwischen liegt. Der Volume-Endpunkt gibt den Kubikinhalt nach Smalians Formel – dem Durchschnitt der beiden Endquerschnittsflächen mal Länge – und Hubers Formel – der mittleren Querschnittsfläche mal Länge, normalerweise die genaueste – sowohl in Kubikfuß als auch in Cords (128 ft³ = 1 Cord). Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Entwickler von Forst-, Holzeinschlags-, Sägewerks-, Timber-Cruising- und Landmanagement-Apps, Log-Käufer- und Holzwertermittlungstools sowie Holzplatzrechner. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Imperiale Forsteinheiten. Live, nichts wird gespeichert. 2 Compute-Endpunkte. Für gesägte Brettfuß verwenden Sie eine Lumber-API.
api.oanor.com/logscale-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
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Firewood Calculator API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Firewood Calculator API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Firewood Calculator 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 Firewood Calculator API?
Firewood Calculator API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €12.55 / 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.
Firewood Calculator API è conforme al GDPR?
Tutte le richieste a Firewood Calculator 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/firewood-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/firewood-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/firewood-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/firewood-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.