Critical temperatures from carbon
API · /heattreat-api
Steel Heat-Treat API
salutare
4,806 Abbonati
Stahl-Wärmebehandlungsmathematik als API, lokal und deterministisch berechnet – die Temperaturen und Härtezahlen, mit denen ein Klingenschmied, Maschinist oder Metallurg arbeitet. Der Critical-Temp-Endpunkt gibt die kritischen und Prozess-Temperaturen aus dem Kohlenstoffgehalt: die untere kritische A1 beträgt 727 °C und die obere kritische A3 ≈ 910 − 203·√(%C), also hat ein 0,4 %-Kohlenstoffstahl eine A3 um 782 °C und härtet bei etwa 817 °C (Austenitisieren 30–50 °C über A3, dann abschrecken), während ein übereutektoider Stahl knapp über A1 austenitisiert. Der Tempering-Endpunkt bildet Anlassoxidfarben auf Temperatur in beide Richtungen ab – helles Stroh bei etwa 204 °C für harte Schneidkanten, Lila um 282, Blau um 304 für Federn – mit der typischen Verwendung bei jeder Farbe, die man auf blankem Stahl beobachtet, während man die Härte zurücknimmt. Der Härte-Endpunkt konvertiert zwischen Rockwell C, Brinell und Zugfestigkeit (SAE J417 / ASTM E140): HRC 50 entspricht etwa 481 Brinell und etwa 1.660 MPa Zugfestigkeit, da Zugfestigkeit ≈ 3,45 × Brinell. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Klingenschmiede- und Metallbearbeitungs-Apps, Maschinenwerkstatt- und Wärmebehandlungswerkzeuge, Materialtechnik-Rechner und Studienhilfen. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Live, nichts gespeichert. 3 Compute-Endpunkte. Schätzungen für unlegierten Kohlenstoffstahl – legierte Stähle und eine getestete Tabelle weichen ab.
api.oanor.com/heattreat-api
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 103 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,806
- attiva
- Chiamate totali
- 4
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 460 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 460 Aufrufe/Monat
- 2 req/sec
- Kritische Temperatur + Anlassen + Härte
- Keine Kreditkarte
Starter
€5.45 /mese
- 12,200 chiamate/mese
- 6 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 12.200 Aufrufe/Monat
- 6 req/sec
- A3 from carbon, HRC/HB
- E-Mail-Support
Pro
€17.60 /mese
- 79,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 79.000 Aufrufe/Monat
- 15 req/sec
- Wärmebehandlungs- und Shop-Pipelines
- Prioritäts-Support
Mega
€52.40 /mese
- 258,000 chiamate/mese
- 36 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 258.000 Aufrufe/Monat
- 36 req/sec
- Plattform-Skalierung
- Dedizierte SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Metal Weight API
Metal stock weight and cost as an API, computed locally and deterministically. The weight endpoint computes the mass of a length of metal stock from its shape, dimensions and material: round bar, square bar, flat bar or plate, sheet, hexagonal bar, round tube or pipe and rectangular (box) tube. It works out the cross-sectional area, multiplies by the length and the material density, and returns the weight per piece and the total for a quantity — in kilograms, pounds, grams and tonnes — along with the volume. Material density is looked up from a built-in table of metals (steel, stainless, aluminium, copper, brass, bronze, lead, zinc, titanium, nickel, gold, silver and more) or you can pass an explicit density. The cost endpoint multiplies that weight by a price per kilogram, pound or tonne to give the material cost per piece and in total. The materials endpoint lists the densities. Dimensions accept millimetres, centimetres, metres, inches or feet. Everything is computed locally and deterministically, so it is instant and private. Ideal for metal fabrication and machine-shop tools, engineering and CAD apps, scrap and stock quoting, and shipping-weight estimates. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is metal stock weight from geometry and density; for beam reactions and deflection use a beam API and for live metal spot prices use a commodities API.
api.oanor.com/metalweight-api
Screw Auger API
Screw-conveyor and grain-auger maths as an API, computed locally and deterministically — the capacity, speed and throughput numbers a farmer, millwright or material-handling engineer sizes an auger with. The capacity endpoint gives the volumetric throughput from the screw geometry: the annular flight volume per turn ((π/4)(diameter² − shaft²) × pitch) × rpm × 60 × the trough loading, so a 9-inch full-pitch screw on a 2.5-inch shaft at 40 rpm and 45 % loading moves about 330 cubic feet — 265 bushels — an hour. The speed endpoint inverts it, the rpm needed for a target capacity, so you don't overspeed a small auger and grind the grain. The bushels endpoint converts a volumetric rate to bushels and tons per hour (1 bushel = 1.2445 ft³, tons = bushels × test weight ÷ 2000), so 330 ft³/hr of 56-lb corn is 265 bushels or 7.4 tons an hour — the number you match to the dryer or the truck. Everything is computed locally and deterministically, so it is instant and private. Ideal for grain-handling and ag-equipment apps, material-handling and conveyor-design tools, farm-build calculators, and engineering aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — incline and material change real throughput. For belt conveyors use a conveyor API.
api.oanor.com/auger-api
Radiant Floor API
Radiant-Floor- und Hydronic-Heizungsmathematik als API, lokal und deterministisch berechnet – die Output-, Rohr- und Durchflusszahlen, mit denen ein Installateur oder Heimwerker einen warmen Fußboden plant. Der Output-Endpunkt gibt die Wärme aus, die ein warmer Fußboden abgibt: etwa 2 BTU/h pro Quadratfuß für jedes °F, das die Bodenoberfläche wärmer als der Raum ist, also liefert ein 85 °F-Boden in einem 70 °F-Raum etwa 30 BTU/h/ft² – etwa 9.000 BTU/h über 300 ft², die Komfortgrenze, da der Boden bei ~85 °F gehalten wird. Der Rohr-Endpunkt gibt das Rohr und die Schleifen für eine Fläche bei einem Abstand an: Feldrohr = Fläche × 12 ÷ Abstand, also benötigt 300 ft² bei 9-Zoll-Abstand 400 Fuß Rohr, aufgeteilt in Schleifen unter ~300 Fuß (zwei 200-Fuß-Schleifen), damit die Pumpe sie durchdrücken kann. Der Durchfluss-Endpunkt gibt die Schleifendurchflussrate für eine Heizlast an, GPM = Last ÷ (500 × ΔT), wobei 500 die Wasserkonstante und ΔT die Vorlauf-Rücklauf-Differenz ist – 9.000 BTU/h bei einer ΔT von 20 °F benötigt 0,9 GPM. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Fußbodenheizungs- und Sanitäranwendungen, Hydronic-Design- und PEX-Layout-Tools, HVAC-Rechner für Auftragnehmer und DIY-Bau-Seiten. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Live, nichts gespeichert. 3 Compute-Endpunkte. Schätzungen – mit einer vollständigen Wärmeverlustberechnung überprüfen. Für die Gebäudelast eine HVAC-API verwenden; für die Rohrgeschwindigkeit eine Durchflussraten-API.
api.oanor.com/radiant-api
Ladder Safety API
Ladder-safety maths as an API, computed locally and deterministically — the angle, reach and load numbers that keep a ladder from sliding out or buckling. The angle endpoint applies the 4:1 rule: the base goes out one foot for every four feet of working length, which lands the ladder at about 75.5° — a 24-foot ladder sits 6 feet from the wall and reaches roughly 23 feet up, steep enough not to tip back and shallow enough not to slide. The extension endpoint gives the usable length and reach of a two-section extension ladder, which loses the overlap the sections share (3 feet up to 36, 4 to 48, 5 beyond), and the working height at the safe angle — remembering the ladder must extend 3 feet above a roof edge you step onto. The duty-rating endpoint turns a total load — your weight plus tools and materials, not just bodyweight — into the right duty class, from Type III household (200 lb) through I industrial (250) to IAA professional (375). Everything is computed locally and deterministically, so it is instant and private. Ideal for construction-safety and trades apps, jobsite and rental tools, OSHA training aids, and home-improvement sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Educational — always follow the manufacturer's labels and OSHA/ANSI rules.
api.oanor.com/ladder-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Steel Heat-Treat API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Steel Heat-Treat API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Steel Heat-Treat 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 Steel Heat-Treat API?
Steel Heat-Treat API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €5.45 / 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.
Steel Heat-Treat API è conforme al GDPR?
Tutte le richieste a Steel Heat-Treat 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/heattreat-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/heattreat-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/heattreat-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/heattreat-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.