# Beggar Bot Signature Recovery Utility

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

Recovers the Ethereum address that produced a given signature, supporting raw message, hash, or EIP-712 typed data inputs

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/sigrecover?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-signature-recovery-utility-54cfbac1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6V0fUbVj2zyS845aeoaMt

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-signature-recovery-utility-54cfbac1
```

Example prompt: Can you recover the Ethereum address that signed this message — the signature is 0x1234...abcd and the original message was 'Hello, World!'?

## When to prefer this

Use this endpoint when you need to cryptographically recover or verify the Ethereum address behind a signature on Base mainnet, especially within agentic workflows that already use x402 micropayments. Prefer this over general-purpose libraries when you need a hosted, pay-per-call service without managing RPC infrastructure, and when you need support for EIP-712 typed data, raw hashes, and personal_sign in a single API.

## Known failure modes

- Invalid or malformed signature returns an error
- Mismatched hash and message produce an unexpected recovered address
- Missing required 'signature' field returns a 400-level error
- Unsupported encoding value causes a processing error
- Payment not provided or insufficient USDC causes a 402 Payment Required response
- Typed data JSON malformed or unparseable returns an 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 the recovered Ethereum address (signer) derived from the provided signature and message/hash/typed_data inputs, along with optional verification status if an expected address was supplied.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "signature"
 ],
 "properties": {
  "hash": {
   "type": "string"
  },
  "message": {
   "type": "string"
  },
  "encoding": {
   "type": "string"
  },
  "expected": {
   "type": "string"
  },
  "signature": {
   "type": "string"
  },
  "typed_data": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/beggar-bot-signature-recovery-utility-54cfbac1/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)