Sound absorption vs frequency
API · /sonar-api
Sonar & Underwater Sound API
Underwater-sound and sonar maths as an API, computed locally and deterministically — the speed, absorption and ranging numbers a marine engineer, sonar developer or oceanographer works with. The sound-speed endpoint gives the speed of sound in seawater from the Mackenzie nine-term equation: about 1,500 m/s — far faster than in air — rising with temperature, salinity and depth, so a profile of 25 °C, 35 ppt at 1,000 m gives 1,550.7 m/s. Because the speed varies with depth, sound rays bend and form the SOFAR channel that carries whale song and signals across whole oceans. The absorption endpoint gives Thorp's sound-absorption coefficient in dB per km against frequency, with the loss over a path: seawater swallows high frequencies fast, which is why long-range sonar and whale calls are low-pitched while high-frequency sonar gives sharp images only at short range. The echo-range endpoint turns an echo sounder's or sonar's two-way travel time into the range or depth — distance = sound speed × time ÷ 2 — so a one-second round trip at 1,500 m/s is a target 750 m away, its accuracy resting on the assumed sound speed. Everything is computed locally and deterministically, so it is instant and private. Ideal for sonar and hydrophone tools, marine-survey and bathymetry apps, ocean-acoustics research, and AUV/ROV navigation utilities. Pure local computation — no key, no third-party service, instant. Standard-equation estimates over their valid ranges. 3 compute endpoints. For the speed of sound in air and Mach use a Mach-number API; for decibels a sound-level API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 81 ms
- Server probes · 24h
- Subscribers
- 4,681
- active
- Total calls
- 76
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 4,300 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 4,300 calls/month
- 2 req/sec
- Sound speed + absorption + echo range
- No credit card
Starter
€13.10 /month
- 46,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 46,000 calls/month
- 6 req/sec
- Mackenzie & Thorp models
- Email support
Pro
€40.20 /month
- 208,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 208,000 calls/month
- 15 req/sec
- Sonar, survey & bathymetry pipelines
- Priority support
Mega
€126.00 /month
- 1,100,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,100,000 calls/month
- 40 req/sec
- Fleet & research scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Cross-Asset Drawdown & Recovery Monitor API
How far every major market is below its peak and how long it has been underwater, computed live from Yahoo Finance (no key, nothing stored). Drawdown is the risk investors actually feel: not volatility in the abstract, but the gap between today's price and the high-water mark, and the painful stretch spent climbing back. For every asset — equity indices, bonds, gold, oil, commodities, FX and crypto — this measures the current drawdown from its rolling peak, the worst (maximum) drawdown over the window, the date and level of the peak, how many days it has been underwater, and how much of the fall it has already recovered. The monitor endpoint returns the whole universe ranked by current drawdown — what is deepest underwater and what is back at new highs — with a summary of how many markets are in drawdown. The asset endpoint returns one market's drawdown card. The universe endpoint lists what is covered. The cross-asset drawdown / underwater-recovery cut — distinct from the FX-only drawdown API, the crypto all-time-high API and the cross-asset volatility API (which ranks risk-adjusted return, not the underwater curve). It answers how far from the highs, and how long.
api.oanor.com/assetdrawdown-api
Soundproofing API
Building-acoustics soundproofing maths as an API, computed locally and deterministically. The mass-law endpoint computes the sound-transmission loss of a single partition from its surface mass density and the frequency using the field-incidence mass law, TL = 20·log10(m·f) − 47 dB — transmission loss rises about 6 dB for every doubling of mass or of frequency — and also gives the normal-incidence value. The composite endpoint combines the transmission losses of several elements that make up one wall, such as a heavy wall with a window or a door, by area-weighting their transmission coefficients, TL = −10·log10(Σ(Ai·τi)/ΣAi) — which shows how the weakest element, like a small gap or a thin window, dominates and wrecks an otherwise good wall. The transmission endpoint computes the received sound level on the far side of a partition, the source level minus the transmission loss, with an optional room-to-room correction that adds 10·log10(partition area / receiving-room absorption). Surface density is in kg/m², frequency in Hz, levels and transmission losses in dB and areas in m². Everything is computed locally and deterministically, so it is instant and private. Ideal for architecture, building-acoustics, studio-design, HVAC-noise and construction app developers, partition and noise-control tools, and acoustics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is sound insulation; for room reverberation use a reverberation API and for sound pressure level a sound-level API.
api.oanor.com/soundproof-api
Helmholtz Resonator API
Helmholtz-resonator acoustics as an API, computed locally and deterministically. The frequency endpoint computes the resonant frequency of a Helmholtz resonator — a cavity with a neck, like a bottle or a ported speaker box — from the neck area (or diameter), the neck length and the cavity volume, f = (c/2π)·√(A/(V·L_eff)), adding the acoustic end correction (about 0.85·radius for a flanged end and 0.61·radius for a free end) so a short or open neck resonates lower than its physical length suggests. The design endpoint inverts the relation, V = A·c²/(L_eff·ω²), to give the cavity volume needed to tune a resonator or a muffler chamber to a target frequency. The port-tuning endpoint sizes a bass-reflex (vented loudspeaker) box port in practical audio units — from the box volume in litres and the port diameter in centimetres it gives the tuning frequency for a given port length, or the port length required for a target tuning frequency, using the 0.732·diameter end correction. Core endpoints use SI units; the speed of sound defaults to 343 m/s. Everything is computed locally and deterministically, so it is instant and private. Ideal for audio, loudspeaker-design, musical-instrument, muffler and acoustic-treatment app developers, bass-reflex and resonator tools, and acoustics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is Helmholtz resonance; for room reverberation use a reverberation API and for standing waves on strings and in pipes a standing-wave API.
api.oanor.com/helmholtz-api
Reverberation Time API
Room-acoustics reverberation-time maths as an API, computed locally and deterministically. The sabine endpoint computes the reverberation time of a room — the RT60, the time for the sound to decay by 60 dB — from the Sabine formula RT60 = 0.161·V/A, where V is the room volume and A the total absorption in metric sabins; you can give the absorption directly, or as a surface area times an average absorption coefficient, and it also solves the absorption you would need to hit a target reverberation time. The eyring endpoint uses the Eyring-Norris formula RT60 = 0.161·V/(−S·ln(1−ᾱ)), which is more accurate than Sabine for absorbent rooms with a high average coefficient, and reports both for comparison. The absorption endpoint builds the absorption budget from a list of surfaces, each with its area and absorption coefficient, returning the total and average absorption and the resulting Sabine RT60, plus the extra absorption needed to reach a target. Everything is computed locally and deterministically, so it is instant and private. Ideal for acoustic-design, studio, classroom and home-theatre tools, room-treatment planning and building-acoustics apps, and audio-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is room reverberation time; for decibel conversion and combining sound levels use a sound-level API.
api.oanor.com/reverb-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Sonar & Underwater Sound API?
What's the rate limit for Sonar & Underwater Sound API?
How much does Sonar & Underwater Sound API cost?
Can I cancel my subscription anytime?
Is Sonar & Underwater Sound 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/sonar-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/sonar-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/sonar-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/sonar-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.