# Beggar Bot Address Poisoning Detector

> Beggar Bot Address Poisoning Detector 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-02).

Detects address poisoning attacks by comparing a list of addresses against a known address book and intended recipient on Base mainnet

## Facts

- Endpoint: POST https://beggar-bot-demand.beggarbot.workers.dev/v1/addrpoison?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/beggar-bot-address-poisoning-detector-da1e8d78
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yTfyWCn7UiGCjPvZFHq4n

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-address-poisoning-detector-da1e8d78 -d '<json body>'
```

Example prompt: Before I send this USDC transfer, check whether 0x1234abcd...ef is safe — my address book includes 0xAAA...111 and 0xBBB...222, and my intended recipient is 0xAAA...111. Flag any address poisoning risk.

## When to prefer this

Choose this endpoint when an AI agent or wallet application needs to protect a user from address poisoning attacks on Base mainnet — specifically when you have a known address book to compare against. It is purpose-built for the address-poisoning threat vector (look-alike addresses injected into transaction history) and costs $0.02 USDC per call via x402, making it appropriate for pre-transfer security checks where catching a poisoned address is worth the small fee.

## Known failure modes

- Missing required fields (known, intended, or addresses) returns a 4xx validation error
- Payment failure via x402 if USDC balance is insufficient or payment not completed
- Malformed Ethereum addresses in input may cause parsing errors
- Network error on Cloudflare Worker returns 5xx
- Empty addresses array returns trivial or error response

## 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 indicating whether any of the checked addresses appear to be poisoning attempts — comparing them against the known address book and intended recipient to flag suspicious look-alike or substituted addresses, likely including a risk verdict, matched/unmatched indicators, and details about suspicious addresses.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "known": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "your address book"
  },
  "intended": {
   "type": "string",
   "description": "intended recipient"
  },
  "addresses": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "addresses to check"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/beggar-bot-address-poisoning-detector-da1e8d78/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)