# Beggar Bot L2 Deposit Lookup (Base mainnet)

> Beggar Bot L2 Deposit Lookup (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).

Looks up and analyzes L2 deposit information on Base mainnet (or Base Sepolia testnet) for a given transaction or address, returning structured deposit data.

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/l2deposit?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-deposit-lookup-base-mainnet-b9dfca7a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_erL7qTkPiosUHcDkIIBRL

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-deposit-lookup-base-mainnet-b9dfca7a
```

Example prompt: Can you look up the L2 deposit details for transaction 0xabc123 on Base mainnet using Beggar Bot?

## When to prefer this

Use this endpoint when you need to look up or verify specific L2 deposit transactions on Base mainnet or Base Sepolia testnet, especially for USDC deposits. Prefer it over general block explorers when you need structured, machine-readable deposit data for agent workflows. Best suited for confirming bridged funds, debugging failed deposits, or auditing deposit histories programmatically via a paid, x402-compatible API.

## Known failure modes

- Payment not received — returns 402 if the $0.02 USDC x402 payment is missing or invalid
- Transaction hash not found — returns error if the deposit does not exist on the specified network
- Invalid input — malformed address or hash returns a validation error
- Network mismatch — querying a mainnet tx on Sepolia (or vice versa) may return no results
- Rate limiting or worker timeout on Cloudflare edge

## 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

Returns structured JSON containing L2 deposit details for the queried transaction or address on Base mainnet (or Base Sepolia), including deposit status, amounts, timestamps, and USDC-related transfer information.

## 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-deposit-lookup-base-mainnet-b9dfca7a/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)