Belt length from diameters & centres
API · /beltdrive-api
Belt Drive API
Belt-drive and pulley maths as an API, computed locally and deterministically. The belt endpoint computes the length of an open V-belt or flat belt from the two pulley diameters and the centre distance with L = 2C + (π/2)(D1+D2) + (D1−D2)²/(4C), and returns the belt length plus the wrap (contact) angle on each pulley; pass a driver rpm and it also gives the belt surface speed. The ratio endpoint computes the speed ratio of a pulley pair (driven ÷ driver diameter, since N1·D1 = N2·D2): give a driver or driven rpm and it returns the other, the torque ratio and the belt speed. The centers endpoint reverses the length equation to find the centre distance for a target belt length, solving the equation numerically. Diameters and distances accept millimetres, centimetres, metres, inches or feet, and lengths are reported in several units. Everything is computed locally and deterministically, so it is instant and private. Ideal for machine and drivetrain design tools, maintenance and MRO apps, maker and CNC projects, and mechanical-engineering calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is belt-and-pulley power transmission; for bicycle gear ratios and development use a bike-gear API and for bolt tightening torque use a torque API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 92 ms
- Server probes · 24h
- Subscribers
- 4,956
- active
- Total calls
- 40
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 13,935 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 13,935 calls/month
- 2 req/sec
- Belt length + ratio + centres
- No credit card
Starter
€15.55 /month
- 23,650 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 23.65k calls/month
- 8 req/sec
- Wrap angles, belt speed
- Email support
Pro
€35.85 /month
- 286,500 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 286.5k calls/month
- 20 req/sec
- Machine / drivetrain pipelines
- Priority support
Mega
€73.85 /month
- 1,475,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 1.475M calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Pulley System API
Pulley and block-and-tackle mechanics as an API, computed locally and deterministically. The advantage endpoint computes the mechanical advantage of a pulley system — the ideal MA equals the number of rope parts supporting the load, which is also the velocity ratio — and returns the effort needed to hold or raise a load, effort = load/(n·efficiency), the length of rope that must be pulled (n times the lift height) and the work in and out. The friction endpoint models a real block and tackle where every sheave loses a little tension: the mechanical advantage becomes MA = e·(1−eⁿ)/(1−e) for a per-sheave efficiency e (≈0.96 for a plain bearing, ≈0.98 for a ball bearing), so it returns the true MA, the overall efficiency and the extra effort friction costs you. The solve endpoint takes any two of the load, the effort and the number of rope parts and returns the third — for example, how many parts you need so a given person can raise a given load, or the heaviest load a winch can lift. Everything is computed locally and deterministically, so it is instant and private. Ideal for rigging, lifting and hoist-design tools, sailing, climbing and theatre-rigging apps, crane and winch sizing, and physics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is pulley and block-and-tackle mechanics; for lever and moment balance use a lever API and for rope-around-a-drum capstan friction use a capstan API.
api.oanor.com/pulley-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 Belt Drive API?
What's the rate limit for Belt Drive API?
How much does Belt Drive API cost?
Can I cancel my subscription anytime?
Is Belt Drive API GDPR-compliant?
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/beltdrive-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/beltdrive-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/beltdrive-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/beltdrive-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
·
-
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.