API · /ppi-api

Screen PPI API

salutare 3,799 Abbonati

Screen and display pixel-density maths as an API, computed locally and deterministically. The ppi endpoint computes the pixels per inch of a display from its resolution and diagonal size — along with the pixels per centimetre, the dot pitch in millimetres, the diagonal in pixels, the total pixels and megapixels, the simplified aspect ratio, and the physical width and height. The size endpoint does the inverse: from a resolution and a known PPI it works out the physical dimensions and diagonal in inches and centimetres. The retina endpoint analyses a display at a viewing distance: it computes the pixels per degree, says whether the display is effectively "retina" (pixels indistinguishable to 20/20 vision, around 60 pixels per degree), and gives the distance at which it becomes retina. Everything is computed locally and deterministically, so it is instant and private. Ideal for display and monitor tools, AV and signage planning, UI and responsive-design work, and hardware comparison sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is screen pixel density; for print resolution and image-to-print sizing use a DPI API.

api.oanor.com/ppi-api
Ottieni una chiave API Prova nel parco giochi → Contatta provider

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

/api/ppi-api/openapi.json
/api/ppi-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
81 ms
Sondaggi del server · 24 ore su 24
Abbonati
3,799
attiva
Chiamate totali
52
ultimi 7 giorni

Prezzi

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

Free

Gratis

  • 10,135 chiamate/mese
  • 2 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 10,135 llamadas/mes
  • 2 solicitudes/seg
  • PPI + tamaño + retina
  • Sin tarjeta de crédito
Accedi per abbonarti

Starter

€11.65 /mese

  • 19,750 chiamate/mese
  • 8 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 19.75k calls/month
  • 8 req/sec
  • Dot pitch + aspect ratio
  • Email support
Accedi per abbonarti

Pro

€31.55 /mese

  • 247,500 chiamate/mese
  • 20 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 247.5k calls/month
  • 20 req/sec
  • Display / AV pipelines
  • Priority support
Accedi per abbonarti

Mega

€69.55 /mese

  • 1,280,000 chiamate/mese
  • 50 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 1.28M llamadas/mes
  • 50 req/seg
  • Escala de plataforma
  • SLA dedicado
Accedi per abbonarti

Costruito da

Correlato APIs

Altro APIs con tag sovrapposti.

DPI & Print Size API

Resolution, print-size and pixel-density maths for print, design, photography and screens. The resolve endpoint takes any two of pixels, DPI and physical length and computes the third, returning the size in inches, centimetres, millimetres and points — so you can answer "how big will a 3000-pixel image print at 300 DPI" or "what DPI do I get printing 3000 px at 10 inches". The ppi endpoint computes a screen's pixel density from its resolution and diagonal size, plus the dot pitch in millimetres, the total megapixels and the aspect ratio. The convert endpoint converts a length between pixels, inches, centimetres, millimetres and points (PostScript points, 1/72 inch), using a DPI when pixels are involved. Everything is computed locally and deterministically, so it is instant and private. Ideal for print and prepress, graphic and web design, photography, and screen and display specs. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is DPI and print-size maths; for aspect ratios and resizing use an aspect-ratio API and for general unit conversion use a unit API.

api.oanor.com/dpi-api

Mask API

Mascara un valor para mostrarlo de forma segura. El endpoint de máscara mantiene visibles los primeros y/o últimos caracteres y reemplaza el resto con un carácter de máscara — así una tarjeta se convierte en ••••••••••••1111 y un token API en sk**********3456 — y puede mantener intactos los separadores (espacios y guiones) para que el valor conserve su forma. Un enmascarador de correo electrónico dedicado oculta la parte local (y opcionalmente el dominio) mientras mantiene la dirección reconocible, por ejemplo, j•••••••@example.com. Elige cuántos caracteres revelar y qué carácter de máscara usar. Perfecto para mostrar los últimos cuatro dígitos de una tarjeta, ocultar parcialmente correos electrónicos y números de teléfono, y enmascarar tokens y números de cuenta en interfaces de usuario, recibos y registros. Cálculo puramente local — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 3 endpoints. Esto enmascara un valor conocido para su visualización; para encontrar y redactar PII dentro de texto libre, usa una API de redacción.

api.oanor.com/mask-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

Railway Tractive Effort API

Railway train-performance maths as an API, computed locally and deterministically — the tractive-effort, resistance and adhesion numbers a railway engineer, train planner or rail-sim developer rates motive power with. The tractive-effort endpoint gives the pulling force a locomotive develops = 375 × horsepower × efficiency ÷ speed (mph), the classic hyperbolic curve where a constant-power loco pulls hardest at low speed and tapers as it accelerates — 4,000 hp at 25 mph and 82 % efficiency is about 49,200 lbf at the rail. The resistance endpoint gives the forces a train fights: grade resistance ≈ 20 lb per ton per 1 % of grade (the weight component along the slope, the dominant force on a hill — a 5,000-ton train on a 1 % grade fights 100,000 lbf) plus curve resistance ≈ 0.8 lb per ton per degree of curve from flange friction. The adhesion endpoint gives the hard ceiling: however much power a loco has, it can only pull as hard as the wheels grip — maximum starting tractive effort = the adhesion coefficient (≈ 0.25 dry, more with sand) × the weight on the driving wheels, so 200 tons on the drivers is about 100,000 lbf before slip. Everything is computed locally and deterministically, so it is instant and private. Ideal for rail-operations and motive-power planning tools, train-simulator and railfan apps, and transport-engineering utilities. Pure local computation — no key, no third-party service, instant. Excludes the speed-dependent Davis rolling/air resistance. 3 compute endpoints. For highway curve geometry use a horizontal-curve API.

api.oanor.com/railway-api

Domande frequenti

Risposte rapide su prezzi, quote e integrazione.

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