Impedance transformation
API · /transformer-api
Transformer Ratio API
healthy
4,979 Subscribers
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 health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 91 ms
- Server probes · 24h
- Subscribers
- 4,979
- active
- Total calls
- 32
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 2,000 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- Turns ratio a = Np/Ns from voltage or turns
- Voltage & current step-up/step-down
- Deterministic JSON, no upstream latency
Starter
€9.00 /month
- 25,000 calls / month
- 5 requests / second
- Hard cap (429 above quota, no overage)
- Full turns-ratio relations (V, I, N)
- Reflected impedance Zp = a^2 * Zs
- Impedance-matching ratio solver
- Email support
Pro
€24.00 /month
- 150,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- High-volume batch transformer calcs
- Impedance matching + reflected load
- Step-up / step-down design helpers
- 99.9% uptime SLA
Mega
€75.00 /month
- 768,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- Bulk EE design pipelines
- Unmetered impedance-matching solver
- Priority engineering support
- Dedicated throughput headroom
Built by
Related APIs
Other APIs with overlapping tags.
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
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Transformer Ratio API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Transformer Ratio API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Transformer Ratio API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Transformer Ratio API cost?
Transformer Ratio API has a free tier with 100 calls / month. Paid plans start at €9.00 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Transformer Ratio API GDPR-compliant?
All requests to Transformer Ratio API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your 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())Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
📌 Pinned
🔒 Locked
·
·
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.