# Beggar Bot HLVaultPos Endpoint (Base Mainnet)

> Beggar Bot HLVaultPos 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-04).

Returns high-level vault position data on Base mainnet, paid via x402 micropayment protocol at $0.02 USDC per call

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/hlvaultpos?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-hlvaultpos-endpoint-base-mainnet-65d69cbb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ndv3GH-Lkzi5N5JwjGvke

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-hlvaultpos-endpoint-base-mainnet-65d69cbb
```

Example prompt: Can you fetch the high-level vault position data for USDC on Base mainnet using the Beggar Bot hlvaultpos endpoint? I want to see current vault metrics and holdings.

## When to prefer this

Use this endpoint when you need a high-level snapshot of vault positions on Base mainnet and are set up to pay via x402 micropayments in USDC. Prefer this over manual on-chain queries when you want a structured JSON summary without writing custom blockchain calls. Best for agents already integrated with the x402 payment protocol targeting Base mainnet DeFi vaults.

## Known failure modes

- Payment not included or insufficient USDC — returns HTTP 402 requiring x402 payment of $0.02 USDC
- Invalid or missing properties parameter — may return empty or malformed response
- Network parameter set to unsupported value — defaults to base mainnet or errors
- Cloudflare Worker timeout or upstream RPC error — 500 or gateway error response
- Rate limiting or payment address mismatch — 402 or 403 error

## 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 a JSON object containing high-level vault position information for the specified vault on Base mainnet (or Base Sepolia if specified), including holdings, balances, and position metrics for USDC or other tracked assets.

## 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-hlvaultpos-endpoint-base-mainnet-65d69cbb/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)