Audio Extract API

Extracts the audio track from a video (or any container) and returns it in a chosen audio format.

Updated

Agents read this page asGET /v1/audio-extract/schemafree: schema, examples, errors, price

Endpoint
POST /v1/audio-extract
Price
$0.003 per call
Timeout
94 s
max_timeout_seconds
115 (the whole call as the 402 envelope sells it: the timeout, plus payment verification and settlement around it)
Response cap
200 MB (209,715,200 bytes)
Max duration
60 min (3,600 s) of inputLonger input is refused with too_large (413), and input whose duration cannot be measured with unprocessable (422). Both are decided before any encoding, so the call is never settled.

When to use it

Demuxing and re-encoding an audio track needs ffmpeg AND a hardened fetch: an agent that pulls the URL itself walks past every SSRF control, and carrying an ffmpeg per call is not something an agent does inline.

When not to use it

  • The input is over 200 MB (209,715,200 bytes) or longer than 60 min (3,600 s): audio-extract answers too_large (413).
  • The destination needs more than 94 s to answer: the call ends with upstream_timeout (424).
  • The destination is on a private or local network: the network guard refuses it with blocked_target (403).

Parameters

One JSON body. The schema is free at GET /v1/audio-extract/schema.

FieldTypeRequiredDescription
urlstringyesAbsolute http(s) URL of a video or audio file, up to 2048 characters, in a recognised container (MP4/MOV, Matroska/WebM, AVI, Ogg, WAV, FLAC, AIFF or MP3); the selected audio stream must last at most 3600 seconds.
streamintegernoZero-based index among the audio streams only (0 is the first audio track), 0 to 63; an index the file does not have is refused as unprocessable. Default: 0.
tostringnoOutput format for the extracted track: wav (16-bit PCM), mp3 (LAME), flac, aac (ADTS stream) or opus (in an Ogg container); defaults to mp3. One of: "wav", "mp3", "flac", "aac", "opus". Default: "mp3".

Limits

LimitValue
Size cap200 MB (209,715,200 bytes)
Longest input60 min (3,600 s)
Timeout94 s
Show the JSON Schema the handler validates against
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 2048,
      "format": "uri",
      "description": "Absolute http(s) URL of a video or audio file, up to 2048 characters, in a recognised container (MP4/MOV, Matroska/WebM, AVI, Ogg, WAV, FLAC, AIFF or MP3); the selected audio stream must last at most 3600 seconds."
    },
    "stream": {
      "default": 0,
      "description": "Zero-based index among the audio streams only (0 is the first audio track), 0 to 63; an index the file does not have is refused as unprocessable.",
      "type": "integer",
      "minimum": 0,
      "maximum": 63
    },
    "to": {
      "default": "mp3",
      "description": "Output format for the extracted track: wav (16-bit PCM), mp3 (LAME), flac, aac (ADTS stream) or opus (in an Ogg container); defaults to mp3.",
      "type": "string",
      "enum": [
        "wav",
        "mp3",
        "flac",
        "aac",
        "opus"
      ]
    }
  },
  "required": [
    "url"
  ],
  "additionalProperties": false
}

Example

The published example, verbatim: the request and the response it returns.

Request
POST /v1/audio-extract
content-type: application/json
payment-signature: <base64 x402 payload>

{
  "url": "https://grist.tools/samples/av/probe-clip.mov",
  "stream": 0,
  "to": "wav"
}

Without the payment-signature header the call answers 402 with the payment requirements, including this endpoint's price and its max_timeout_seconds, so the deadline is known before anything is paid. The payment is verified before the handler runs and settled only after it succeeds, so a call refused by the gate, or one that fails inside the handler, is never settled. The single case we cannot state for you is a settlement call that fails without answering: the error message says so when that is what happened.

Response200 OK
200 OK
payment-response: <base64 settlement receipt>

{
  "source_url": "https://grist.tools/samples/av/probe-clip.mov",
  "bytes": 33850,
  "container": "mp4",
  "stream_index": 0,
  "format": "wav",
  "audio_bytes": 32044,
  "audio_base64": "UklGRiR9AABXQVZFZm10IBAAAAABAAEAQB8AAIA+AAACABAAZGF0YQB9AAAA4ADo..."
}

Sample file: av/probe-clip.mov. Two-second QuickTime clip: 64x36 PNG video at 2 fps with a light square moving across a slate field, plus the three rising 500 Hz beeps of waveform-beeps.wav as mono 16-bit PCM at 8 kHz.

In the sample itself, the ftyp box names major brand qt, minor version 512 and compatible brands qt; the top-level boxes run ftyp, wide, mdat and moov, so the moov index comes after the media data; mvhd counts 2,000 ticks at 1,000 per second, 2 s; the 2 tracks are url with sample entry png and url with sample entry sowt. In the returned file: the RIFF header counts 32,036 bytes after itself, and the fmt chunk, in its own field order, declares audio format 1 (integer PCM), 1 channel, 8,000 Hz, 16,000 bytes per second, a block align of 2 bytes and 16 bits per sample. The data chunk right after it holds 32,000 bytes of samples, 2 s at that rate.

Response fields

FieldTypeIn the example
source_urlstring"https://grist.tools/samples/av/probe-clip.mov"
bytesnumber33850
containerstring"mp4"
stream_indexnumber0
formatstring"wav"
audio_bytesnumber32044
audio_base64stringa string of 67 characters

Deterministic: the same input returns the same output. Clock-derived fields, when present, are declared in the response.

Call it from code

The client reads the 402, signs the payment and retries on its own.

// audio-extract: $0.003 per call, paid in USD Coin on eip155:8453 via x402
// Install: npm install @x402/fetch@2 @x402/evm@2 viem@2
// Save as client.mjs (ES module, Node 18+), export EVM_PRIVATE_KEY with the paying wallet's key in your shell, then run: node client.mjs
// The wrapper reads the 402 (payment-required), signs and retries with payment-signature.
import { wrapFetchWithPayment, x402Client, decodePaymentResponseHeader } from '@x402/fetch'
import { ExactEvmScheme } from '@x402/evm/exact/client'
import { privateKeyToAccount } from 'viem/accounts'

const account = privateKeyToAccount(process.env.EVM_PRIVATE_KEY)
const client = new x402Client().register('eip155:8453', new ExactEvmScheme(account))
const fetchWithPayment = wrapFetchWithPayment(fetch, client)

const body = {
  "url": "https://grist.tools/samples/av/probe-clip.mov",
  "stream": 0,
  "to": "wav"
}

const res = await fetchWithPayment('https://grist.tools/v1/audio-extract', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify(body),
})
console.log(res.status, await res.json())
const settle = res.headers.get('payment-response')
if (settle) console.log(decodePaymentResponseHeader(settle).transaction)

Errors

Every error is typed JSON. Only a successful call is settled.

CodeHTTPWhen
invalid_input400The body does not match the schema on this page. Nothing is charged. The body does not match the schema; its fields are url, stream and to.
blocked_target403The destination is refused by the network guard: a disallowed address, or, for HTTP requests, a scheme other than http/https, a port other than 80/443, or credentials in the URL.
unreachable_target424The destination you named did not resolve or refused the connection.
upstream_timeout424The destination you named did not answer before the declared timeout for this endpoint expired.
unsupported_content_type415The destination returned a type this endpoint does not handle.
too_large413The response exceeded the size cap while streaming, or decompressed at more than the allowed ratio.
unprocessable422The bytes arrived but could not be processed, for instance a malformed document.
internal500Our fault, and in almost every case nothing is charged. The exceptions come after the call has run and the settlement call was made: the message "The work was done but settlement could not be completed", and the messages starting with "Payment settlement returned". There, whether the payment moved is unknown to us as well. The payment moves at most once: its nonce is single-use and settlement is idempotent, so a retry with it is never charged twice. A retry is normally refused with a 402: replay_consumed, an expiry reason, or a reason saying the nonce was already used once the transfer is on-chain. Only if our server restarted before the transfer was final can a retry run the call again. Even then, the payment moves at most once. To see whether it was settled, read the EIP-3009 authorizationState of its nonce on-chain; to call again, sign a new payment.
rate_limited429Too many calls from the same payer, or too many calls towards the same destination domain. Nothing is charged.
concurrency_limit,
registry_at_capacity,
upstream_unavailable
503We could not serve the call right now. Retryable: wait the number of seconds in the retry-after header, then repeat the call. concurrency_limit and registry_at_capacity mean we were at capacity: the call did not run. You can send the same payment again if its validBefore is still far enough away to cover another call. If it is not, the retry gets a 402 authorization_validity_too_short: sign a new payment. upstream_unavailable means our internal service failed or did not answer in time: the call may already have run and the payment may have been settled. A retry with the same payment can get a 402 whose error field says why. authorization_validity_too_short: too little time is left before validBefore to cover another call. This check comes before the replay check, so it does not tell whether the first payment was settled. replay_consumed (the payment was used and may have been settled) or replay_exhausted (too many attempts): sign a new payment. replay_in_flight: the first call is still running, so wait and do not pay again. invalid_exact_evm_nonce_already_used: the transfer is already on-chain, so this payment cannot move again. Sign a new payment. An authorization can be settled only once, since its nonce is single-use. To see whether it was settled, read the EIP-3009 authorizationState of its nonce on-chain.
misconfigured503The service is not configured to serve calls. The call did not run and nothing is charged. It needs a fix on our side, so there is no retry delay to wait for.

Input that is rejected before the tool runs (malformed JSON, schema mismatch, body over the size limit) is never charged.

Questions

How much does a call to the Audio Extract API cost?

$0.003 per call, paid in USD Coin on Base via x402. There is no account and no API key: the price is in the 402 answer, before anything is paid.

What is the timeout of audio-extract?

The endpoint itself runs for at most 94 s. max_timeout_seconds in the 402 answer is 115: that covers the whole call, including payment verification and settlement around it.

How large can a response from audio-extract be?

The response-size cap is 200 MB (209,715,200 bytes).

Is the audio-extract input schema free to read?

Yes. GET https://grist.tools/v1/audio-extract/schema returns the input schema for free, paid endpoints included.

How long can the input to audio-extract be?

At most 60 min (3,600 s). Longer input is refused with too_large (413), and input whose duration cannot be measured with unprocessable (422). Both are decided before any encoding, so the call is never settled.

What happens if a call to audio-extract fails?

The payment is verified before the handler runs and settled only after it succeeds, so a call refused by the gate, or one that fails inside the handler, is never settled. The single case that cannot be stated in advance is a settlement call that fails without answering: the error message says so when that is what happened.

What does audio-extract return?

A JSON object with 7 top-level fields: source_url, bytes, container, stream_index, format, audio_bytes and audio_base64. The example on this page is a real call over av/probe-clip.mov.