oanor
Sign up free
Marketplace Pricing Features Sign in

API · /shaftpower-api

Shaft Power API

healthy 4,208 Subscribers

Rotational and shaft-power maths as an API, computed locally and deterministically. The power endpoint relates mechanical power, torque and rotational speed — give any two of the power, the torque in newton-metres and the speed in rpm and it returns the third using P = T·ω with ω = 2πN/60, reporting the angular velocity and the power in watts, kilowatts, mechanical horsepower and metric horsepower (PS). The angular endpoint converts a rotational speed freely between rpm, radians per second, degrees per second and hertz (revolutions per second), and — given a radius — the tangential speed and centripetal acceleration at the rim. The units endpoint converts power across watts, kilowatts, mechanical horsepower (745.7 W), metric horsepower or PS (735.5 W), foot-pounds per second and BTU per hour. Everything is computed locally and deterministically, so it is instant and private. Ideal for automotive, motor, drivetrain, robotics and machinery app developers, engine and gearbox tools, and mechanical-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is mechanical shaft power; for bolt tightening torque use a torque API and for electrical power factor a power-factor API.

#shaft-power #torque #rpm #horsepower #mechanical #developer-tools
api.oanor.com/shaftpower-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

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

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
86 ms
Server probes · 24h
Subscribers
4,208
active
Total calls
32
last 7 days
status Full status page → · 24 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 2,000 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • Power-torque-RPM solver (solve any one from the other two)
  • Watts, kW and horsepower outputs
  • Deterministic local compute, no upstream latency
Sign in to subscribe

Starter

€8.00 /month

  • 15,000 calls / month
  • 5 requests / second
  • Hard cap (429 above quota, no overage)
  • Full torque/speed/power triangle conversions
  • Metric and imperial unit handling (N·m, lb·ft, RPM, rad/s)
  • Angular-velocity and shaft-speed conversions
  • Email support
Sign in to subscribe

Pro

€22.00 /month

  • 120,000 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • High-throughput batch shaft-power computations
  • Drivetrain efficiency and output-power chaining
  • 99.9% uptime SLA
  • Priority support
Sign in to subscribe

Mega

€69.00 /month

  • 600,000 calls / month
  • 60 requests / second
  • Hard cap (429 above quota, no overage)
  • Unlimited-tier rotational and shaft-power maths at scale
  • Highest RPS for simulation and bulk pipelines
  • Dedicated support channel
  • Custom unit and rounding profiles
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

Bolt Torque API

Bolt and fastener torque maths as an API, using the standard short-form relation T = K · D · F — torque equals the nut factor times the bolt diameter times the clamp load (preload). The torque endpoint computes the tightening torque, in newton-metres, foot-pounds, inch-pounds and kilogram-force metres, from the bolt diameter, the target clamp load and a nut factor — given directly or chosen from a condition preset (dry, lubricated, zinc-plated, galvanized, waxed and more). The preload endpoint solves the inverse: the clamp load a given torque produces on a bolt of a given diameter and friction. The convert endpoint converts a torque value between newton-metres, foot-pounds, inch-pounds and kilogram-force metres. Everything is computed locally and deterministically, so it is instant and private. The K·D·F short form is an estimate that depends heavily on friction — it is engineering guidance only, so always follow the manufacturer's torque specification. Ideal for mechanical, automotive and aerospace tools, maker and assembly apps, maintenance and field-service software, and engineering calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is fastener torque; for wire gauge and resistance use a wire-gauge API and for Ohm's law use an electronics API.

api.oanor.com/torque-api

Roller Chain Drive API

Roller-chain power-transmission maths as an API, computed locally and deterministically. The ratio endpoint computes a chain drive's speed ratio (driven ÷ driver teeth), the output rpm and torque multiplier, the chain (line) velocity v = N·p·rpm/60 and the pitch diameter of each sprocket, PD = p/sin(π/N), from the driver and driven tooth counts, the input speed and the chain pitch. The length endpoint computes the chain length in pitches and then rounds it up to an even number of links — links must come in pairs — using L = 2C/p + (N1+N2)/2 + ((N2−N1)/2π)²·p/C from the tooth counts, the centre distance and the pitch. The center-distance endpoint inverts that relation to give the exact centre distance for a chosen even link count, C = (p/8)·[(2L−N1−N2) + √((2L−N1−N2)² − 8·((N2−N1)/2π)²)]. Tooth counts are integers, pitch and centre distance in metres (the default pitch 0.0127 m is ANSI 40, ½ inch) and speeds in rpm. Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical, machine-design, conveyor, motorcycle and industrial-equipment app developers, sprocket-sizing and chain-selection tools, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is industrial roller-chain drives; for bicycle gearing use a bike-gear API and for belt or gear ratios a gear-ratio API.

api.oanor.com/chain-api

Pressure Vessel API

Thin-walled pressure-vessel engineering maths as an API, computed locally and deterministically. The thin-wall endpoint computes the wall stresses in a cylindrical or spherical vessel under internal pressure: for a cylinder the hoop (circumferential) stress σ_h = p·r/t and the longitudinal stress σ_l = p·r/(2t), which is half the hoop — so cylinders tend to split along their length — together with the von Mises equivalent stress, and for a sphere the single biaxial stress σ = p·r/(2t); it also reports the radius-to-thickness ratio and whether the thin-wall assumption (r/t ≳ 10) holds. The thickness endpoint computes the wall thickness required to keep the hoop stress within an allowable value, t = p·r/(σ_allow·E), with a weld-joint efficiency factor. The burst endpoint computes the theoretical burst pressure of a pipe from Barlow's formula, p = 2·S·t/OD, using the ultimate tensile strength. Pressures and stresses are in pascals (megapascals also returned) and dimensions in metres. Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical, chemical-plant, piping, boiler and tank-design app developers, ASME-style sizing and safety tools, and engineering education; for code work consult the applicable standards. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is thin-walled vessel stress; for general stress transformation use a Mohr-circle API and for fatigue a fatigue API.

api.oanor.com/pressurevessel-api

Material Fatigue API

Mechanical-fatigue engineering maths as an API, computed locally and deterministically. The stress-cycle endpoint decomposes a cyclic load given by its maximum and minimum stress into the alternating stress σa = (σmax − σmin)/2, the mean stress σm = (σmax + σmin)/2, the stress range and the stress ratio R = σmin/σmax, and names the loading (fully reversed at R = −1, repeated at R = 0). The criteria endpoint computes the infinite-life safety factor against fatigue using the three classic mean-stress theories — Goodman (1/n = σa/Se + σm/Sut, standard and safe), Soderberg (uses the yield strength, conservative) and Gerber (a parabola, least conservative) — from the alternating and mean stress, the endurance limit Se, the ultimate strength Sut and an optional yield strength. The endurance-limit endpoint estimates the corrected endurance limit Se = ka·kb·kc·kd·ke·Se' from the ultimate strength, with Se' = 0.5·Sut for steel and the Marin modifying factors for surface finish, size, load type, temperature and reliability. Stresses and strengths use any one consistent unit (MPa is typical). Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical, structural, automotive and aerospace-design app developers, durability and safety-factor tools, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is fatigue and endurance; for static stress transformation use a Mohr-circle API and for column buckling a buckling API.

api.oanor.com/fatigue-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Shaft Power API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Shaft Power API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Shaft Power 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 Shaft Power API cost?
Shaft Power API has a free tier with 100 calls / month. Paid plans start at €8.00 / 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 Shaft Power API GDPR-compliant?
All requests to Shaft Power 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/shaftpower-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/shaftpower-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/shaftpower-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/shaftpower-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 in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 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 in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.