oanor
Sign up free
Marketplace Pricing Features Sign in

API · /clutch-api

Clutch & Brake Torque API

healthy 3,678 Subscribers

Friction clutch and disc-brake torque as an API, computed locally and deterministically. The clutch endpoint computes the torque a plate (disc) clutch can transmit from the friction coefficient, the axial clamping force and the friction-face inner and outer radii, by both standard theories — uniform-wear, T = n·μ·F·(Ro+Ri)/2, and uniform-pressure, T = ⅔·n·μ·F·(Ro³−Ri³)/(Ro²−Ri²) — for any number of friction surfaces (a multi-plate clutch multiplies the torque), plus the maximum power at a given speed. The cone endpoint does the same for a cone clutch, T = n·μ·F·Rm/sin α, where the wedge angle amplifies the normal force by 1/sin α. The brake endpoint gives the braking torque of a disc brake, T = n·μ·F·R_eff, the power dissipated at a speed and — given a rotating inertia and its speed — the angular deceleration, the time and number of revolutions to stop, and the kinetic energy turned into heat. Everything is computed locally and deterministically, so it is instant and private. Ideal for drivetrain, automotive and machine-design tools, clutch, brake and winch engineering, and mechanical-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is rotating-friction clutch and brake torque; for shaft torsion stress use a torsion API and for rope/belt capstan friction use a capstan API.

#clutch #brake #friction-torque #drivetrain #mechanical-engineering #developer-tools
api.oanor.com/clutch-api
Get an API key Try in playground → Contact provider

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

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

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

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
89 ms
Server probes · 24h
Subscribers
3,678
active
Total calls
36
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)
  • Plate-clutch transmissible torque endpoint
  • Disc-brake friction torque endpoint
  • Deterministic, instant local compute
  • 2 req/s, 2,000 calls/mo
Sign in to subscribe

Starter

€9.00 /month

  • 20,000 calls / month
  • 5 requests / second
  • Hard cap (429 above quota, no overage)
  • Both clutch + brake torque endpoints
  • Configurable friction coefficient & pad count
  • SI + imperial unit handling
  • 5 req/s, 20,000 calls/mo
Sign in to subscribe

Pro

€24.00 /month

  • 120,000 calls / month
  • 15 requests / second
  • Hard cap (429 above quota, no overage)
  • Multi-plate clutch & multi-pad brake support
  • Effective-radius (uniform-wear/pressure) models
  • Batch torque computation
  • 15 req/s, 120,000 calls/mo
Sign in to subscribe

Mega

€74.00 /month

  • 603,000 calls / month
  • 40 requests / second
  • Hard cap (429 above quota, no overage)
  • Highest throughput for drivetrain CAD/sim pipelines
  • Full clutch + brake parameter sweep batch
  • Priority support & 99.9% uptime SLA
  • 40 req/s, 600,000 calls/mo
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

Gear Ratio API

Gear-train ratio, speed and torque maths as an API, computed locally and deterministically. The ratio endpoint computes the gear ratio of a single pair from the driver and driven tooth counts (or pitch diameters), ratio = N_driven/N_driver, classifies it as a reduction (more torque, less speed) or an overdrive, and — given an input speed and torque — returns the output speed (input/ratio) and the output torque (input·ratio·efficiency). The train endpoint computes a compound gear train: the overall ratio is the product of the individual stage ratios, and it returns each stage ratio, the output speed and torque, noting that idler gears change only the direction of rotation, not the ratio. The solve endpoint finds the missing one of the input speed, the output speed and the ratio from the other two — for example, the ratio needed to drop a 1500 rpm motor to a 500 rpm output. Everything is computed locally and deterministically, so it is instant and private. Ideal for drivetrain, robotics and machine-design tools, gearbox and transmission selection, bicycle and vehicle gearing, and mechanical-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is gear-train ratio and torque; for spur-gear tooth geometry use a spur-gear API.

api.oanor.com/gearratio-api

Shaft Torsion API

Shaft torsion as an API, computed locally and deterministically. The stress endpoint computes the maximum torsional shear stress in a circular shaft, τ = T·r/J — torque times the outer radius divided by the polar moment of inertia — for a solid shaft (J = π·d⁴/32) or a hollow tube (J = π·(D⁴−d⁴)/32), and solves the torque a shaft can carry for an allowable stress. The twist endpoint computes the angle of twist along the shaft, θ = T·L/(G·J), in radians and degrees, from the torque, length and the shear modulus (given directly or from a built-in material table — steel, aluminium, copper, titanium and more), plus the torsional stiffness G·J/L. The power endpoint relates the power a rotating shaft transmits to its torque and speed, P = T·ω = T·2πN/60, and solves any of the three, reporting power in watts, kilowatts and horsepower. Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical and drivetrain engineering tools, shaft, axle and coupling design, motor and gearbox apps, and machine-design education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is circular-shaft torsion; for axial stress-strain use a Young's-modulus API and for the 2D stress state use a Mohr-circle API.

api.oanor.com/torsion-api

Bicycle Gear API

Bicycle gearing maths as an API, computed locally and deterministically. The gear endpoint takes a chainring and cog tooth count and a wheel size and returns every common gearing metric: the gear ratio, gear inches (the classic measure — ratio times wheel diameter in inches), the gain ratio (Sheldon Brown's crank-length-aware measure), the development or rollout (metres travelled per crank revolution), and the road speed at a chosen cadence in km/h and mph. The speed endpoint converts between a gear-and-cadence and road speed in either direction — the speed at a cadence, or the cadence needed for a target speed. The table endpoint builds a gear chart: give one or more chainrings and a cassette of cogs and it returns a matrix of gear inches, development, gain ratio or ratio for every combination — ideal for visualising a drivetrain. Wheel size can be a preset (700x25c, 26-inch, 29er and more) or an exact rolling circumference in millimetres, and crank length is configurable for the gain ratio. Everything is computed locally and deterministically, so it is instant and private. Ideal for cycling apps and bike-fit tools, drivetrain and gear-ratio planners, and bike-shop and component sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is bicycle gearing; for cycling power, FTP and training zones use a cycling API.

api.oanor.com/bikegear-api

O-Ring Seal API

O-ring seal-design maths as an API, computed locally and deterministically — the squeeze, gland and stretch numbers an engineer or maker designs a seal to. The squeeze endpoint gives the compression that makes the seal: squeeze = (cross-section − gland depth) ÷ cross-section, so a 0.139-inch cord in a 0.113-inch deep groove is squeezed 18.7 %, and it grades the result — roughly 10–16 % suits dynamic (reciprocating) seals and 15–30 % static ones — and, given the groove width, the gland fill percentage, which should stay under about 85 % so the rubber has room to expand from heat or fluid swell. The gland endpoint works the other way: from the cross-section and whether the seal is static or dynamic (or a target squeeze) it returns the groove depth and a width sized for about 70 % fill — typically 1.3 to 1.5 times the cross-section — plus a corner radius. The stretch endpoint checks installation: stretch = (mating diameter − o-ring ID) ÷ ID, which should stay under about 5 % on a rod because stretching thins the cross-section and steals squeeze. Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical-engineering, hydraulics, pneumatics, vacuum and product-design app developers, seal-selection and gland-design tools, and CAD plugins. Pure local computation — no key, no third-party service, instant. Inches or millimetres. Live, nothing stored. 3 compute endpoints.

api.oanor.com/oring-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

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