#gear-ratio

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

Tyre, wheel and drivetrain maths as an API. The tire endpoint parses a metric tyre size such as 205/55R16 into all its real dimensions — section width, aspect ratio, sidewall height, rim and overall diameter in millimetres and inches, rolling circumference, and revolutions per kilometre and per mile. The compare endpoint takes an original and a replacement tyre size and works out the change in overall diameter and the resulting speedometer and odometer error — so you know how much faster you are really going than the dial shows after a tyre change. The gear endpoint computes a gear ratio from ring and pinion tooth counts, or the road speed from engine RPM, total gear ratio and tyre size. Everything is computed locally and deterministically, so it is instant and private. Ideal for automotive and motorsport apps, tyre shops and fitment tools, modding and restomod planning, and vehicle configurators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is tyre and drivetrain maths; for vehicle specifications by VIN use a vehicle-database API.

api.oanor.com/tirecalc-api