API · /opamp-api

Op-Amp Gain API

healthy 3,113 Subscribers

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.

#op-amp #amplifier #gain #analog-electronics #electronics #developer-tools

api.oanor.com/opamp-api

Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/opamp-api/openapi.json

/api/opamp-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy

Uptime: 100.00%; Server probes · 24h
Avg latency: 88 ms; Server probes · 24h
Subscribers: 3,113; active
Total calls: 32; last 7 days

Full status page → · 24 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

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

PremiumApi

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

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

RC Filter API

First-order RC and RL passive-filter design as an API, computed locally and deterministically. The lowpass and highpass endpoints take a resistor and capacitor (RC) or a resistor and inductor (RL) and return the −3 dB cutoff frequency (fc = 1/(2πRC) for RC, R/(2πL) for RL), the time constant (τ = RC or L/R) and the angular cutoff; pass a frequency as well and they add the magnitude response as a linear gain and in decibels and the phase shift in degrees — a 1 kΩ / 1 µF low-pass has fc ≈ 159.15 Hz, and right at the cutoff the gain is −3.01 dB with −45° phase for a low-pass or +45° for a high-pass. The component endpoint solves the missing one of fc, R and C from the other two (fc = 1/(2πRC)), so you can size a resistor or capacitor for a target cutoff. All quantities are SI: ohms, farads, henries and hertz. Everything is computed locally and deterministically, so it is instant and private. Ideal for electronics, audio, embedded, signal-processing and EE-education app developers, filter-design and circuit-sizing tools, and maker software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is first-order single-pole filter design; for full RLC impedance and resonance use an impedance API and for stored capacitor energy a capacitor API.

api.oanor.com/rcfilter-api

Chebyshev Filter API

Chebyshev Type I filter-design maths as an API, computed locally and deterministically. The order endpoint computes the minimum filter order to meet a specification, n = ⌈acosh(√((10^(As/10)−1)/(10^(Ap/10)−1))) / acosh(fs/fp)⌉, from the passband edge frequency and its ripple and the stopband edge and its required attenuation — a Chebyshev filter usually needs a lower order than a Butterworth for the same specification, trading a flat passband for equiripple. The response endpoint computes the equiripple magnitude response, |H| = 1/√(1 + ε²·Tₙ²(f/fc)) with the ripple factor ε = √(10^(Ap/10) − 1) and the Chebyshev polynomial Tₙ, in linear and decibel form — in the passband the magnitude ripples between 0 and −Ap dB and reaches exactly −Ap dB at the cutoff, then rolls off faster than a Butterworth. The ripple endpoint converts between the passband ripple in decibels and the ripple factor ε, with the passband maximum and minimum. Frequencies are in hertz, ripple and attenuation in decibels and the order a positive integer. Everything is computed locally and deterministically, so it is instant and private. Ideal for DSP, audio, RF, communications and instrumentation app developers, filter-design and selectivity tools, and signal-processing education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is the Chebyshev Type I filter; for the maximally-flat Butterworth use a Butterworth API.

api.oanor.com/chebyshev-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Op-Amp Gain API?

Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Op-Amp Gain API with the x-oanor-key header. No credit card needed for the free tier.

What's the rate limit for Op-Amp Gain 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 Op-Amp Gain API cost?

Op-Amp Gain API has a free tier with 100 calls / month. Paid plans start at €8.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 Op-Amp Gain API GDPR-compliant?

All requests to Op-Amp Gain 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.

Op-Amp 3

Meta 1

Pick an endpoint from the list on the left to see its details and try it.

GET /v1/bandwidth

Gain-bandwidth product

Playground

Parameters

Custom headers

Language: Client:

GET /v1/gain

Inverting / non-inverting gain

Playground

Parameters

Custom headers

Language: Client:

GET /v1/summing

Summing amplifier

Playground

Parameters

Custom headers

Language: Client:

GET /v1/meta

Spec

Playground

Custom headers

Language: Client:

Code snippets

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

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

New thread

📌 Pinned 🔒 Locked

· ·

🔒 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.

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.

Pick a key

Plaintext is shown once at creation — use the prefix as a reminder.

Op-Amp Gain API

API health

Pricing

Built by

Related APIs

BJT Transistor API

Voltage Divider API

RC Filter API

Chebyshev Filter API

Frequently asked questions

Parameters

Parameters

Parameters

Code snippets

Ratings

Discussion

New thread

📌 🔒

Support

Open new ticket

Your cookie choices