Cylinder push/pull force
API · /hydraulic-api
Hydraulic Press & Pascal API
salutare
4,023 Abbonati
Pascal's-principle hydraulics as an API, computed locally and deterministically. The press endpoint computes the force multiplication of a hydraulic press, jack or master/slave cylinder: a pressure P = F/A acts equally throughout a connected fluid, so a small input force on a small piston becomes a large output force on a large piston, F2 = F1·A2/A1, with the mechanical advantage A2/A1 — areas given directly or as piston diameters, and the pressure in pascals, bar and psi. The stroke endpoint applies volume conservation, A1·d1 = A2·d2: the big piston moves less the more force it gains, and the work F·d is the same on both sides. The cylinder endpoint gives the push and pull force of a hydraulic cylinder at a pressure, F = P·A on the bore side and F = P·(A_bore − A_rod) on the rod (annulus) side. Everything is computed locally and deterministically, so it is instant and private. Ideal for hydraulics and fluid-power engineering tools, press, jack and lift design, brake and machine apps, and physics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is Pascal-principle force multiplication; for pressure at depth and force on a submerged wall use a hydrostatics API and for pump power use a pump API.
api.oanor.com/hydraulic-api
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 90 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,023
- attiva
- Chiamate totali
- 36
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 2,000 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 19,635 calls/month
- 2 req/sec
- Press + stroke + cylinder
- No credit card
Starter
€9.00 /mese
- 25,000 chiamate/mese
- 8 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 30.95k calls/month
- 8 req/sec
- Diameters, work, push & pull
- Email support
Pro
€24.00 /mese
- 150,000 chiamate/mese
- 25 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 343.5k calls/month
- 20 req/sec
- Fluid-power / press pipelines
- Priority support
Mega
€74.00 /mese
- 773,000 chiamate/mese
- 80 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1.76M calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
News API
Busque notícias e obtenha manchetes principais de milhares de editores em todo o mundo, por tópico, país e idioma. Cada artigo inclui título, editor, data de publicação, link e um trecho — alimentado pelo Google News.
api.oanor.com/news-api
O-Ring Seal API
O-Ring-Dichtungs-Design-Mathematik als API, lokal und deterministisch berechnet – die Squeeze-, Gland- und Stretch-Werte, die ein Ingenieur oder Hersteller für eine Dichtung entwirft. Der Squeeze-Endpunkt liefert die Kompression, die die Dichtung bewirkt: Squeeze = (Querschnitt − Nuttiefe) ÷ Querschnitt, also wird eine 0,139-Zoll-Schnur in einer 0,113-Zoll-tiefen Nut um 18,7 % gequetscht, und bewertet das Ergebnis – etwa 10–16 % eignet sich für dynamische (hin- und hergehende) Dichtungen und 15–30 % für statische – und, bei gegebener Nutbreite, den Nutfüllgrad, der unter etwa 85 % bleiben sollte, damit der Gummi Platz zum Ausdehnen durch Hitze oder Flüssigkeitsquellung hat. Der Gland-Endpunkt arbeitet umgekehrt: Aus dem Querschnitt und ob die Dichtung statisch oder dynamisch ist (oder einem Ziel-Squeeze) gibt er die Nuttiefe und eine Breite zurück, die für etwa 70 % Füllung ausgelegt ist – typischerweise das 1,3- bis 1,5-fache des Querschnitts – plus einen Eckradius. Der Stretch-Endpunkt prüft die Installation: Stretch = (Paarungsdurchmesser − O-Ring-ID) ÷ ID, der unter etwa 5 % auf einer Stange bleiben sollte, da Dehnung den Querschnitt verringert und Squeeze stiehlt. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für App-Entwickler im Maschinenbau, Hydraulik, Pneumatik, Vakuum- und Produktdesign, Dichtungsauswahl- und Nutdesign-Tools sowie CAD-Plugins. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Zoll oder Millimeter. Live, nichts gespeichert. 3 Compute-Endpunkte.
api.oanor.com/oring-api
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
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Hydraulic Press & Pascal API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Hydraulic Press & Pascal API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Hydraulic Press & Pascal API?
Il piano gratuito consente 1 richiesta al secondo. I piani a pagamento arrivano fino a 50 richieste al secondo nel piano Mega. I limiti rigorosi restituiscono HTTP 429 oltre la quota — nessuna spesa imprevista.
Quanto costa Hydraulic Press & Pascal API?
Hydraulic Press & Pascal API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €9.00 / mese con quote più alte e limiti di velocità più rapidi.
Posso cancellare l'abbonamento in qualsiasi momento?
Sì. I piani sono fatturati mensilmente e puoi cancellare in qualsiasi momento dalla dashboard di fatturazione. Nessun contratto a lungo termine e nessuna penale di cancellazione.
Hydraulic Press & Pascal API è conforme al GDPR?
Tutte le richieste a Hydraulic Press & Pascal API passano attraverso il nostro gateway in UE. La tua chiave upstream non lascia mai il nostro server e nessun dato personale viene condiviso con il fornitore upstream oltre alla richiesta inviata.
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo slug.
curl https://api.oanor.com/hydraulic-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/hydraulic-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/hydraulic-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/hydraulic-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
📌 Fissato
🔒 Bloccato
·
·
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.