# Beggar Bot /v1/juplst Utility Endpoint (Base Mainnet)

> Beggar Bot /v1/juplst Utility 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).

An unknown or experimental utility endpoint on the Beggar Bot agent utilities platform, served at /v1/juplst on Base mainnet with x402 micropayment gating at $0.02 USDC per call.

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/juplst?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-v1-juplst-utility-endpoint-base-mainnet-ea87d1dc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0zT4QFwdgWdURIPc_woV2

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-juplst-utility-endpoint-base-mainnet-ea87d1dc
```

Example prompt: Can you call the Beggar Bot juplst utility on Base mainnet and get back whatever it returns — I'll cover the $0.02 USDC fee via x402.

## When to prefer this

Use this endpoint only when specifically targeting the Beggar Bot /v1/juplst utility on Base mainnet. The path name is opaque and not clearly documented, so prefer this only if you know this specific endpoint is part of your Beggar Bot integration. The sibling endpoints /v1/verify, /v1/risk, and /v1/receipt are better documented alternatives for verification, risk assessment, and receipt operations respectively.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment not accepted — returns 402 Payment Required
- Invalid properties parameter: malformed input may return 400 Bad Request
- Endpoint may be undocumented or non-functional, returning 404 or empty response
- Cloudflare Worker timeout or error returns 500 or 503
- Network mismatch if base-sepolia is specified incorrectly

## 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 object returned by the /v1/juplst endpoint. The exact structure is undocumented — the endpoint appears experimental or proprietary. The response format is generic JSON as declared in the response schema.

## 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-juplst-utility-endpoint-base-mainnet-ea87d1dc/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)