# Beggar Bot Agent Utilities – /v1/whvaa (Base Mainnet)

> Beggar Bot Agent Utilities – /v1/whvaa (Base Mainnet) is a paid API for AI agents from beggar-bot-demand.beggarbot.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-11-04).

A paid utility endpoint on Beggar Bot's Base mainnet service, accessible via x402 micropayment, returning JSON for unspecified agent utility purposes at the /v1/whvaa path.

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/whvaa?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/beggar-bot-agent-utilities-v1-whvaa-base-mainnet-2cb1a214
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kfQLlp6bDQyhBpEYLp5Ii

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-agent-utilities-v1-whvaa-base-mainnet-2cb1a214
```

Example prompt: Can you call the Beggar Bot /v1/whvaa utility on Base mainnet and get the JSON result back for me? I'll authorize the $0.02 USDC x402 payment to cover the call.

## When to prefer this

Choose this endpoint when you specifically need the /v1/whvaa utility offered by Beggar Bot on Base mainnet and are equipped to handle x402 USDC micropayments programmatically. It is distinct from the other Beggar Bot utilities (/v1/verify, /v1/risk, /v1/receipt) and should only be used when this specific path is required. Prefer it in agent workflows that already handle x402 payment flows on Base mainnet.

## Known failure modes

- Insufficient USDC balance for $0.02 micropayment — payment rejected
- Invalid or missing x402 payment header — 402 Payment Required response
- Incorrect properties parameter format — malformed request error
- Cloudflare Worker downtime — 503 or timeout
- Wrong network specified — Base Sepolia vs Base mainnet mismatch
- Endpoint path /v1/whvaa not recognized — 404 Not Found

## 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 object returned by the /v1/whvaa endpoint after a successful $0.02 USDC x402 micropayment on Base mainnet. The exact structure of the response is not specified in the metadata, but it reflects a utility operation performed by Beggar Bot's Cloudflare Worker infrastructure.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/beggar-bot-agent-utilities-v1-whvaa-base-mainnet-2cb1a214/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)