Single spur-gear geometry
API · /spurgear-api
Spur Gear API
healthy
4,957 Subscribers
Spur-gear geometry as an API, computed locally and deterministically for standard full-depth involute teeth. The geometry endpoint takes a module and a number of teeth (and an optional pressure angle, default 20°) and returns the complete tooth geometry: the pitch diameter (module × teeth), the base, tip (outside) and root diameters, the addendum, dedendum, whole and working depth, the circular and base pitch, the diametral pitch and the tooth thickness — all in millimetres. The module can be given directly or derived from a diametral pitch or a circular pitch. The pair endpoint meshes two gears of the same module and returns each gear's pitch and tip diameter, the centre distance (module × (z1 + z2) ÷ 2) and the gear ratio. The module endpoint converts freely between module, diametral pitch and circular pitch, or derives the module from a pitch diameter and tooth count. Everything is computed locally and deterministically, so it is instant and private. Ideal for machine-design and CAD tools, gear and gearbox calculators, maker, robotics and 3D-printing projects, and mechanical-engineering apps. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is spur-gear geometry; for bicycle gear ratios and development use a bike-gear API and for belt-and-pulley drives use a belt-drive API.
api.oanor.com/spurgear-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 81 ms
- Server probes · 24h
- Subscribers
- 4,957
- active
- Total calls
- 76
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 2,000 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- Pitch, addendum & dedendum diameters
- Standard full-depth involute teeth
- JSON geometry response
- 2 req/s burst limit
Starter
€9.00 /month
- 18,000 calls / month
- 5 requests / second
- Hard cap (429 above quota, no overage)
- Full tooth geometry from module + tooth count
- Root, base & outside diameters
- Deterministic, instant compute
- Email support
Pro
€24.00 /month
- 90,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- Batch gear-pair geometry
- Center distance & ratio output
- Metric module presets
- Priority support
Mega
€74.00 /month
- 408,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- High-volume CAD/CAM pipeline use
- Full involute profile parameters
- Highest throughput SLA
- Dedicated engineering support
Built by
Related APIs
Other APIs with overlapping tags.
Hammock Hang API
Hammock-hang maths as an API, computed locally and deterministically — the suspension-force, ridgeline and strap-height numbers a camper or hammock hanger sets up by. It all comes back to the 30-degree rule. The force endpoint shows why: the tension in each suspension line is the occupant weight ÷ (2 × sin of the hang angle), so at a 30° hang each strap carries about one body weight, but flatten the hang to 15° and it jumps to roughly 1.9 times — which is what over-stresses straps, trees and your back when people pull a hammock drum-tight. The ridgeline endpoint sizes a structural ridgeline at about 83 % of the hammock length, the fixed line that reproduces that ~30° lay and the right sag on any pair of trees. The strapheight endpoint estimates how high to attach the straps from the distance between the trees and the seat height you want, since trees farther apart need higher anchor points to hold the angle. Everything is computed locally and deterministically, so it is instant and private. Ideal for camping, backpacking, outdoor-gear and hammock app developers, hang-calculator and trip-planning tools, and adventure software. Pure local computation — no key, no third-party service, instant. Weight and lengths in your own unit. Live, nothing stored. 3 compute endpoints.
api.oanor.com/hammock-api
Sui Modules API
Inspect the Move smart-contract code published in any Sui package, live from a public Sui fullnode JSON-RPC — no key. Sui contracts are published as packages of Move modules; this reads their normalized ABI: list every module in a package, read a module's exposed functions (visibility, entry flag, type parameters with their abilities, parameter and return type tags) and struct definitions, or drill straight into a single function's signature. Unlike object- and coin-readers, this exposes the callable interface itself — exactly what a Sui package lets you do — the layer Sui wallets, explorers, programmable-transaction-block builders and SDK and binding generators need before they can construct a transaction. Reads straight from the chain; live, short cache only.
api.oanor.com/suimodules-api
Aptos Modules API
Inspect the Move smart-contract code published at any Aptos account, live from the official public Aptos fullnode REST API — no key. Where a resources endpoint shows an account's data, this shows its code: list the Move modules an account publishes, read any module's full ABI — its exposed functions with their visibility, entry and view flags, generic type parameters, parameter and return types, plus its struct definitions — and filter straight to the callable entry functions (state-changing transactions) and view functions (read-only queries) a dApp can invoke. The on-chain interface layer for Aptos wallets, explorers, SDK and binding generators, and security tooling that need to know exactly what a contract exposes before calling it. Reads straight from the chain; live, short cache only.
api.oanor.com/aptosmodules-api
Roller Chain Drive API
Roller-chain drive maths as an API, computed locally and deterministically — the chain-length, sprocket and speed numbers a machine designer or millwright lays out a drive with. The chain-length endpoint gives the chain in pitches from the two sprocket tooth counts, the chain pitch and the centre distance: L = 2·C + (N1+N2)/2 + ((N2−N1)/2π)² ÷ C (C in pitches), rounded UP to an even number so the chain closes without an offset link — a 17- and 34-tooth pair at 15-inch centres on #40 (half-inch) chain comes to 86 pitches, 43 inches. The sprocket endpoint gives the pitch diameter, pitch ÷ sin(180°/teeth), and the outside diameter — a 17-tooth #40 sprocket has a 2.72-inch pitch circle. The speed endpoint gives the chain's linear speed, pitch × teeth × rpm ÷ 12, so a 17-tooth #40 sprocket at 100 rpm runs the chain at about 71 ft/min. Everything is computed locally and deterministically, so it is instant and private. Ideal for machine-design and drivetrain apps, conveyor and equipment-build tools, maker and CAD calculators, and engineering aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For gear ratios use a gear-ratio API; for belts use a pulley API.
api.oanor.com/chaindrive-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Spur Gear API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Spur Gear API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Spur Gear 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 Spur Gear API cost?
Spur Gear 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 Spur Gear API GDPR-compliant?
All requests to Spur Gear 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/spurgear-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/spurgear-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/spurgear-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/spurgear-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.