oanor
Sign up free
Marketplace Pricing Features Sign in

API · /oring-api

O-Ring Seal API

healthy 3,608 Subscribers

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.

#o-ring #seal #gland #mechanical-engineering #hydraulics #developer-tools
api.oanor.com/oring-api
Get an API key Try in playground → Contact provider

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

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

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

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
94 ms
Server probes · 24h
Subscribers
3,608
active
Total calls
4
last 7 days
status Full status page → · 8 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 6,550 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 6,550 calls/month
  • 2 req/sec
  • Squeeze + gland + stretch
  • No credit card
Sign in to subscribe

Starter

€4.52 /month

  • 51,800 calls / month
  • 6 requests / second
  • Hard cap (429 above quota, no overage)
  • 51,800 calls/month
  • 6 req/sec
  • Gland fill, static/dynamic, in/mm
  • Email support
Sign in to subscribe

Pro

€12.38 /month

  • 215,000 calls / month
  • 15 requests / second
  • Hard cap (429 above quota, no overage)
  • 215,000 calls/month
  • 15 req/sec
  • Seal-selection & gland-design pipelines
  • Priority support
Sign in to subscribe

Mega

€39.40 /month

  • 1,282,000 calls / month
  • 40 requests / second
  • Hard cap (429 above quota, no overage)
  • 1,282,000 calls/month
  • 40 req/sec
  • Platform scale
  • Dedicated SLA
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

Belt Conveyor API

Belt-conveyor design maths as an API, computed locally and deterministically. The capacity endpoint computes the throughput of a belt conveyor — the volumetric capacity Q = A·v·3600 (m³/h) from the belt cross-section and speed, and the mass capacity Q·ρ/1000 (t/h) from the bulk density — and, when only the belt width is given, estimates the cross-section as A ≈ load_factor·width². The power endpoint computes the drive power as the sum of the horizontal friction power, μ·g·(material + 2·belt + idler mass per metre)·length·speed, and the vertical lift power, ṁ·g·height, then divides by the drive efficiency to give the motor power. The tension endpoint computes the belt tensions from the effective tension Te = P/v: the tight-side tension T1 = Te·e^(μθ)/(e^(μθ)−1) and the slack-side tension T2 = T1 − Te, using the Euler-Eytelwein grip of the belt on the drive pulley. Everything is computed locally and deterministically, so it is instant and private. Ideal for bulk-materials-handling, mining and plant-design tools, conveyor selection and motor sizing, and mechanical-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is a simplified belt-conveyor model; for rope/belt capstan friction use a capstan API and for belt-drive geometry use a belt-drive API.

api.oanor.com/conveyor-api

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

Bolt Torque API

Bolted-joint torque, preload and stress maths as an API, computed locally and deterministically for ISO metric fasteners. The torque endpoint applies the torque-tension relation T = K·D·F — the tightening torque equals the nut factor times the nominal diameter times the bolt preload — and solves either way: the torque needed for a target preload, or the preload achieved by a given torque, with the nut factor K capturing the lubrication condition (≈0.20 plain, 0.16 plated, 0.12 lubricated). The stressarea endpoint computes the tensile stress area from the thread geometry, As = π/4·(d − 0.9382·P)² — the effective cross-section that carries the load — together with the nominal shank area and, given a proof or yield stress, the proof and yield loads of the bolt. The preload endpoint sets the clamp force as a percentage of the proof load (75 % is the usual target for reusable joints), F = (percent/100)·σproof·As, and returns the resulting tensile stress and, with a diameter and nut factor, the tightening torque. Grade proof stresses for 8.8, 10.9 and 12.9 bolts are documented. Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical-design, assembly and maintenance tools, torque-spec generation, fastener selection and structural-bolting apps, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is bolt tightening and preload mechanics; for thread pitch/lead geometry use a thread API and for bolt-circle hole patterns use a bolt-circle API.

api.oanor.com/bolttorque-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

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