Impedance transformation
API · /transformer-api
Transformer Ratio API
salutare
4,979 Abbonati
Ideal-transformer relations as an API, computed locally and deterministically. The transformer endpoint works from the turns ratio a = Np/Ns = Vp/Vs = Is/Ip: give any ratio-defining pair — the primary and secondary turns, voltages or currents — and it derives the rest, classifies the transformer as step-up, step-down or 1:1 isolation, and reports the primary and secondary apparent power (which are equal for an ideal transformer, so a step-down in voltage is a step-up in current). The power endpoint applies the power balance with an efficiency, Ps = η·Pp, from the primary or secondary power (given directly or as voltage times current) and reports the power loss. The impedance endpoint reflects an impedance across the transformer, Zp/Zs = (Np/Ns)² = a² — the basis of impedance matching, so an 8 Ω speaker on a 10:1 transformer looks like 800 Ω to the source. Everything is computed locally and deterministically, so it is instant and private. Ideal for electrical and electronics-engineering tools, power-supply and audio-amplifier design, impedance-matching and EE-education apps. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is ideal-transformer ratios; for Ohm's law, reactance and series/parallel components use an Ohm's-law API.
api.oanor.com/transformer-api
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 91 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,979
- attiva
- Chiamate totali
- 32
- 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,135 calls/month
- 2 req/sec
- Ratio + power + impedance
- No credit card
Starter
€9.00 /mese
- 25,000 chiamate/mese
- 5 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 30.45k calls/month
- 8 req/sec
- Step-up/down, impedance matching
- Email support
Pro
€24.00 /mese
- 150,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 338.5k calls/month
- 20 req/sec
- Power-supply / audio design pipelines
- Priority support
Mega
€75.00 /mese
- 768,000 chiamate/mese
- 40 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1.735M llamadas/mes
- 50 req/seg
- Escala de plataforma
- SLA dedicado
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Voltage Drop API
Cable voltage-drop and conductor-sizing maths as an API, computed locally and deterministically. The drop endpoint computes the voltage lost along a cable run from the current, the one-way run length, the conductor cross-section and the material: the conductor resistance R = ρ·L/A, the voltage drop Vd = k·I·R (k = 2 for single-phase, √3 for three-phase), the drop as a percentage of the supply and the voltage left at the load. The sizing endpoint works backwards: from an allowable percentage drop it returns the minimum conductor cross-section needed, A ≥ k·I·ρ·L/Vd_allow, rounds up to the next standard cable size (1.5, 2.5, 4, 6, 10, 16, 25 … mm²) and reports the actual drop at that size. The power endpoint computes the power dissipated as heat in the cable, P = N·I²·R (N = 2 or 3 current-carrying conductors), and the cable efficiency given a load power. Copper (ρ = 0.0172) and aluminium (ρ = 0.0282 Ω·mm²/m) are supported. Everything is computed locally and deterministically, so it is instant and private. Ideal for electrical-installation and panel-design tools, cable selection to wiring-regulation limits, solar, EV-charger and sub-main sizing, and electrical-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is cable voltage drop and sizing; for Ohm's law, reactance and resonance use an Ohm's-law API and for transformer ratios use a transformer API.
api.oanor.com/voltagedrop-api
Power Factor & AC Power API
AC power triangle and power-factor maths as an API, computed locally and deterministically. The power-factor endpoint solves the power triangle: from any two of the apparent power S (volt-amperes), the real power P (watts), the reactive power Q (VAR), the power factor (cos φ) or the phase angle it returns all of them, using S = √(P²+Q²), P = S·cosφ, Q = S·sinφ and PF = P/S. The load endpoint computes the powers of a load directly from its voltage, current and power factor — single-phase S = V·I or three-phase S = √3·V·I from line values. The correction endpoint sizes power-factor correction: the reactive power a capacitor must supply to raise the power factor from a present value to a target, Qc = P·(tanφ1 − tanφ2), and — given the supply voltage and frequency — the capacitance, C = Qc/(2π·f·V²), the basis of cutting reactive demand and utility penalties. Everything is computed locally and deterministically, so it is instant and private. Ideal for electrical-engineering and power-systems tools, motor, industrial and HVAC load analysis, energy-billing and power-quality apps. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is AC power and power-factor correction; for Ohm's law, reactance and resonance use an Ohm's-law API.
api.oanor.com/powerfactor-api
Coulomb & Electric Field API
Coulomb's-law electrostatics as an API, computed locally and deterministically. The force endpoint computes the electrostatic force between two point charges, F = k·q1·q2/(εr·r²) — Coulomb's law, with k = 8.9876×10⁹ N·m²/C² — from the two charges, their separation and an optional relative permittivity for a dielectric medium, and tells you whether the force is attractive (opposite signs) or repulsive (like signs). The field endpoint gives the electric field of a point charge, E = k·q/(εr·r²), its direction (away from a positive charge, toward a negative one), and the force on a test charge placed there, F = q_test·E. The potential endpoint gives the electric potential V = k·q/(εr·r) and, for a pair of charges, the electrostatic potential energy U = k·q1·q2/(εr·r) in joules and electron-volts. Charges may be entered in coulombs, microcoulombs or nanocoulombs. Everything is computed locally and deterministically, so it is instant and private. Ideal for physics and electrical-engineering education tools, electrostatics and field-theory apps, and laboratory and simulation software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is electrostatics; for Ohm's law and DC/AC circuits use an Ohm's-law API.
api.oanor.com/coulomb-api
Transmission Line API
Transmission-line RF maths as an API, computed locally and deterministically for a lossless line. The input-impedance endpoint transforms a complex load impedance along a line, Zin = Z0·(ZL + jZ0·tanβl)/(Z0 + jZL·tanβl), from the characteristic impedance, the load resistance and reactance and the electrical length in degrees — a quarter-wave (90°) line inverts the load to Z0²/ZL while a half-wave (180°) line repeats it, which is the basis of impedance matching. The quarter-wave endpoint computes the characteristic impedance Z0 = √(Z1·Z2) of a quarter-wave transformer that matches two real impedances, exact at one frequency. The electrical-length endpoint converts a physical line length to its electrical length in wavelengths, degrees and radians at a frequency, using the on-line wavelength λ = vf·c/f with a velocity factor for the dielectric. Impedances are in ohms (the load split into resistance and reactance), electrical length in degrees, physical length in metres and frequency in hertz. Everything is computed locally and deterministically, so it is instant and private. Ideal for RF, antenna-matching, PCB, radar and microwave app developers, stub-matching and transformer-design tools, and electromagnetics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is line impedance transformation; for SWR and return loss use a VSWR API and for microstrip trace geometry a PCB API.
api.oanor.com/transmissionline-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Transformer Ratio API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Transformer Ratio API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Transformer Ratio 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 Transformer Ratio API?
Transformer Ratio 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.
Transformer Ratio API è conforme al GDPR?
Tutte le richieste a Transformer Ratio 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/transformer-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/transformer-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/transformer-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/transformer-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.