Voyage AI via Spawnpay

Best-in-class embeddings (voyage-3-large, voyage-multimodal) — meter per-call through Spawnpay with the rest of your stack.

Why route through Spawnpay

Production RAG pipelines that need an embeddings provider separate from the LLM. Multi-tenant SaaS that re-bills the embedding cost.

Endpoint

curl

curl -X POST https://spawnpay.ai/api/proxy \
  -H 'Authorization: Bearer spk_live_…' \
  -H 'X-Provider-Key: $VOYAGE_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
  "provider": "voyage",
  "path": "/v1/embeddings",
  "method": "POST",
  "body": {
    "model": "voyage-3-large",
    "input": [
      "agent native payments"
    ]
  }
}'

Node (spawnpay-paywall)

import { proxy } from 'spawnpay-paywall';

const out = await proxy({
  "provider": "voyage",
  "path": "/v1/embeddings",
  "method": "POST",
  "body": {
    "model": "voyage-3-large",
    "input": [
      "agent native payments"
    ]
  },
  "providerKey": process.env.VOYAGE_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.