Critical temperatures from carbon
API · /heattreat-api
Steel Heat-Treat API
healthy
4,806 Subscribers
Steel heat-treatment maths as an API, computed locally and deterministically — the temperatures and hardness numbers a bladesmith, machinist or metallurgist works to. The critical-temp endpoint gives the critical and process temperatures from carbon content: the lower critical A1 is 727 °C and the upper critical A3 ≈ 910 − 203·√(%C), so a 0.4 %-carbon steel has an A3 around 782 °C and hardens about 817 °C (austenitize 30–50 °C above A3, then quench), while a hypereutectoid steel austenitizes just above A1. The tempering endpoint maps temper oxide colours to temperature both ways — light straw at about 204 °C for hard cutting edges, purple around 282, blue around 304 for springs — with the typical use at each, the colour you watch on bright steel as you draw the hardness back. The hardness endpoint converts between Rockwell C, Brinell and tensile strength (SAE J417 / ASTM E140): HRC 50 is roughly 481 Brinell and about 1,660 MPa tensile, since tensile ≈ 3.45 × Brinell. Everything is computed locally and deterministically, so it is instant and private. Ideal for bladesmithing and metalworking apps, machine-shop and heat-treat tools, materials-engineering calculators, and trade study aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Plain-carbon-steel estimates — alloy steels and a tested chart differ.
api.oanor.com/heattreat-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 103 ms
- Server probes · 24h
- Subscribers
- 4,806
- active
- Total calls
- 4
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 460 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 460 calls/month
- 2 req/sec
- Critical temp + tempering + hardness
- No credit card
Starter
€5.45 /month
- 12,200 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 12,200 calls/month
- 6 req/sec
- A3 from carbon, HRC/HB
- Email support
Pro
€17.60 /month
- 79,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 79,000 calls/month
- 15 req/sec
- Heat-treat & shop pipelines
- Priority support
Mega
€52.40 /month
- 258,000 calls / month
- 36 requests / second
- Hard cap (429 above quota, no overage)
- 258,000 calls/month
- 36 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
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
Tire Calculator API
Tire maths as an API, computed locally and deterministically — the size, pressure and speedometer numbers a driver, fitter or fleet manager works out before fitting a tyre. The size endpoint turns a P-metric spec into the real dimensions: overall diameter = rim + 2 × the sidewall (section width × aspect ratio), so a 225/45R17 stands about 25 inches tall, rolls a 78-inch circumference and turns roughly 808 times a mile — the numbers behind fitment, gearing and clearance. The pressure endpoint gives the hot pressure from a cold pressure and the temperature change, because pressure tracks absolute temperature (P2/P1 = T2/T1), about +1 psi per 10 °F — so 32 psi set cold at 70 °F reads ~34.6 after warming to 100 °F, and drops on a cold morning, which is what trips the warning light. The speedo-error endpoint gives the speedometer error and true speed from a tyre-size change: a taller tyre makes the speedo read low, so actual speed = indicated × new diameter ÷ old — go up 4 % and 60 on the dial is really 62.5. Everything is computed locally and deterministically, so it is instant and private. Ideal for tyre-shop and fitment apps, fleet and 4x4 build tools, speedo-recalibration calculators, and automotive sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — always set pressure cold to the placard.
api.oanor.com/tire-api
Boat Propeller API
Boat-propeller maths as an API, computed locally and deterministically — the slip, RPM and pitch numbers that decide whether a boat hits its numbers or labours. The slip endpoint gives propeller slip from the pitch, the prop RPM and the actual boat speed: theoretical speed = pitch × prop RPM ÷ 1215, and slip = (theoretical − actual) ÷ theoretical — a 19-inch prop at 2000 RPM should make 31 knots in theory, so a real 26.6 knots is about 15 % slip, normal for a clean planing boat. The prop-rpm endpoint gives the propeller RPM from the engine RPM and the gear (reduction) ratio — a 2:1 gearbox spins the prop at half engine speed — and, with a pitch, the theoretical no-slip speed at that RPM. The pitch endpoint gives the pitch needed to reach a target speed at a prop RPM and expected slip, pitch = target × 1215 ÷ (prop RPM × (1 − slip)), so you can prop the boat to let the engine reach the top of its wide-open-throttle range instead of lugging. Everything is computed locally and deterministically, so it is instant and private. Ideal for boating and marine apps, repower and prop-shop tools, performance calculators, and seamanship study aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — hull, load and bottom condition shift real slip.
api.oanor.com/propeller-api
Boat Anchoring API
Boat-anchoring maths as an API, computed locally and deterministically — the scope, swing and load numbers a sailor or boater sets the hook by. The scope endpoint gives the rode to let out: scope = rode ÷ the vertical from the seabed to the bow roller (water depth + bow height), measured at high tide, so anchoring in 20 feet with a 4-foot bow at the classic 7:1 means paying out 168 feet of rode — let out more in a blow, and never less than 5:1 on all chain. The swing endpoint gives the circle the boat swings on: radius = the horizontal reach of the rode (√(rode² − vertical²)) plus the boat length, so that 168-foot rode on a 30-foot boat sweeps a 196-foot radius — the room you must leave every other boat, which swings too. The load endpoint gives the wind load the ground tackle has to hold, 0.00256 × drag coefficient × frontal windage area × wind speed², which quadruples every time the wind doubles — 50 square feet of windage takes 138 lb at 30 mph but 553 lb at 60. Everything is computed locally and deterministically, so it is instant and private. Ideal for sailing and boating apps, anchoring and cruising tools, ground-tackle sizing calculators, and seamanship study aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — add current, waves and a safety margin.
api.oanor.com/anchor-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Steel Heat-Treat API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Steel Heat-Treat API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Steel Heat-Treat API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Steel Heat-Treat API cost?
Steel Heat-Treat API has a free tier with 100 calls / month. Paid plans start at €5.45 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Steel Heat-Treat API GDPR-compliant?
All requests to Steel Heat-Treat API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your 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())Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
📌 Pinned
🔒 Locked
·
·
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.