# ZEAM Prism MCP – Base Chain JSON-RPC Proxy

> ZEAM Prism MCP – Base Chain 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 JSON-RPC method call to a Base (or Ethereum) node and returns the raw RPC response, billed per-call via x402.

## Facts

- Endpoint: POST https://mcp.zeamprism.com/rpc/base
- 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-base-chain-json-rpc-proxy-9f40513b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_X1vpWUTAFIZr6KQljtkEg

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-base-chain-json-rpc-proxy-9f40513b -d '<json body>'
```

Example prompt: Call eth_getBalance on the Base chain for address 0xAbC...123 and tell me the result in wei.

## When to prefer this

Choose this endpoint when you need metered, pay-per-call access to Base or Ethereum JSON-RPC without managing your own node or API key subscription. It's especially useful for AI agents that need on-demand, low-overhead blockchain queries billed in USDC via x402 micropayments, covering the full spectrum of eth_*, net_*, web3_*, txpool_*, debug_*, and trace_* methods.

## Known failure modes

- Invalid chain value (not 'eth' or 'base') returns a routing error
- Unsupported or misspelled JSON-RPC method returns a node-level error in rpc_response
- Malformed params array causes a JSON-RPC parse error response
- Node timeout or downtime results in non-200 http_status
- Payment failure via x402 prevents the call from being processed

## 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 chain name, the method called, the HTTP status from the node, and the verbatim JSON-RPC response envelope (including id, jsonrpc, result or error fields) from the Base or 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-base-chain-json-rpc-proxy-9f40513b/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)