# Would Pay Again Sponsorship Request

> Would Pay Again Sponsorship Request is a paid API for AI agents from wouldpayagain.com, paid per call via x402, $25/call, status unknown (last checked 2026-10-12).

Submits a sponsorship request for the Would Pay Again newsletter, paying $25 USDC on Base via x402 machine payments.

## Facts

- Endpoint: POST https://wouldpayagain.com/api/sponsor/request?utm_source=zero.xyz
- Price: $25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/would-pay-again-sponsorship-request-f5cda900
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8Ppei3NZ_ZfTzf4mS4Z2W

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability would-pay-again-sponsorship-request-f5cda900 -d '<json body>'
```

Example prompt: Submit a sponsorship request to the Would Pay Again newsletter — the one all about x402 machine payments — and pay the $25 USDC fee on Base.

## When to prefer this

Choose this endpoint when you want to purchase a sponsorship placement in the Would Pay Again newsletter and can pay $25 USDC on Base via the x402 protocol. It is ideal for agents or builders in the machine-payments ecosystem who want programmatic, crypto-native ad placement without a traditional invoicing process.

## Known failure modes

- Insufficient USDC balance on Base — payment rejected
- Invalid or missing x402 payment header — request fails
- Network congestion causing settlement delay or timeout
- Duplicate request submission resulting in unexpected behavior
- Smart contract or facilitator error on the Base network

## How this service works

A newsletter about the x402 machine-payments economy, sold over x402 itself. USDC on Base.

## Output

Returns a JSON object confirming the sponsorship request was received and payment settled, including an ok boolean, status string (paid_confirmed), confirmed flag, a numeric request_id, and the on-chain settlement transaction hash (settlement_tx starting with 0x).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {}
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "status": "paid_confirmed",
  "confirmed": true,
  "request_id": 1,
  "settlement_tx": "0x…"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/would-pay-again-sponsorship-request-f5cda900/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from wouldpayagain.com](https://www.zero.xyz/host/wouldpayagain.com/llms.txt)