Coverage from solids & DFT
API · /coating-api
Industrial Coatings API
salutare
3,042 Abbonati
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
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 79 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 3,042
- attiva
- Chiamate totali
- 76
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 440 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 440 Aufrufe/Monat
- 2 req/sec
- Coverage + Filmdicke + TE
- Keine Kreditkarte
Starter
€5.65 /mese
- 11,800 chiamate/mese
- 6 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 11.800 Aufrufe/Monat
- 6 req/sec
- Volumen-Feststoffe & WFT/DFT
- E-Mail-Support
Pro
€17.90 /mese
- 76,500 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 76.500 Aufrufe/Monat
- 15 req/sec
- Schätz- und Inspektionspipelines
- Prioritäts-Support
Mega
€53.00 /mese
- 252,000 chiamate/mese
- 36 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 252.000 Aufrufe/Monat
- 36 req/sec
- Plattform-Skalierung
- Dedizierte SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Air Compressor API
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.
api.oanor.com/compressor-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
Handrail & Baluster API
Railing and baluster layout maths as an API, computed locally and deterministically — the baluster-count, spacing and post numbers a deck builder, fabricator or balustrade designer sets a guardrail out with. The baluster-count endpoint gives the smallest number of balusters that keeps every gap within the safety limit: between two posts n balusters leave n+1 gaps, so the count = ceil((rail length − max gap) ÷ (baluster width + max gap)). The usual guardrail limit is a 100 mm (4-inch) sphere — a child-safety rule — so a 2000 mm rail with 40 mm balusters needs 14 of them at even 96 mm gaps; round up, because one fewer opens the gaps past the limit. The layout endpoint sets out a known count evenly: the gap = (rail length − total baluster width) ÷ (count + 1), the centre-to-centre pitch = baluster width + gap, and the first baluster's centre sits one gap plus half a baluster from the post face, so you mark the first centre and step off the pitch with the last gap landing equal to the first. The post-count endpoint sizes the frame: a run needs one more post than spans, spans = ceil(run ÷ max post spacing), posts = spans + 1, even spacing = run ÷ spans — a 6 m run at a 1.8 m max takes 4 spans and 5 posts at a tidy 1.5 m. Everything is computed locally and deterministically, so it is instant and private. Ideal for deck and balustrade design tools, fabrication and estimating apps, and building calculators. Pure local computation — no key, no third-party service, instant. Uses the common 100 mm infill rule — confirm your local code. 3 compute endpoints. For stair rise and run use a stair API; for fence pickets a fence API.
api.oanor.com/handrail-api
Arch Geometry API
Circular-segment arch geometry as an API, computed locally and deterministically — the radius, arc-length and set-out numbers a mason, joiner, stonemason or CAD user lays a segmental arch out with. A segmental arch is an arc of a circle struck through the two springings and the crown: the from-span-rise endpoint takes the span and the rise (the height of the crown above the springing line) and returns the radius = (span²/4 + rise²) ÷ (2·rise), the central angle it subtends, the arc length along the curve, and the segment area of the void below it — flatter arches with a small rise have surprisingly huge radii. The from-radius-angle endpoint inverts it, returning the chord (span), the rise (sagitta), the arc length and the area from a known radius and central angle, the way a curve struck with a trammel or a router on a pivot is described. The setout-ordinates endpoint gives the practical numbers to mark a template: the rise of the arc above a straight base line at equally spaced stations across the span (y = √(R² − x²) − (R − rise)), so you can plot the heights, connect them and cut a plywood former or bend a batten without a giant compass — the ends come out zero at the springings and the middle equals the rise at the crown. Everything is computed locally and deterministically, so it is instant and private. Ideal for masonry and joinery layout tools, stair and window-head design, and CAD and woodworking calculators. Pure local computation — no key, no third-party service, instant. Segmental (up to a semicircle) arcs. 3 compute endpoints. For road curves use a horizontal- or vertical-curve API; for plain shape areas a geometry API.
api.oanor.com/arch-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Industrial Coatings API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Industrial Coatings API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Industrial Coatings 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 Industrial Coatings API?
Industrial Coatings API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €5.65 / 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.
Industrial Coatings API è conforme al GDPR?
Tutte le richieste a Industrial Coatings 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/coating-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/coating-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/coating-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/coating-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.