# Beggar Bot /v1/hlfees – Hyperliquid Fee Lookup (Base Mainnet)

> Beggar Bot /v1/hlfees – Hyperliquid Fee 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-10).

Returns Hyperliquid fee schedule or fee-related data for Base mainnet via the Beggar Bot agent utilities suite, payable at $0.02 USDC per call via x402.

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/hlfees?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-v1-hlfees-hyperliquid-fee-lookup-base-mainnet-c6a49385
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3VIwarcMTXQI1GSIWBJBM

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-v1-hlfees-hyperliquid-fee-lookup-base-mainnet-c6a49385
```

Example prompt: Can you fetch the current Hyperliquid fee schedule on Base mainnet using Beggar Bot's hlfees endpoint so I know what trading fees to expect?

## When to prefer this

Use this endpoint when an AI agent needs on-demand, up-to-date Hyperliquid fee schedule data on Base mainnet and is already operating within the x402 micropayment flow. Prefer this over scraping Hyperliquid's UI or using manual lookups when you need programmatic, low-cost fee data integrated into an automated DeFi workflow.

## Known failure modes

- Payment not received — x402 payment of $0.02 USDC to 0x719227f384b66BFEF00093D6d8d32fA9dC2B40e7 on Base mainnet must precede the call
- Invalid or malformed properties parameter returns an error or empty result
- Network parameter typo (e.g. wrong chain name) may return default Base mainnet data or an error
- Cloudflare Worker downtime results in 5xx responses
- Stale fee data if Hyperliquid updates its schedule and the cache has not refreshed

## 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 Hyperliquid fee schedule or fee-tier data as observed on Base mainnet (or base-sepolia if specified), including applicable trading fee rates or related fee metadata.

## 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-v1-hlfees-hyperliquid-fee-lookup-base-mainnet-c6a49385/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)