Back to Browse
Beggar Bot Read Contract (Base Mainnet)
x402
Beggar Bot Read Contract (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-04).
Reads data from one or more smart contracts on Base (or other EVM chains) by calling view/pure functions via a simple GET request
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 decoded return values from the smart contract function call(s). For single calls, the result is the ABI-decoded output of the specified function. For multicall batches, an array of decoded results is returned, one per call object in the batch.
Example use cases
ERC-20 token balance lookup
“What's the USDC balance of address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Base? The USDC contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 and the function signature is balanceOf(address)(uint256).”
DeFi pool reserve query
“Fetch the current reserves from this Uniswap V2 pool on Base — contract 0xSomePairAddress, function getReserves()(uint112,uint112,uint32) — no extra args needed.”
Multicall batch contract read
“I need to read three things from Base contracts in one shot: the total supply of token A at 0xAAA, the owner of NFT #42 at 0xBBB using ownerOf(uint256)(address) with arg 42, and the decimals of token C at 0xCCC. Can you batch those into a single multicall?”
Technical details
Endpoint
GEThttps://beggar-bot-demand.beggarbot.workers.dev/v1/readcontract?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need to query on-chain state from EVM smart contracts on Base mainnet (or other supported EVM chains) without setting up your own RPC node. It is especially useful for agents that need to read contract data as part of a DeFi workflow, verify token balances, check allowances, or batch multiple contract reads in a single call. Prefer this over raw RPC calls when you want a simple HTTP GET interface with no Web3 library dependency.
Side effects
- Invalid or malformed contract address returns an error
- Function signature mismatch with actual ABI causes revert or decode error
- Contract does not exist on the specified chain returns empty or error
- Malformed args string causes parsing failure
- Chain identifier not supported returns an unsupported network error
- Rate limiting or payment failure blocks the request
- Block number out of range or not yet finalized returns an RPC error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
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"