ElevenLabs via Spawnpay

Realistic text-to-speech voices through Spawnpay — every render gets a USDC receipt + cross-provider budget.

Why route through Spawnpay

Voice-agent products that bill end-users per minute of synthesised audio. Multi-tenant tools that want a single budget across LLM + TTS.

Endpoint

curl

curl -X POST https://spawnpay.ai/api/proxy \
  -H 'Authorization: Bearer spk_live_…' \
  -H 'X-Provider-Key: $ELEVENLABS_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
  "provider": "elevenlabs",
  "path": "/v1/text-to-speech/21m00Tcm4TlvDq8ikWAM",
  "method": "POST",
  "body": {
    "text": "hello from spawnpay",
    "model_id": "eleven_turbo_v2_5"
  }
}'

Node (spawnpay-paywall)

import { proxy } from 'spawnpay-paywall';

const out = await proxy({
  "provider": "elevenlabs",
  "path": "/v1/text-to-speech/21m00Tcm4TlvDq8ikWAM",
  "method": "POST",
  "body": {
    "text": "hello from spawnpay",
    "model_id": "eleven_turbo_v2_5"
  },
  "providerKey": process.env.ELEVENLABS_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.