# Beggar Bot Bridge Aggregations Lookup (Base mainnet)

> Beggar Bot Bridge Aggregations 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).

Retrieves bridge aggregation data for USDC and other assets on Base mainnet, surfacing cross-chain bridging routes and liquidity information.

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/bridgeaggs?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-bridge-aggregations-lookup-base-mainnet-ba0d2cbc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9hpcdfmvTUfdiNHlNG89X

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-bridge-aggregations-lookup-base-mainnet-ba0d2cbc
```

Example prompt: Can you pull up the bridge aggregation data on Base mainnet for USDC so I can see what cross-chain bridging options are available?

## When to prefer this

Use this endpoint when you need to discover and compare cross-chain bridge aggregation data specifically for Base mainnet assets, particularly USDC. It is best suited for DeFi agents researching optimal bridging routes, monitoring bridge liquidity, or building cross-chain transfer workflows on Base. Prefer it over generic bridge UIs when you need machine-readable aggregation data accessible via a paid API with x402 micropayments.

## Known failure modes

- Payment not provided or insufficient — x402 payment of $0.02 USDC on Base mainnet required; missing payment returns 402
- Invalid network parameter — only base and base-sepolia are supported
- Cloudflare Worker timeout or unavailability — 5xx error
- Malformed query parameters — may return empty or error response
- Stale or missing bridge aggregator data — response may reflect incomplete routing information

## 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 containing bridge aggregation data for Base mainnet, including available bridging protocols, routes, and liquidity information for USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) and potentially other assets. Can optionally reflect Base Sepolia testnet data if the network parameter is specified.

## 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-bridge-aggregations-lookup-base-mainnet-ba0d2cbc/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)
