# Beggar Bot SOL-Verified Address Lookup (Base mainnet)

> Beggar Bot SOL-Verified Address 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).

Looks up verified Solana-linked addresses or SOL-verified wallet data on Base mainnet via a paid x402 endpoint.

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/solverified?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-sol-verified-address-lookup-base-mainnet-279cc927
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8lBF9RNerJJTfDUczMPuI

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-sol-verified-address-lookup-base-mainnet-279cc927
```

Example prompt: Can you check if the wallet address 0xABC123... is SOL-verified on Base mainnet using Beggar Bot's solverified lookup?

## When to prefer this

Use this endpoint when you need to verify whether a specific wallet address has been SOL-verified on Base mainnet as part of Beggar Bot's verification suite, particularly in agent workflows that gate actions on address legitimacy. Prefer this over generic blockchain explorers when you specifically need the SOL-verification status signal rather than general transaction history.

## Known failure modes

- Payment not received — x402 payment of $0.02 USDC to 0x719227f384b66BFEF00093D6d8d32fA9dC2B40e7 not completed, returns 402
- Invalid or malformed address input — returns error or empty result
- Address not found in SOL-verified registry — returns null or unverified status
- Network mismatch — querying wrong network if base-sepolia is not specified correctly
- Rate limiting or Cloudflare Worker timeout

## 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 response indicating whether the queried address has been SOL-verified on Base mainnet, along with any associated verification metadata or properties from the on-chain record.

## 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-sol-verified-address-lookup-base-mainnet-279cc927/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)