# Beggar Bot CometPOS Endpoint (Base Mainnet)

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

Provides CometPOS-related data or point-of-sale analytics for Base mainnet transactions, paid via x402 micropayment protocol at $0.02 USDC per call.

## Facts

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

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-cometpos-endpoint-base-mainnet-42a0e9b0
```

Example prompt: Can you fetch the CometPOS data from Beggar Bot on Base mainnet for me? I'll authorize the $0.02 USDC micropayment.

## When to prefer this

Use this endpoint when you specifically need CometPOS data from the Beggar Bot service on Base mainnet and are prepared to make a $0.02 USDC micropayment via the x402 protocol. It is part of the Beggar Bot suite of blockchain utility endpoints and is distinct from the cheaper /v1/verify, /v1/risk, and /v1/receipt endpoints ($0.01 each). Prefer this when your workflow requires CometPOS-specific output rather than transaction verification or risk analysis.

## Known failure modes

- Insufficient USDC balance for $0.02 micropayment — returns 402 Payment Required
- Invalid or missing properties parameter — returns 400 Bad Request
- x402 payment not confirmed on Base mainnet — payment rejected
- Network unavailable or Cloudflare Worker error — returns 503
- Incorrect network specified — data unavailable for requested chain

## 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 containing CometPOS-related data or point-of-sale analytics for the Base mainnet, returned after a successful x402 micropayment of $0.02 USDC to the operator's address.

## 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-cometpos-endpoint-base-mainnet-42a0e9b0/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)