# Beggar Bot High-Level Orders (HL Orders) Lookup – Base Mainnet

> Beggar Bot High-Level Orders (HL Orders) 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 high-level order data on Base mainnet for blockchain/DeFi order analysis via a paid x402 endpoint costing $0.02 USDC per call.

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/hlorders?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-high-level-orders-hl-orders-lookup-base-mainnet-17079d3d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ySWREanC6l0WokrhSKV7Y

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-high-level-orders-hl-orders-lookup-base-mainnet-17079d3d
```

Example prompt: Can you fetch the high-level orders on Base mainnet from Beggar Bot — I want to see the current on-chain order data?

## When to prefer this

Choose this endpoint when you specifically need high-level on-chain order data from Base mainnet and are set up to pay via the x402 micropayment protocol using USDC. It is distinct from the lower-cost verify/risk/receipt endpoints ($0.01 each) on the same service, and is appropriate when order-level DeFi data is needed rather than transaction verification or risk scoring.

## Known failure modes

- Payment not provided or insufficient USDC — returns HTTP 402 requiring $0.02 USDC payment via x402 protocol
- Invalid properties filter parameter — may return empty results or a 400 error
- Network unavailable or Cloudflare Worker error — returns 5xx
- Base mainnet RPC issues causing delayed or incomplete order data
- Malformed query parameters returning unexpected JSON structure

## 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 high-level order records from the Base mainnet blockchain, including order details such as status, amounts, addresses, and other on-chain order metadata relevant to DeFi activity.

## 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-high-level-orders-hl-orders-lookup-base-mainnet-17079d3d/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)