# Beggar Bot L2 Withdraw Utility (Base Mainnet)

> Beggar Bot L2 Withdraw Utility (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).

Retrieves information about L2 withdrawal transactions on Base mainnet, returning structured data about the withdraw operation.

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/l2withdraw?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-l2-withdraw-utility-base-mainnet-31df38b7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3Pt1Ha0El-KRoTZB092tL

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-l2-withdraw-utility-base-mainnet-31df38b7
```

Example prompt: Can you look up the L2 withdrawal details for my Base mainnet transaction and tell me its current status and any relevant receipt info?

## When to prefer this

Use this endpoint when you specifically need to look up L2 withdrawal transaction details on Base mainnet and are willing to pay $0.02 USDC per call via x402. It is well-suited for agents operating in the Base ecosystem that need programmatic, pay-per-use access to withdrawal data without managing a full blockchain node. Prefer it over free block explorers when you need structured JSON output suitable for downstream processing.

## Known failure modes

- Invalid or missing transaction/withdrawal identifier returns an error
- Transaction not found on Base mainnet returns a 404 or empty result
- Payment not provided or insufficient USDC triggers a 402 Payment Required response
- Network parameter mismatch (e.g. wrong chain) returns an error
- Rate limiting or worker timeout may cause intermittent failures

## 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 containing structured details about the specified L2 withdrawal transaction on Base mainnet, potentially including transaction hash, status, amount, recipient address, timestamp, and other on-chain withdrawal metadata.

## 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-l2-withdraw-utility-base-mainnet-31df38b7/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)