oanor
Iscriviti gratis
Mercata Prezzi Caratteristiche Accedi

API · /transistor-api

BJT Transistor API

salutare 4,994 Abbonati

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.

#transistor #bjt #biasing #electronics #amplifier #developer-tools
api.oanor.com/transistor-api
Ottieni una chiave API Prova nel parco giochi → Contatta provider

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

/api/transistor-api/openapi.json
/api/transistor-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
105 ms
Sondaggi del server · 24 ore su 24
Abbonati
4,994
attiva
Chiamate totali
8
ultimi 7 giorni
status Pagina di stato completa → · 12 sonde/24h

Prezzi

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

Free

Gratis

  • 2,580 chiamate/mese
  • 2 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 2,580 calls/month
  • 2 req/sec
  • Currents + bias + power
  • No credit card
Accedi per abbonarti

Starter

€8.00 /mese

  • 39,200 chiamate/mese
  • 6 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 39,200 llamadas/mes
  • 6 req/seg
  • Punto de operación, región, α
  • Soporte por correo electrónico
Accedi per abbonarti

Pro

€21.00 /mese

  • 253,000 chiamate/mese
  • 15 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 253,000 calls/month
  • 15 req/sec
  • Amplifier & embedded pipelines
  • Priority support
Accedi per abbonarti

Mega

€65.00 /mese

  • 1,640,000 chiamate/mese
  • 40 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 1,640,000 llamadas/mes
  • 40 req/seg
  • Escalabilidad de plataforma
  • SLA dedicado
Accedi per abbonarti

Costruito da

P
PremiumApi

Correlato APIs

Altro APIs con tag sovrapposti.

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

Butterworth Filter API

Butterworth-filter design maths as an API, computed locally and deterministically. The order endpoint computes the minimum filter order needed to meet a specification — from the passband edge frequency and its allowed ripple and the stopband edge frequency and its required attenuation it returns the exact and rounded-up order, n = ⌈log10((10^(As/10)−1)/(10^(Ap/10)−1)) / (2·log10(fs/fp))⌉, where each extra order adds 20 dB per decade of roll-off. The response endpoint computes the maximally-flat magnitude response of an n-th order Butterworth filter at a frequency, |H| = 1/√(1 + (f/fc)^(2n)), in linear and decibel form with the attenuation and the asymptotic roll-off — the response is exactly −3.01 dB at the cutoff for any order. The poles endpoint gives the s-plane pole locations, equally spaced on a circle of radius ωc in the left half-plane at angles π·(2k+n−1)/(2n), all stable. Frequencies are in hertz (or any consistent unit), 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, instrumentation and embedded app developers, anti-aliasing and filter-design tools, and signal-processing education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is the Butterworth filter; for a single-pole RC cutoff and resonance use a resonance API and for AC impedance an impedance API.

api.oanor.com/butterworth-api

Domande frequenti

Risposte rapide su prezzi, quote e integrazione.

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