81trust / 100

Audio Normalize

by Sift Web Tools in News & content

x402 APIPassing, checked 3 h ago

Normalise audio loudness to a broadcast or streaming target, file returned. Linear two-pass EBU R 128 loudness normalisation to a named target (ebu_r128, atsc_a85, ebu_r128_short, podcast, spotify, youtube, apple_music, amazon_music, deezer, aes_streaming, audiobook_acx) or custom lufs/true_peak. Returns the corrected file (wav, wav16, flac, mp3, m4a, opus) with before/after figures in X-Loudness-Report.

GET
https://sift.srv1996466.hstgr.cloud/v1/audio/normalize
Price
$0.02
per call in USDC
Uptime
96.2%
last 30 days
Response time
156 ms
414 ms slowest 5%
Last check
Passed
3 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://sift.srv1996466.hstgr.cloud/v1/audio/normalize

Each call costs $0.02 in USDC on Base, 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://sift.srv1996466.hstgr.cloud/v1/audio/normalize?url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Ftone.mp3

Parameters

ParameterTypeRequiredDescription
formatstringNowav, wav16, flac, mp3, m4a or opus (default mp3)
lufsnumberNoCustom integrated loudness, -40 to -5
targetstringNoNamed target (default podcast)
true_peaknumberNoCustom true peak dBTP, -9 to 0
urlstringYesAudio file URL

Example response

The listing has no example response.

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://sift.srv1996466.hstgr.cloud/v1/audio/normalize?url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Ftone.mp3'

# 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://sift.srv1996466.hstgr.cloud/v1/audio/normalize?url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Ftone.mp3' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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%2Fsift.srv1996466.hstgr.cloud%2Fv1%2Faudio%2Fnormalize
const res = await pay("https://sift.srv1996466.hstgr.cloud/v1/audio/normalize?url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Ftone.mp3");
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://sift.srv1996466.hstgr.cloud/v1/audio/normalize?url=https%3A%2F%2Fsift.srv1996466.hstgr.cloud%2Fsamples%2Ftone.mp3")
    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

WhenResultHTTPTimePrice
3 h agoPassed402156 ms$0.02
7 h agoPassed402164 ms$0.02
12 h agoPassed40245 ms$0.02
16 h agoPassed402137 ms$0.02
21 h agoPassed402186 ms$0.02
Show 10 older checks
25 h agoPassed402173 ms$0.02
29 h agoPassed402144 ms$0.02
33 h agoPassed402414 ms$0.02
37 h agoPassed402105 ms$0.02
41 h agoPassed402326 ms$0.02
45 h agoPassed402184 ms$0.02
2 days agoPassed40252 ms$0.02
2 days agoExpected HTTP 402, got 404404207 ms-
2 days agoPassed40290 ms$0.02
3 days agoPassed402153 ms$0.02