Fatigue safety factors
API · /fatigue-api
Material Fatigue API
salutare
4,394 Abbonati
Mechanical-fatigue engineering maths as an API, computed locally and deterministically. The stress-cycle endpoint decomposes a cyclic load given by its maximum and minimum stress into the alternating stress σa = (σmax − σmin)/2, the mean stress σm = (σmax + σmin)/2, the stress range and the stress ratio R = σmin/σmax, and names the loading (fully reversed at R = −1, repeated at R = 0). The criteria endpoint computes the infinite-life safety factor against fatigue using the three classic mean-stress theories — Goodman (1/n = σa/Se + σm/Sut, standard and safe), Soderberg (uses the yield strength, conservative) and Gerber (a parabola, least conservative) — from the alternating and mean stress, the endurance limit Se, the ultimate strength Sut and an optional yield strength. The endurance-limit endpoint estimates the corrected endurance limit Se = ka·kb·kc·kd·ke·Se' from the ultimate strength, with Se' = 0.5·Sut for steel and the Marin modifying factors for surface finish, size, load type, temperature and reliability. Stresses and strengths use any one consistent unit (MPa is typical). Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical, structural, automotive and aerospace-design app developers, durability and safety-factor tools, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is fatigue and endurance; for static stress transformation use a Mohr-circle API and for column buckling a buckling API.
api.oanor.com/fatigue-api
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 78 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,394
- attiva
- Chiamate totali
- 76
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 2,100 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 2,100 llamadas/mes
- 2 req/seg
- Ciclo de estrés + criterios + resistencia
- Sin tarjeta de crédito
Starter
€9.00 /mese
- 37,000 chiamate/mese
- 6 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 37,000 calls/month
- 6 req/sec
- Goodman, Soderberg, Gerber factors
- Email support
Pro
€26.00 /mese
- 245,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 245,000 llamadas/mes
- 15 req/seg
- Tuberías de durabilidad y factor Marin
- Soporte prioritario
Mega
€78.00 /mese
- 1,680,000 chiamate/mese
- 40 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1,680,000 llamadas/mes
- 40 req/seg
- Escala de plataforma
- SLA dedicado
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Riveted Joint API
Riveted-joint strength maths as an API, computed locally and deterministically — the shear, bearing and rivet-count numbers a structural, sheet-metal or aircraft fitter checks a riveted connection by. The shear-capacity endpoint gives the load a rivet group carries across its shanks = the rivet area (π/4·d²) × the shear strength × the number of rivets × the shear planes — a rivet in single shear is cut on one plane, in double shear (the centre plate of a butt joint with cover plates) on two, so it carries twice. The bearing-capacity endpoint gives the load the rivets can press against the sides of their holes before the plate crushes = the projected contact area (diameter × plate thickness) × the bearing strength × the number of rivets; thin plates fail in bearing long before the rivet shears, which is exactly why both must be checked — the joint strength is the lesser of the two. The rivets-required endpoint inverts it: the rivets a design load needs = the load ÷ the allowable load per rivet (area × allowable shear × planes), rounded up to a whole rivet, using the working shear (strength ÷ safety factor) not the raw value. Everything is computed locally and deterministically, so it is instant and private. Ideal for structural and sheet-metal estimating, mechanical-design and fastener tools, and engineering calculators. Pure local computation — no key, no third-party service, instant. Shank-shear and bearing only — also confirm edge tear-out and minimum pitch. 3 compute endpoints. For bolt preload and torque use a bolt-torque API; for thread geometry a thread API; for welded joints a welding API.
api.oanor.com/rivet-api
Winch Drum API
Winch and cable-drum maths as an API, computed locally and deterministically — the rope-capacity, line-pull and rope-out numbers a winch operator, rigger or recovery driver works a drum with. The capacity endpoint gives the rope a drum holds by exact layer geometry: the sum over every full layer of the turns per layer × π × that layer's mean wrap diameter, where turns per layer = drum width ÷ rope diameter and the number of layers = the flange-to-barrel depth ÷ rope diameter — a 10-inch barrel, 20-inch flange, 12-inch-wide drum on half-inch rope holds about 940 ft over 10 layers. The layer-pull endpoint shows why pull falls as the drum fills: the rated pull is for the bare-drum first layer, and as rope piles on, the growing lever arm cuts the line pull and raises the line speed in the same ratio — pull × (first-layer diameter ÷ this layer's diameter) — so the top layer of a deep drum can pull barely half the bottom-layer rating, which is why you spool off to bare drum for a hard pull or add a snatch block. The length-at-layer endpoint gives the rope wound after a number of full layers, for marking the rope or knowing how much line is out. Everything is computed locally and deterministically, so it is instant and private. Ideal for winch- and hoist-sizing tools, recovery and off-road apps, marine and industrial-rigging utilities, and engineering calculators. Pure local computation — no key, no third-party service, instant. Geometric estimate — allow for nesting and freeboard. 3 compute endpoints. For capstan friction use a capstan API; for block-and-tackle a pulley API.
api.oanor.com/winch-api
Elevator Traction API
Traction-elevator engineering maths as an API, computed locally and deterministically — the counterweight, hoist-motor and rope-traction numbers a lift engineer or building-services designer sizes a passenger elevator with. The counterweight endpoint gives the balancing mass = the empty car plus a fraction of the rated load (the overbalance, typically 40–50 %, 45 % common), so a 1,000 kg car rated for 1,000 kg uses a 1,450 kg counterweight — the car and weight balance near half load and the machine is sized for the worst-case imbalance, not the full load. The motor-power endpoint uses that: because the counterweight cancels most of the car, the motor only lifts the out-of-balance load = rated load × (1 − overbalance), so power = that × g × speed ÷ efficiency (~65–75 % geared) — a 1,000 kg lift at 1.5 m/s needs only about 11–12 kW, half what a counterweight-less hoist would draw. The traction-ratio endpoint checks the friction grip: a traction elevator moves the ropes by friction over the sheave, so the available traction (e^(μθ), the capstan equation) must beat the T1/T2 tension ratio at both worst cases — a full car at the bottom and an empty car at the top — and it returns the governing ratio. Everything is computed locally and deterministically, so it is instant and private. Ideal for lift-design and building-services tools, vertical-transport and MEP utilities, and engineering calculators. Pure local computation — no key, no third-party service, instant. Sizing estimates — follow the lift code and maker data. 3 compute endpoints. For block-and-tackle use a pulley API; for capstan friction a capstan API.
api.oanor.com/elevator-api
HVAC Air-Side Load API
HVAC air-side heat maths as an API, computed locally and deterministically with the classic standard-air factors — the sensible, latent and airflow numbers a mechanical engineer or HVAC technician sizes ducts and equipment with. The sensible endpoint gives the sensible heat an airflow carries to change temperature: Qs = 1.08 × CFM × ΔT (dry-bulb difference), where the 1.08 bundles standard-air density and specific heat — 2,000 CFM across a 20 °F difference is 43,200 BTU/hr, 3.6 tons — with the result in BTU/hr, tons and kW. The latent endpoint gives the latent (moisture) heat: Ql = 0.68 × CFM × ΔW, where ΔW is the humidity-ratio difference in grains of water per pound of dry air, the dehumidification part of a cooling load that runs high in humid climates and from people and cooking, and why air conditioners are sized on total, not just temperature. The airflow endpoint inverts the sensible relation: CFM = sensible load ÷ (1.08 × ΔT), the supply air needed at a chosen supply-to-room temperature difference (comfort cooling runs ~18–22 °F below room), the number that sets fan and duct size — sanity-checked against ~400 CFM per ton. Everything is computed locally and deterministically, so it is instant and private. Ideal for HVAC-design and load-calc tools, mechanical-estimating and commissioning utilities, and building-engineering apps. Pure local computation — no key, no third-party service, instant. Standard-air factors — adjust for altitude. 3 compute endpoints. For room rule-of-thumb sizing use an HVAC API; for moist-air properties a psychrometric API; for duct sizing a ductwork API.
api.oanor.com/hvacload-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Material Fatigue API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Material Fatigue API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Material Fatigue 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 Material Fatigue API?
Material Fatigue 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.
Material Fatigue API è conforme al GDPR?
Tutte le richieste a Material Fatigue 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/fatigue-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/fatigue-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/fatigue-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/fatigue-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.