Serper (Google SERP) via Spawnpay

Google search results through Serper, behind Spawnpay billing.

Why route through Spawnpay

When the answer must come from Google. Spawnpay receipts close the loop on per-query cost recovery for your own customers.

Endpoint

curl

curl -X POST https://spawnpay.ai/api/proxy \
  -H 'Authorization: Bearer spk_live_…' \
  -H 'X-Provider-Key: $SERPER_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
  "provider": "serper",
  "path": "/search",
  "method": "POST",
  "body": {
    "q": "spawnpay"
  }
}'

Node (spawnpay-paywall)

import { proxy } from 'spawnpay-paywall';

const out = await proxy({
  "provider": "serper",
  "path": "/search",
  "method": "POST",
  "body": {
    "q": "spawnpay"
  },
  "providerKey": process.env.SERPER_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.