# Prism MCP — Ethereum & Base JSON-RPC Proxy

> Prism MCP — Ethereum & Base JSON-RPC Proxy is a paid API for AI agents from mcp.zeamprism.com, paid per call via x402, $0.00025/call, status unknown (last checked 2026-10-11).

Forwards arbitrary JSON-RPC method calls to an Ethereum or Base node and returns the node's verbatim response, billed per-call via x402.

## Facts

- Endpoint: POST https://mcp.zeamprism.com/v1/call_rpc?utm_source=zero.xyz
- Price: $0.00025/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prism-mcp-ethereum-base-json-rpc-proxy-625ff9bd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6hGrbl8MaljEqr1XbiZmu

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 prism-mcp-ethereum-base-json-rpc-proxy-625ff9bd -d '<json body>'
```

Example prompt: Can you call eth_getBalance for address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on the Base chain and tell me the current balance?

## When to prefer this

Choose this endpoint when you need to query EVM-compatible nodes on Ethereum mainnet or Base without managing your own RPC infrastructure, and are comfortable with per-call micro-billing via x402/USDC. It exposes the full JSON-RPC surface (eth_*, debug_*, trace_*, txpool_*, etc.) rather than a curated subset, making it suitable for advanced queries like transaction tracing, mempool inspection, or raw contract calls that higher-level APIs often don't expose.

## Known failure modes

- Invalid chain value (not 'eth' or 'base') results in an error response
- Unsupported or misspelled JSON-RPC method returns a node-level error in the rpc_response envelope
- Malformed params array causes a JSON-RPC parse error from the node
- Node downtime or network error returns a non-200 HTTP status
- Rate limiting or payment failure via x402 blocks the request

## How this service works

Prism: an agent-facing tools marketplace. Paid by the millisecond in USDC on Base over x402 via ZEAM :: Pass; some tools free. No account, no API key. ZEAM Labs, LLC. One human and the agents it employs. This endpoint was built and is operated by those agents.

## Output

Returns an object containing the chain that was queried, the JSON-RPC method that was called, the HTTP status code from the node, and the full verbatim JSON-RPC response envelope (including id, jsonrpc, result or error fields exactly as the node returned them).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "base",
    "eth"
   ],
   "type": "string",
   "description": "string — which node to forward to: eth or base"
  },
  "method": {
   "type": "string",
   "description": "string — a JSON-RPC method; the ones we check are listed in /llms.txt. Not forwarded: signing methods, debug_ methods that control the node, eth_subscribe (use the websocket)."
  },
  "params": {
   "type": "array",
   "description": "optional array — JSON-RPC params, default []"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prism-mcp-ethereum-base-json-rpc-proxy-625ff9bd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcp.zeamprism.com](https://www.zero.xyz/host/mcp.zeamprism.com/llms.txt)