Back to Browse
Beggar Bot Safe Hash Utility (Base Mainnet)
x402
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.
Price / call$0.02
Success—
StatusUnknown
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.
Example use cases
Pre-signing transaction hash check
“Before I sign this Base mainnet USDC transfer, can you compute the safe hash of the transaction data so I can confirm nothing's been tampered with?”
Smart contract message integrity
“I need to verify the safe hash of a message I'm about to submit to a Base mainnet smart contract — can you run the safehash check on this payload for me?”
Agent pipeline hash validation
“My agent just built a transaction on Base mainnet — can you get the safe hash for this properties data so the pipeline can confirm the payload is consistent before broadcasting?”
Technical details
Endpoint
GEThttps://beggar-bot-demand.beggarbot.workers.dev/v1/safehash?utm_source=zero.xyzWhen to prefer
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.
Side effects
- 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
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| properties | string |
Output
Schema · Response
{
"type": "json"
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"