# Beggar Bot Receipt Verification (Base Mainnet)

> Beggar Bot Receipt Verification (Base Mainnet) is a paid API for AI agents from beggar-bot-demand.beggarbot.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-29).

Verifies a USDC payment receipt on Base mainnet by confirming a specific on-chain transaction matches the expected payee, payer, and amount.

## Facts

- Endpoint: POST https://beggar-bot-demand.beggarbot.workers.dev/v1/receipt?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/beggar-bot-receipt-verification-base-mainnet-e89b8f64
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__v75C95u8cMIGsf94bcxb

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 beggar-bot-receipt-verification-base-mainnet-e89b8f64 -d '<json body>'
```

Example prompt: Can you verify that transaction 0xabc123...def on Base mainnet was a USDC payment of 5.00 from wallet 0xPayer... to wallet 0xPayee...?

## When to prefer this

Use this endpoint when you need to cryptographically verify a specific USDC transaction on Base mainnet or Base Sepolia — particularly when confirming that a payment from a known payer reached a known payee for a specific amount. Prefer this over generic block explorer lookups when you need structured, machine-readable receipt validation with optional invoice matching.

## Known failure modes

- Invalid or malformed tx_hash returns an error
- Transaction not found on the specified network
- Mismatch between on-chain data and provided payee/payer/amount details
- Payment of $0.01 USDC required via x402 protocol before the response is returned; missing payment returns 402
- Unsupported network value other than 'base' or 'base-sepolia'
- Invalid Ethereum address format for payee or payer fields

## How this service works

Paid: /v1/verify, /v1/risk, /v1/receipt cost $0.01 USDC per call on Base mainnet via x402 (payTo 0x719227f384b66BFEF00093D6d8d32fA9dC2B40e7); utilities analyze Base mainnet (USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) by default, network=base-sepolia optional; /v1/receipt/verify and discovery files are free. Operator: Beggar Bot.

## Output

A JSON response indicating whether the on-chain transaction matches the provided payee, payer, amount, and optional invoice/resource fields — including transaction status, matched payment details, and any discrepancies found.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "payee": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$",
   "description": "payee"
  },
  "payer": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$",
   "description": "payer"
  },
  "amount": {
   "type": "string",
   "description": "USDC decimal amount"
  },
  "invoice": {
   "type": "string",
   "description": "optional invoice id"
  },
  "network": {
   "enum": [
    "base",
    "base-sepolia"
   ],
   "type": "string",
   "description": "base (default) or base-sepolia"
  },
  "tx_hash": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{64}$",
   "description": "0x tx hash"
  },
  "resource": {
   "type": "string",
   "description": "optional resource"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/beggar-bot-receipt-verification-base-mainnet-e89b8f64/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from beggar-bot-demand.beggarbot.workers.dev](https://www.zero.xyz/host/beggar-bot-demand.beggarbot.workers.dev/llms.txt)