# Beggar Bot V2 Liquidity Pool Endpoint (Base Mainnet)

> Beggar Bot V2 Liquidity Pool Endpoint (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-10).

Returns V2 liquidity pool data on Base mainnet for USDC and related tokens, paid via x402 micropayment protocol

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/v2lp?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/beggar-bot-v2-liquidity-pool-endpoint-base-mainnet-8624faec
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zzZJq4xDnX7j7vJ_dCVV5

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-v2-liquidity-pool-endpoint-base-mainnet-8624faec
```

Example prompt: Can you pull the V2 liquidity pool data for USDC on Base mainnet from Beggar Bot — I want to see the current pool reserves and metrics?

## When to prefer this

Use this endpoint when you need V2 liquidity pool data specifically on Base mainnet, particularly for USDC pairs, and are already operating within the x402 micropayment ecosystem. Prefer this over general blockchain RPC calls when you want pre-processed pool metrics without writing raw contract calls. Best suited for agents that have USDC on Base and need quick LP intelligence for trading, arbitrage, or portfolio decisions.

## Known failure modes

- Payment not provided or invalid x402 payment header — returns 402 Payment Required
- Invalid or missing properties parameter — returns malformed or empty response
- Network parameter not recognized — may fall back to Base mainnet default or return error
- Rate limiting or worker quota exceeded on Cloudflare — returns 503 or timeout
- Pool not found for given token pair — returns empty or null pool data

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

JSON object containing V2 liquidity pool data for the queried token pair on Base mainnet, including pool reserves, token addresses, and pool state metrics. Response is specific to USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) by default; base-sepolia network can be requested optionally. Costs $0.02 USDC per call via x402 payment protocol.

## 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-v2-liquidity-pool-endpoint-base-mainnet-8624faec/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)