Lufs Math
by Audio Calc in Other
Loudness maths: gain to a LUFS target or platform, resulting true peak vs ceiling, or combining segment loudness.
https://audio-calc.x402tookit.com/lufs-math- Price
- $0.02
- per call in USDC
- Uptime
- 52.9%
- last 30 days
- Response time
- 516 ms
- 571 ms slowest 5%
- Last check
- Failed
- 25 h ago, next in 58 min
Reliability
Latest check failed 25 h ago: Expected HTTP 402, got 530
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://audio-calc.x402tookit.com/lufs-math
Each call costs $0.02 in USDC on Polygon, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://audio-calc.x402tookit.com/lufs-math?ceilingDbtp=-1&lufs=-9.5&target=spotify&truePeakDbtp=-0.3Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
ceilingDbtp | number | No | True-peak ceiling in dBTP (default -1) |
lufs | number | No | Measured integrated loudness in LUFS (negative), for example -9.5 |
segments | string | No | To combine: lufs:seconds pairs, for example -20:30,-10:30 |
target | string | No | Target LUFS or a name: spotify, youtube, apple-music, amazon-music, tidal, podcast, ebu-r128, atsc-a85, arib-tr-b32 |
truePeakDbtp | number | No | Measured true peak in dBTP, to predict the peak after the gain |
Example response
The provider's example. We can't check it without paying.
Example response, 43 lines
{
"asOf": "2026-10-11T14:38:34.877Z",
"ceilingDbtp": -1,
"combinedLufs": null,
"degraded": false,
"disclaimer": "Screening signal computed from the named public source. Not financial, legal or investment advice; provided as is. Verify at the source before acting.",
"gainDb": -4.5,
"gainLinear": 0.595662,
"limitingNeeded": false,
"loudestSegmentLufs": null,
"measuredLufs": -9.5,
"mode": "gain",
"newTruePeakDbtp": -4.8,
"notChecked": [
"BS.1770 gating (absolute -70 LUFS and relative -10 LU): combining segments here averages ALL energy ungated, so measure a whole programme with a meter for a delivery value",
"loudness range and short-term or momentary limits (for example the EBU R128 +-0.5 LU tolerance)",
"…2 more"
],
"peakHeadroomDb": 3.8,
"platform": "spotify",
"platformTargets": {
"amazon-music": -14,
"apple-music": -16,
"arib-tr-b32": -24,
"atsc-a85": -24,
"ebu-r128": -23,
"podcast": -16,
"spotify": -14,
"tidal": -14,
"youtube": -14
},
"quietestSegmentLufs": null,
"reasons": [
"Loudness changes dB for dB with gain, so the gain is simply target minus measured.",
"Turning down never raises the peak."
],
"segmentCount": null,
"source": "ITU-R BS.1770 / EBU R128 loudness arithmetic (level offsets add in dB; energies average linearly); platform targets as commonly published, computed locally",
"summary": "-9.5 LUFS to -14 LUFS (spotify): -4.5 dB. True peak -0.3 becomes -4.8 dBTP, 3.8 dB under the -1 dBTP ceiling.",
"targetLufs": -14,
"totalSeconds": null,
"verdict": "TURN_DOWN"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.02.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://audio-calc.x402tookit.com/lufs-math?ceilingDbtp=-1&lufs=-9.5&target=spotify&truePeakDbtp=-0.3'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://audio-calc.x402tookit.com/lufs-math?ceilingDbtp=-1&lufs=-9.5&target=spotify&truePeakDbtp=-0.3' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Faudio-calc.x402tookit.com%2Flufs-math
const res = await pay("https://audio-calc.x402tookit.com/lufs-math?ceilingDbtp=-1&lufs=-9.5&target=spotify&truePeakDbtp=-0.3");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://audio-calc.x402tookit.com/lufs-math?ceilingDbtp=-1&lufs=-9.5&target=spotify&truePeakDbtp=-0.3")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 25 h ago | Expected HTTP 402, got 530 | 530 | 103 ms | - |
| 37 h ago | Expected HTTP 402, got 530 | 530 | 128 ms | - |
| 2 days ago | Expected HTTP 402, got 530 | 530 | 98 ms | - |
| 3 days ago | Passed | 402 | 571 ms | $0.02 |
| 3 days ago | Expected HTTP 402, got 530 | 530 | 104 ms | - |
Show 10 older checks
| 3 days ago | Passed | 402 | 551 ms | $0.02 |
| 5 days ago | Expected HTTP 402, got 530 | 530 | 98 ms | - |
| 5 days ago | Expected HTTP 402, got 530 | 530 | 110 ms | - |
| 5 days ago | Expected HTTP 402, got 530 | 530 | 169 ms | - |
| 5 days ago | Expected HTTP 402, got 530 | 530 | 266 ms | - |
| 5 days ago | Passed | 402 | 252 ms | $0.02 |
| 5 days ago | Passed | 402 | 516 ms | $0.02 |
| 6 days ago | Passed | 402 | 550 ms | $0.02 |
| 6 days ago | Passed | 402 | 555 ms | $0.02 |
| 6 days ago | Passed | 402 | 504 ms | $0.02 |