Gain-bandwidth product
API · /opamp-api
Op-Amp Gain API
Operational-amplifier gain and bandwidth maths as an API, computed locally and deterministically. The gain endpoint computes the closed-loop gain of an inverting (Av = −Rf/Rin) or non-inverting (Av = 1 + Rf/Rin) amplifier from the feedback and input resistors, gives the gain in decibels (20·log₁₀|Av|) and the output voltage for an input, and solves the feedback resistor needed for a target gain. The summing endpoint computes the output of an inverting summing (adder) amplifier, Vout = −Rf·Σ(Vi/Ri), from any number of weighted inputs — the basis of analogue mixers and digital-to-analogue converters. The bandwidth endpoint applies the gain-bandwidth product, GBW = closed-loop gain × bandwidth, and solves any of the three (a 1 MHz op-amp at a gain of 10 has a 100 kHz bandwidth), and computes the full-power bandwidth from the slew rate and the peak output voltage, f = slew_rate/(2π·Vpeak). Everything is computed locally and deterministically, so it is instant and private. Ideal for analogue-electronics and circuit-design tools, amplifier, filter and sensor-conditioning design, audio and instrumentation apps, and electronics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is op-amp amplifier design; for Ohm's law, reactance and resonance use an Ohm's-law API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 80 ms
- Server probes · 24h
- Subscribers
- 3,113
- active
- Total calls
- 76
- 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)
- Inverting & non-inverting closed-loop gain
- Deterministic local compute, no upstream
- JSON responses, 2 req/s
- 2,000 calls/month
Starter
€8.00 /month
- 30,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- Gain + gain-bandwidth product maths
- Bandwidth & slew-rate estimates
- 6 req/s burst
- 30,000 calls/month
Pro
€22.00 /month
- 150,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- Full gain & bandwidth endpoint suite
- dB and linear gain output
- Batch resistor-ratio solving
- 150,000 calls/month, 20 req/s
Mega
€69.00 /month
- 750,000 calls / month
- 60 requests / second
- Hard cap (429 above quota, no overage)
- Unlimited endpoint access
- High-throughput 60 req/s
- Priority compute lane
- 750,000 calls/month for bench/EDA integrations
Built by
Related APIs
Other APIs with overlapping tags.
BJT Transistor API
Bipolar-junction-transistor (BJT) circuit maths as an API, computed locally and deterministically. The currents endpoint relates the three terminal currents through the DC current gain β (hFE): the collector current Ic = β·Ib, the emitter current Ie = (β+1)·Ib and the common-base gain α = β/(β+1) ≈ 1, from β and any one current. The bias endpoint analyses the operating point of the classic voltage-divider bias network — from the supply voltage, the two divider resistors, the collector and emitter resistors, β and the base-emitter drop it computes the Thévenin equivalent (Vth = Vcc·R2/(R1+R2), Rth = R1‖R2), the base current Ib = (Vth − Vbe)/(Rth + (β+1)·Re), the collector and emitter currents, the collector-emitter voltage Vce and the node voltages, and classifies the operating region as cutoff, active or saturation. The power endpoint computes the transistor's power dissipation, Pd ≈ Vce·Ic (plus Vbe·Ib), to check it against the rated maximum. Currents are in amperes, resistances in ohms and voltages in volts, with Vbe defaulting to 0.7 V for silicon. Everything is computed locally and deterministically, so it is instant and private. Ideal for electronics, amplifier-design, embedded and hobbyist app developers, biasing and operating-point tools, and electronics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is BJT biasing; for op-amp circuits use an op-amp API and for an LED series resistor an LED-resistor API.
api.oanor.com/transistor-api
Newegg API
Live product search from Newegg.com, the major electronics & tech retailer. Search any keyword — laptop, rtx 4070, ssd — and get the product listings with title, brand, model, current price, original price, image, rating, review count, in-stock status, seller and the Newegg product URL. Prices are live USD. Ideal for shopping, price-comparison, deal-tracking and e-commerce dashboards.
api.oanor.com/newegg-api
RTD Pt100 Sensor API
RTD (resistance-temperature-detector) sensor maths as an API, computed locally and deterministically with the IEC 60751 Callendar–Van Dusen equation — the resistance, temperature and tolerance numbers an instrumentation or controls engineer reads a Pt100 or Pt1000 with. The resistance endpoint gives the sensor resistance from temperature: above 0 °C, R = R₀·(1 + A·T + B·T²) with A = 3.9083×10⁻³ and B = −5.775×10⁻⁷; below 0 °C a third term adds C·(T−100)·T³ — a standard Pt100 (100 Ω at 0 °C) reads 138.51 Ω at 100 °C and 80.31 Ω at −50 °C, and a Pt1000 is ten times that. The temperature endpoint inverts it to turn a measured resistance back into temperature — analytically above 0 °C, iteratively below — exactly what a transmitter does with the bridge reading, and a reminder that a 3- or 4-wire connection cancels the lead-wire resistance so it does not read as extra degrees. The tolerance endpoint gives the IEC 60751 accuracy band in both °C and Ω by class — AA ±(0.10 + 0.0017·|T|), A ±(0.15 + 0.002·|T|), B ±(0.30 + 0.005·|T|), C ±(0.60 + 0.010·|T|) — the error growing with distance from 0 °C. Everything is computed locally and deterministically, so it is instant and private. Ideal for instrumentation and controls software, data-logger and transmitter firmware, calibration and industrial-IoT tools. Pure local computation — no key, no third-party service, instant. 3 compute endpoints. For NTC thermistors use a thermistor API; for thermocouples a thermocouple API.
api.oanor.com/rtd-api
Voltage Divider API
Resistive voltage-divider circuit design as an API, computed locally and deterministically. The divide endpoint takes an input voltage and two resistors and returns the output voltage Vout = Vin·R2/(R1+R2), the current I = Vin/(R1+R2) that flows through the chain, and the power dissipated in each resistor and in total — a 12 V source with R1 = 1 kΩ and R2 = 2 kΩ gives 8 V at 4 mA. The loaded endpoint adds a load resistor across R2, computes the parallel combination R2′ = R2·RL/(R2+RL) and the loaded output Vout = Vin·R2′/(R1+R2′), and reports the droop in volts and percent against the unloaded value, the classic mistake when a divider feeds a real load. The resistor endpoint sizes the missing resistor for a target output — R2 = R1·Vout/(Vin−Vout) or R1 = R2·(Vin−Vout)/Vout — so you can pick parts for a reference or sensor-bias point. All quantities are volts, ohms, amps and watts. Everything is computed locally and deterministically, so it is instant and private. Ideal for electronics, embedded, hardware, sensor-interfacing and EE-education app developers, reference-voltage and bias-network tools, and maker software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is the resistive divider; for a single Ohm’s-law relationship use an Ohm’s-law API and for RC/RL filters an RC-filter API.
api.oanor.com/voltagedivider-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Op-Amp Gain API?
What's the rate limit for Op-Amp Gain API?
How much does Op-Amp Gain API cost?
Can I cancel my subscription anytime?
Is Op-Amp Gain API GDPR-compliant?
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/opamp-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/opamp-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/opamp-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/opamp-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
·
-
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.