# ZEAM Prism MCP — Ethereum JSON-RPC Proxy

> ZEAM Prism MCP — Ethereum JSON-RPC Proxy is a paid API for AI agents from mcp.zeamprism.com, paid per call via x402, $0.001796/call, status unknown (last checked 2026-09-18).

Forwards any Ethereum JSON-RPC method call to an Ethereum node and returns the raw JSON-RPC response, billed per-call via x402 micropayments.

## Facts

- Endpoint: POST https://mcp.zeamprism.com/rpc/eth
- Price: $0.001796/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/zeam-prism-mcp-ethereum-json-rpc-proxy-f39855be
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_03_dE5nY_0EIZW-jnRqiT

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 zeam-prism-mcp-ethereum-json-rpc-proxy-f39855be -d '<json body>'
```

Example prompt: Call eth_getBalance on the Ethereum node for address 0xde0B295669a9FD93d5F28D9Ec85E40f4cb697BAe with block tag 'latest' and give me the raw result.

## When to prefer this

Choose this endpoint when an AI agent needs direct, metered Ethereum or Base JSON-RPC access without managing its own node infrastructure, and especially when operating in a pay-per-call micropayment context (x402). It is ideal for agents that need occasional or bursty on-chain reads without a long-term node subscription. It supports the full range of eth_*, net_*, web3_*, txpool_*, debug_*, and trace_* methods, making it suitable for both simple balance lookups and advanced trace/debug workflows.

## Known failure modes

- Invalid chain value (not 'eth' or 'base') returns an error
- Unsupported or misspelled JSON-RPC method returns a node-level error in rpc_response
- Malformed params array causes node to return an invalid params error
- Node unavailability or timeout results in non-200 http_status
- Payment failure via x402 prevents the call from reaching the node
- debug_* and trace_* methods may not be available if the node does not support them

## How this service works

ZEAM Labs LLC. One human and the agents it employs. This endpoint was built and is operated by those agents. One metered line, billed by the millisecond over x402. tools/list is the catalog.

## Output

Returns a JSON object containing the target chain name, the method called, the node's HTTP status code, and the verbatim JSON-RPC response envelope (with jsonrpc, id, result or error fields) exactly as returned by the underlying Ethereum node.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "chain",
  "method"
 ],
 "properties": {
  "chain": {
   "type": "string",
   "description": "string — which node to forward to: eth or base"
  },
  "method": {
   "type": "string",
   "description": "string — any method the node serves: eth_*, net_*, web3_*, txpool_*, debug_*, trace_*;…"
  },
  "params": {
   "type": "array",
   "description": "optional array — JSON-RPC params, default []"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "chain",
  "method",
  "http_status",
  "rpc_response"
 ],
 "properties": {
  "chain": {
   "type": "string",
   "description": "the node this was forwarded to"
  },
  "method": {
   "type": "string",
   "description": "the JSON-RPC method called"
  },
  "http_status": {
   "type": "number",
   "description": "the node's HTTP status"
  },
  "rpc_response": {
   "type": "object",
   "description": "the node's JSON-RPC envelope, verbatim"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zeam-prism-mcp-ethereum-json-rpc-proxy-f39855be/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)