Scientific & engineering notation
API · /sigfig-api
Scientific Notation API
healthy
4,896 Subscribers
Scientific number representation as an API. The scientific endpoint expresses a number in both scientific notation (one digit before the decimal point × a power of ten) and engineering notation (the exponent a multiple of three, lining up with SI prefixes), and reports the mantissa and exponent. The sigfigs endpoint rounds a number to a chosen number of significant figures, and counts the significant figures in a value — respecting the rules for leading zeros, trailing zeros and the decimal point, and flagging the ambiguous cases such as "1200". The si-prefix endpoint formats a number with the right metric prefix (1500 → 1.5 k, 2.3×10⁹ → 2.3 G, 0.0023 → 2.3 m) with an optional unit, and parses a prefixed value back to a plain number (2.2 MΩ → 2,200,000). Everything is computed locally and deterministically, so it is instant and private. Ideal for science and engineering tools, lab and measurement software, electronics and signal work, and education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is scientific number representation; for locale number formatting use a number-format API and for number-to-words or Roman numerals use a number API.
api.oanor.com/sigfig-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 73 ms
- Server probes · 24h
- Subscribers
- 4,896
- active
- Total calls
- 80
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 8,635 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 8,635 calls/month
- 2 req/sec
- Scientific + sigfigs + SI prefix
- No credit card
Starter
€10.15 /month
- 18,150 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 18.15k calls/month
- 8 req/sec
- Engineering notation
- Email support
Pro
€30.05 /month
- 232,500 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 232.5k calls/month
- 20 req/sec
- Science / engineering pipelines
- Priority support
Mega
€68.05 /month
- 1,205,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 1.205M calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Railway Tractive Effort API
Railway train-performance maths as an API, computed locally and deterministically — the tractive-effort, resistance and adhesion numbers a railway engineer, train planner or rail-sim developer rates motive power with. The tractive-effort endpoint gives the pulling force a locomotive develops = 375 × horsepower × efficiency ÷ speed (mph), the classic hyperbolic curve where a constant-power loco pulls hardest at low speed and tapers as it accelerates — 4,000 hp at 25 mph and 82 % efficiency is about 49,200 lbf at the rail. The resistance endpoint gives the forces a train fights: grade resistance ≈ 20 lb per ton per 1 % of grade (the weight component along the slope, the dominant force on a hill — a 5,000-ton train on a 1 % grade fights 100,000 lbf) plus curve resistance ≈ 0.8 lb per ton per degree of curve from flange friction. The adhesion endpoint gives the hard ceiling: however much power a loco has, it can only pull as hard as the wheels grip — maximum starting tractive effort = the adhesion coefficient (≈ 0.25 dry, more with sand) × the weight on the driving wheels, so 200 tons on the drivers is about 100,000 lbf before slip. Everything is computed locally and deterministically, so it is instant and private. Ideal for rail-operations and motive-power planning tools, train-simulator and railfan apps, and transport-engineering utilities. Pure local computation — no key, no third-party service, instant. Excludes the speed-dependent Davis rolling/air resistance. 3 compute endpoints. For highway curve geometry use a horizontal-curve API.
api.oanor.com/railway-api
Worm Gear API
Worm-gear engineering maths as an API, computed locally and deterministically — the ratio, lead-angle and efficiency numbers a machine designer or millwright sizes a worm drive with. The ratio endpoint gives the reduction = wheel teeth ÷ worm starts, so a single-start worm on a 40-tooth wheel is a big 40:1 reduction in one compact stage — the high ratio in a small package is the whole appeal of a worm drive. The geometry endpoint gives the lead (= starts × axial pitch, with axial pitch = π × module) and the lead angle = atan(lead ÷ (π × worm pitch diameter)), and tests for self-locking: a small lead angle (roughly under 5–6° for typical steel-on-bronze) means the wheel cannot back-drive the worm — invaluable for hoists and holding loads, at the cost of efficiency. The efficiency endpoint gives the mesh efficiency when the worm drives = tan(lead angle) ÷ tan(lead angle + friction angle), which is low for the small lead angles that give big ratios — often 50–70 %, which is why worm gears run warm and need good lubrication — while high-lead multi-start worms reach 90 %+; when the lead angle drops to the friction angle the drive becomes self-locking. Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical-design and gearbox tools, machine-building and CAD utilities, and engineering calculators. Pure local computation — no key, no third-party service, instant. Confirm self-locking dynamically — vibration can unlock a marginal pair. 3 compute endpoints. For spur gears use a spur-gear API; for a general ratio a gear-ratio API.
api.oanor.com/wormgear-api
Hydraulic Cylinder API
Hydraulic-cylinder engineering maths as an API, computed locally and deterministically — the force, speed and oil-volume numbers a fluid-power designer, machine builder or hydraulics technician sizes a cylinder with. The force endpoint gives the push and pull from the bore, rod diameter and working pressure: extending, the oil acts on the full bore area, so the cylinder is strongest pushing out; retracting, it acts only on the annulus left by the rod, giving less force — a 100 mm bore with a 56 mm rod at 160 bar pushes about 125.7 kN out but pulls only 86.3 kN back, which is why a press or an excavator does its hard work on the extend stroke. The speed endpoint gives the piston speed from the pump flow (speed = flow ÷ area), so extending is the slower stroke and retracting the faster, the trade-off every circuit designer balances against force. The volume endpoint gives the swept oil volume per stroke for extend and retract, the rod displacement and the bore-to-annulus area ratio — the differential (regeneration) ratio used to speed the extend stroke in a regen circuit — so the pump, tank and lines can be sized for the larger volume. Everything is computed locally and deterministically, so it is instant and private. Ideal for fluid-power and machine-design tools, hydraulics-sizing calculators, mobile- and industrial-equipment utilities, and engineering apps. Pure local computation — no key, no third-party service, instant. Ideal-area estimates — allow for friction, back-pressure and efficiency. 3 compute endpoints. For Pascal force-multiplication use a hydraulics API; for valve sizing a valve-flow (Cv/Kv) API.
api.oanor.com/hydrauliccylinder-api
Press Fit API
Interference (press and shrink) fit engineering maths as an API, computed locally and deterministically from the Lamé thick-wall equations — the contact-pressure, holding-capacity and assembly-temperature numbers a mechanical designer or machinist sizes a shaft-and-hub joint with. The pressure endpoint gives the contact pressure that builds at the interface from the diametral interference, the shaft and hub diameters and the elastic modulus, plus the tensile hoop stress at the hub bore — the highest stress in the joint, which a thin hub can split if it exceeds the yield: a 50 mm solid steel shaft in a 100 mm hub with 0.05 mm interference makes about 75 MPa of contact pressure and 125 MPa of bore hoop stress, and doubling the interference doubles the pressure. The holding endpoint turns that pressure into the axial push-out force and the transmissible torque through the friction at the interface (force = pressure × contact area × friction, torque = force × shaft radius), the figures that decide whether the joint slips under load. The assembly-temperature endpoint gives the heating (hub) or cooling (shaft) temperature change for a shrink fit — ΔT = (interference + clearance) ÷ (α × diameter) — so the part slides on freely and grips as it returns to temperature. Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical-design and machine-building tools, manufacturing and CAD utilities, and engineering calculators. Pure local computation — no key, no third-party service, instant. Same-material Lamé estimates — verify against the material yield with a safety factor. 3 compute endpoints. For thin-wall pressure-vessel stress use a pressure-vessel API.
api.oanor.com/pressfit-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Scientific Notation API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Scientific Notation API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Scientific Notation 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 Scientific Notation API cost?
Scientific Notation API has a free tier with 100 calls / month. Paid plans start at €10.15 / 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 Scientific Notation API GDPR-compliant?
All requests to Scientific Notation 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/sigfig-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/sigfig-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/sigfig-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/sigfig-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.