oanor
Iscriviti gratis
Mercata Prezzi Caratteristiche Accedi

API · /compressor-api

Air Compressor API

salutare 3,866 Abbonati

Druckluft-Mathematik als API, lokal und deterministisch berechnet – die Receiver-, Pump-up- und SCFM-Zahlen, mit denen ein Pneumatik-Techniker oder Werkstattbesitzer ein System dimensioniert. Der Receiver-Size-Endpunkt gibt den Tank an, den Sie benötigen, um einen Bedarfsspitze zu überbrücken: Volumen = Bedarf (freie Luft CFM) × Minuten × 14,7 ÷ das nutzbare Druckfenster (max − min) – bei 20 CFM für eine Minute über ein 175-zu-100-psi-Fenster wird ein etwa 30-Gallonen-Receiver benötigt, der Puffer, der die Pumpe aufholen lässt. Der Pumpup-Endpunkt gibt die Zeit an, um einen Receiver von einem Druck auf einen anderen zu bringen: Volumen × Druckanstieg ÷ (14,7 × Kompressor-CFM), also benötigt ein 60-Gallonen-Tank von 100 auf 175 psi bei einem 15-CFM-Kompressor etwa 2,7 Minuten. Der SCFM-Endpunkt korrigiert tatsächliche CFM auf Standard-CFM für die Einlassbedingungen – SCFM = ACFM × (Einlassdruck ÷ 14,696) × (528 ÷ Einlasstemperatur in Rankine) – ein Kompressor auf 5.000 Fuß liefert also etwa 17 % weniger SCFM als auf Meereshöhe, der Grund, warum Sie Werkzeuge nach SCFM und nicht nach dem Typenschild dimensionieren. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Pneumatik- und Werkstattluft-Apps, Kompressor-Dimensionierungs- und Werkzeugbedarfs-Tools, Industrieluft-Rechner und Handwerkshilfen. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Live, nichts wird gespeichert. 3 Compute-Endpunkte. Schätzungen – Einschaltdauer und die Pumpenkennlinie verschieben die tatsächlichen Zahlen.

#compressor #pneumatics #compressed-air #shop #industrial #developer-tools
api.oanor.com/compressor-api
Ottieni una chiave API Prova nel parco giochi → Contatta provider

Specifica leggibile dalle macchine, così gli agenti AI possono integrare questa API.

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

Individuazione: GET /api/index.json elenca ogni API.

API salute

salutare
Tempo di attività
100.00%
Sondaggi del server · 24 ore su 24
Latenza media
115 ms
Sondaggi del server · 24 ore su 24
Abbonati
3,866
attiva
Chiamate totali
0
ultimi 7 giorni
status Pagina di stato completa → · 4 sonde/24h

Prezzi

Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.

Free

Gratis

  • 460 chiamate/mese
  • 2 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 460 Aufrufe/Monat
  • 2 req/sec
  • Receiver + pump-up + SCFM
  • Keine Kreditkarte
Accedi per abbonarti

Starter

€5.75 /mese

  • 12,400 chiamate/mese
  • 6 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 12.400 Aufrufe/Monat
  • 6 req/sec
  • Altitude SCFM correction
  • E-Mail-Support
Accedi per abbonarti

Pro

€18.10 /mese

  • 79,000 chiamate/mese
  • 15 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 79.000 Aufrufe/Monat
  • 15 req/sec
  • Sizing- und Shop-Pipelines
  • Prioritäts-Support
Accedi per abbonarti

Mega

€53.60 /mese

  • 256,000 chiamate/mese
  • 36 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 256.000 Aufrufe/Monat
  • 36 req/sec
  • Plattform-Skalierung
  • Dedizierte SLA
Accedi per abbonarti

Costruito da

P
PremiumApi

Correlato APIs

Altro APIs con tag sovrapposti.

Industrial Coatings API

Industrial and protective-coatings maths as an API, computed locally and deterministically — the film-build numbers a coatings inspector, painter or estimator works to, the ones simple paint estimating skips. The coverage endpoint gives theoretical and practical coverage from the coating's volume solids and the target dry film thickness: coverage = 1604 × the volume-solids fraction ÷ the DFT in mils, where 1604 is the square feet a gallon covers at one mil — so a 50 %-solids coating at 2 mils dry covers about 401 ft² per gallon, less a loss factor for overspray and surface profile. The film-thickness endpoint converts between wet and dry film thickness through the volume solids: WFT = DFT ÷ the solids fraction, because the solvent flashes off and the film shrinks, so a 50 %-solids coating laid 4 mils wet dries to 2 mils — the number you check with a wet-film comb as you spray. The transfer-efficiency endpoint gives the real material needed: theoretical gallons ÷ the transfer efficiency, since conventional spray lands only ~25 % on the part, HVLP ~65 %, electrostatic up to ~95 %. Everything is computed locally and deterministically, so it is instant and private. Ideal for coatings-estimating and inspection apps, industrial-painting and protective-coating tools, NACE/SSPC study aids, and spec calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For simple wall-paint area estimating use a paint API.

api.oanor.com/coating-api

Tank Volume API

Tank volume and fill-level maths as an API, computed locally and deterministically. The volume endpoint gives the total capacity — in litres, US gallons and cubic metres — of a vertical cylinder, horizontal cylinder, rectangular tank, sphere or capsule, from its dimensions in metres, centimetres, millimetres, feet or inches. The fill endpoint computes the volume of liquid and the percent full at a given fill depth, using the exact geometry for each shape — including the circular-segment formula for a horizontal cylinder (where the level is famously non-linear) and the spherical-cap formula for a sphere. The level endpoint is the inverse "dipstick" calculation: it finds the depth that corresponds to a target volume or a target percentage, solving the segment geometry by bisection. Everything is computed locally and deterministically, so it is instant and private. Ideal for fuel, water, oil and chemical tank monitoring, agriculture and irrigation, process and industrial tooling, and tank-gauging and dipstick apps. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is tank-gauging geometry; for swimming-pool volume and chemical dosing use a pool API, and for plain unit conversion use a unit-conversion API.

api.oanor.com/tank-api

Screw Auger API

Screw-conveyor and grain-auger maths as an API, computed locally and deterministically — the capacity, speed and throughput numbers a farmer, millwright or material-handling engineer sizes an auger with. The capacity endpoint gives the volumetric throughput from the screw geometry: the annular flight volume per turn ((π/4)(diameter² − shaft²) × pitch) × rpm × 60 × the trough loading, so a 9-inch full-pitch screw on a 2.5-inch shaft at 40 rpm and 45 % loading moves about 330 cubic feet — 265 bushels — an hour. The speed endpoint inverts it, the rpm needed for a target capacity, so you don't overspeed a small auger and grind the grain. The bushels endpoint converts a volumetric rate to bushels and tons per hour (1 bushel = 1.2445 ft³, tons = bushels × test weight ÷ 2000), so 330 ft³/hr of 56-lb corn is 265 bushels or 7.4 tons an hour — the number you match to the dryer or the truck. Everything is computed locally and deterministically, so it is instant and private. Ideal for grain-handling and ag-equipment apps, material-handling and conveyor-design tools, farm-build calculators, and engineering aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — incline and material change real throughput. For belt conveyors use a conveyor API.

api.oanor.com/auger-api

Radiant Floor API

Radiant-Floor- und Hydronic-Heizungsmathematik als API, lokal und deterministisch berechnet – die Output-, Rohr- und Durchflusszahlen, mit denen ein Installateur oder Heimwerker einen warmen Fußboden plant. Der Output-Endpunkt gibt die Wärme aus, die ein warmer Fußboden abgibt: etwa 2 BTU/h pro Quadratfuß für jedes °F, das die Bodenoberfläche wärmer als der Raum ist, also liefert ein 85 °F-Boden in einem 70 °F-Raum etwa 30 BTU/h/ft² – etwa 9.000 BTU/h über 300 ft², die Komfortgrenze, da der Boden bei ~85 °F gehalten wird. Der Rohr-Endpunkt gibt das Rohr und die Schleifen für eine Fläche bei einem Abstand an: Feldrohr = Fläche × 12 ÷ Abstand, also benötigt 300 ft² bei 9-Zoll-Abstand 400 Fuß Rohr, aufgeteilt in Schleifen unter ~300 Fuß (zwei 200-Fuß-Schleifen), damit die Pumpe sie durchdrücken kann. Der Durchfluss-Endpunkt gibt die Schleifendurchflussrate für eine Heizlast an, GPM = Last ÷ (500 × ΔT), wobei 500 die Wasserkonstante und ΔT die Vorlauf-Rücklauf-Differenz ist – 9.000 BTU/h bei einer ΔT von 20 °F benötigt 0,9 GPM. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Fußbodenheizungs- und Sanitäranwendungen, Hydronic-Design- und PEX-Layout-Tools, HVAC-Rechner für Auftragnehmer und DIY-Bau-Seiten. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Live, nichts gespeichert. 3 Compute-Endpunkte. Schätzungen – mit einer vollständigen Wärmeverlustberechnung überprüfen. Für die Gebäudelast eine HVAC-API verwenden; für die Rohrgeschwindigkeit eine Durchflussraten-API.

api.oanor.com/radiant-api

Domande frequenti

Risposte rapide su prezzi, quote e integrazione.

Come ottengo una chiave API per Air Compressor API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Air Compressor API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Air Compressor 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 Air Compressor API?
Air Compressor API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €5.75 / 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.
Air Compressor API è conforme al GDPR?
Tutte le richieste a Air Compressor 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/compressor-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/compressor-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/compressor-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/compressor-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.

Accedi

Nuova discussione

/ 4000

📌 Fissato 🔒 Bloccato

·

· ·

/ 4000

🔒 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.

Accedi

Apri nuovo ticket

Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.

  • Nessun ticket per questa API.

Abbonamento attivo: le chiamate possono iniziare subito.

Invia la tua prima richiesta —

Abbonamento attivo: copia uno snippet e avvia la tua prima chiamata.