# Raw Contract Storage Slot Reader

> Raw Contract Storage Slot Reader is a paid API for AI agents from flat-rate-llm.kikoribera03.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Reads a raw storage slot of any EVM smart contract and returns the value decoded as hex, unsigned integer, and address.

## Facts

- Endpoint: POST https://flat-rate-llm.kikoribera03.workers.dev/v1/evm/storage
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/raw-contract-storage-slot-reader-9db7fcf5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jnEGE31ta6awoiz5MFfE6

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 raw-contract-storage-slot-reader-9db7fcf5 -d '<json body>'
```

Example prompt: Can you read storage slot 0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc of the contract 0x1234...abcd on Base and tell me what address is stored there?

## When to prefer this

Use this endpoint when you need to inspect internal EVM contract state that has no public getter — especially for proxy pattern implementation slots (EIP-1967), owner or admin slots, and paused flags. It is the right choice when you know the slot number or can compute it from an EIP standard hash, and you need the value decoded in multiple formats (hex, uint, address) in a single call. Prefer this over a full node RPC call when you want a simple HTTP POST interface without managing an Ethereum provider.

## Known failure modes

- Invalid contract address returns an error or zero value
- Unsupported chain name returns a validation error
- Slot index out of expected range returns zero bytes (0x000...000) which may be confused with an unset value
- Malformed 0x slot key returns a parsing error
- Contract not deployed at address returns zero value indistinguishable from an empty slot
- Network RPC errors on the target chain cause upstream failures

## How this service works

60 paid endpoints with no metering, no API key and no account. Each endpoint has one flat price per call, whatever the size of the request: LLM completions with automatic failover across several large models, read-only EVM tooling over Base, Ethereum, Polygon, Arbitrum and Optimism, and pure crypto utilities that touch no network.

## Output

Returns a JSON object with the raw storage slot value as a 32-byte hex string, the same value decoded as an unsigned integer (asUint), and implicitly the value as an Ethereum address if applicable. This lets the caller interpret the slot as a boolean flag, a counter, an owner address, or a proxy implementation pointer.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "address"
 ],
 "properties": {
  "slot": {
   "type": "string",
   "description": "Slot number in decimal, or a 0x slot key such as an EIP-1967 hash."
  },
  "chain": {
   "type": "string",
   "description": "base | ethereum | polygon | arbitrum | optimism."
  },
  "address": {
   "type": "string",
   "description": "Contract to read."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "value": {
   "type": "string"
  },
  "asUint": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/raw-contract-storage-slot-reader-9db7fcf5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from flat-rate-llm.kikoribera03.workers.dev](https://www.zero.xyz/host/flat-rate-llm.kikoribera03.workers.dev/llms.txt)