Quantization & ENOB
API · /adc-api
ADC & DAC Converter API
ADC/DAC data-converter maths as an API, computed locally and deterministically. The resolution endpoint turns a bit depth into the number of quantization levels (2^N), the LSB step for a given reference voltage (in V, mV and µV), the full-scale range, the ideal signal-to-noise ratio (6.02·N + 1.76 dB) and dynamic range, and — given an input voltage — the digital output code. The sampling endpoint covers Nyquist: the minimum sample rate for a signal bandwidth (2·f_max), the Nyquist frequency for a sample rate (fs/2), whether a signal is adequately sampled, and the alias frequency a tone folds to, |f_in − round(f_in/fs)·fs|. The quantization endpoint gives the maximum quantization error (LSB/2), the rms quantization noise (LSB/√12), the ideal SNR, and the effective number of bits (ENOB = (SNR − 1.76)/6.02) from a measured SNR. Everything is computed locally and deterministically, so it is instant and private. Ideal for embedded, DSP, audio and instrumentation app developers, data-acquisition and converter-selection tools, and electronics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is data-converter & sampling maths; for media bitrate and file size use a bitrate API and for AC reactance and resonance use a resonance API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 79 ms
- Server probes · 24h
- Subscribers
- 4,664
- 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)
- Bit depth to quantization levels
- Resolution and step-size maths
- Deterministic local compute
- 2 requests/sec
Starter
€9.00 /month
- 40,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- Full ADC/DAC converter endpoints
- SNR and dynamic-range maths
- Sampling-rate helpers
- Email support
Pro
€24.00 /month
- 250,000 calls / month
- 25 requests / second
- Hard cap (429 above quota, no overage)
- High-volume batch conversions
- Quantization-noise modelling
- Nyquist and aliasing checks
- Priority support
Mega
€75.00 /month
- 1,500,000 calls / month
- 80 requests / second
- Hard cap (429 above quota, no overage)
- Bulk DSP pipeline integration
- Highest throughput for CI/firmware
- Full converter-maths suite
- SLA-backed support
Built by
Related APIs
Other APIs with overlapping tags.
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
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
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for ADC & DAC Converter API?
What's the rate limit for ADC & DAC Converter API?
How much does ADC & DAC Converter API cost?
Can I cancel my subscription anytime?
Is ADC & DAC Converter 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/adc-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/adc-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/adc-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/adc-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.