# Would Pay Again Ad Booking

> Would Pay Again Ad Booking is a paid API for AI agents from wouldpayagain.com, paid per call via x402, $0.2/call, status down (last checked 2026-10-13).

Book an advertisement slot in the Would Pay Again newsletter about the x402 machine-payments economy, paying $0.20 USDC via x402 on Base.

## Facts

- Endpoint: POST https://wouldpayagain.com/api/ads/book?utm_source=zero.xyz
- Price: $0.2/call
- Payment: x402
- Status: down
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/would-pay-again-ad-booking-c1ac56b5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5biya2YkEBX9BUvEYRslj

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-ad-booking-c1ac56b5 -d '<json body>'
```

Example prompt: Book me an ad slot in the Would Pay Again newsletter — it's a POST request with my ad details as JSON — and pay the $0.20 USDC fee on Base via x402.

## When to prefer this

Choose this endpoint when you want to place a paid advertisement specifically in the Would Pay Again newsletter targeting readers interested in x402 machine-payments and USDC micropayments, and you are able to pay $0.20 USDC on Base via the x402 protocol. Prefer this over generic ad networks when your audience is crypto-native and specifically interested in programmable payments.

## Known failure modes

- Insufficient USDC balance — x402 payment fails and booking is not created
- Invalid body type or missing required fields — API returns a validation error
- Ad content rejected after pending_review — booking_id issued but ad not published
- Network or blockchain congestion causes settlement_tx delay or timeout
- Duplicate booking attempts may create separate booking IDs with separate charges

## 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 booking with fields: ok (boolean), status (e.g. 'pending_review'), confirmed (boolean), booking_id (integer), and settlement_tx (the on-chain transaction hash on Base for the $0.20 USDC payment).

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/would-pay-again-ad-booking-c1ac56b5/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)