# Beggar Bot EVM Address Utility

> Beggar Bot EVM Address Utility 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).

Resolves, derives, or looks up Ethereum/Base EVM addresses from inputs like ENS names, public keys, CREATE3 salts, init code, or raw addresses

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/evmaddr?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-evm-address-utility-396ce573
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XDJUy2fAAaFHUjGhi-sAS

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-evm-address-utility-396ce573
```

Example prompt: What EVM address will be deployed on Base mainnet using CREATE3 with deployer 0xAbC...123 and salt 'myproject-v1'?

## When to prefer this

Choose this endpoint when you need to resolve, derive, or compute EVM addresses on Base mainnet from various inputs like ENS names, public keys, CREATE3 salts, or init code hashes — especially within an x402 micropayment-enabled agent workflow. Prefer this over generic ENS resolvers if you need CREATE3 address prediction or multi-input address resolution in one call on Base.

## Known failure modes

- Invalid ENS name returns error or null address
- Malformed public key causes derivation failure
- Missing required combination of fields (e.g. CREATE3 requires both deployer and salt) returns 400-level error
- Payment not attached results in 402 Payment Required response
- Unsupported network parameter returns error

## 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 object containing the resolved or derived EVM address (and possibly related metadata) corresponding to the input — such as an ENS-resolved address, a CREATE3-predicted contract address, a public-key-derived address, or a checksummed version of a provided address.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "salt": {
   "type": "string"
  },
  "nonce": {
   "type": "string"
  },
  "pubkey": {
   "type": "string"
  },
  "create3": {
   "type": "string"
  },
  "deployer": {
   "type": "string"
  },
  "name (ENS)": {
   "type": "string"
  },
  "address (or comma list)": {
   "type": "string"
  },
  "init_code | init_code_hash?": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

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