# Beggar Bot Safe Hash Utility (Base Mainnet)

> Beggar Bot Safe Hash Utility (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-10).

Computes or retrieves a safe hash for a given input on the Base mainnet blockchain, useful for verifying transaction or message integrity.

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/safehash?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/beggar-bot-safe-hash-utility-base-mainnet-6c19e029
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ctarL5d6PxZT0BSgS95Dw

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-safe-hash-utility-base-mainnet-6c19e029
```

Example prompt: Can you compute the safe hash for this Base mainnet transaction payload so I can verify it before signing?

## When to prefer this

Use this endpoint when you need a deterministic, on-chain-compatible safe hash for a Base mainnet transaction or message payload, especially within agent workflows that require integrity verification before signing or broadcasting. Prefer this over generic hashing utilities when Base mainnet semantics and USDC payment context matter.

## Known failure modes

- Missing or malformed 'properties' query parameter returns an error response
- Payment not provided or insufficient USDC balance causes a 402 Payment Required response
- Invalid Base mainnet context causes computation failure
- Network parameter mismatch (e.g. wrong chain) may return unexpected results

## 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 containing the computed safe hash of the provided input data, enabling downstream verification of transaction or message integrity on Base mainnet.

## 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-safe-hash-utility-base-mainnet-6c19e029/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)