Back to Browse
Beggar Bot Storage Slot Reader (Base mainnet)
x402
Beggar Bot Storage Slot Reader (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 raw EVM storage slots from smart contracts on Base, Ethereum, Optimism, Arbitrum, or Polygon, with support for mapping slots, proxy slot resolution, and optional block targeting.
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 object containing the raw value stored at the requested storage slot(s), with decoded fields where applicable. For named EIP-1967/ZOS slots, returns the resolved address or value. Mapping lookups return the computed slot and its value. Proxy detection may return additional proxy-related slots.
Example use cases
Proxy implementation address lookup
“What's the current implementation address of the upgradeable proxy at 0x4200000000000000000000000000000000000010 on Base — check the eip1967_impl slot for me.”
Solidity mapping value inspection
“Read the storage value for key 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 in the mapping at base slot 1 of contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base mainnet.”
Historical storage slot at specific block
“What was stored at slot 0 of contract 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum at block 18000000?”
Technical details
Endpoint
GEThttps://beggar-bot-demand.beggarbot.workers.dev/v1/storageslot?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need low-level EVM storage inspection for smart contracts — especially when you need to resolve proxy implementation addresses via EIP-1967 slots, inspect raw Solidity mapping values, or audit contract storage at a historical block. Prefer this over higher-level ABI-based call endpoints when the storage layout is known or when proxy slot patterns are needed without ABI decoding.
Side effects
- Invalid or missing contract address returns an error
- Unsupported chain name returns a validation error
- Invalid slot format (not decimal, hex, or named constant) returns a parse error
- Block number not yet finalized or too far in the past may return an error
- Payment not received (HTTP 402) if x402 USDC payment on Base mainnet is not included
- Rate limiting or worker timeout for complex multi-slot requests
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"