AssemblyAI via Spawnpay

Speech-to-text + diarisation behind one Spawnpay key — pipeline audio without juggling another billing relationship.

Why route through Spawnpay

Transcription agents that batch-process podcasts or meetings and need to bill the requester. Live caption tools with a shared budget.

Endpoint

curl

curl -X POST https://spawnpay.ai/api/proxy \
  -H 'Authorization: Bearer spk_live_…' \
  -H 'X-Provider-Key: $ASSEMBLYAI_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
  "provider": "assemblyai",
  "path": "/v2/transcript",
  "method": "POST",
  "body": {
    "audio_url": "https://example.com/audio.mp3"
  }
}'

Node (spawnpay-paywall)

import { proxy } from 'spawnpay-paywall';

const out = await proxy({
  "provider": "assemblyai",
  "path": "/v2/transcript",
  "method": "POST",
  "body": {
    "audio_url": "https://example.com/audio.mp3"
  },
  "providerKey": process.env.ASSEMBLYAI_KEY
});

console.log(out.status, out.body);
console.log('charged', out.charged); // txHash + $0.001 USDC receipt

What you get back

The full upstream JSON body, the upstream status code, the upstream response headers, plus a charged field with the USDC receipt (tx hash) when the call succeeded.