# GPUOps Ethereum RPC Endpoint

> GPUOps Ethereum RPC Endpoint is a paid API for AI agents from chain.gpuops.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Executes Ethereum JSON-RPC calls via a pay-per-call API using x402/USDC micropayments on Base

## Facts

- Endpoint: POST https://chain.gpuops.io/v1/rpc/ethereum
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gpuops-ethereum-rpc-endpoint-a2e94d19
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HId1SrtSFLOXzZwyqlx2B

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 gpuops-ethereum-rpc-endpoint-a2e94d19 -d '<json body>'
```

Example prompt: What's the current ETH balance of wallet address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum mainnet?

## When to prefer this

Choose this endpoint when you need direct Ethereum JSON-RPC access with pay-per-call micropayment billing (no subscription required) and want to avoid managing your own node. Ideal for agents making sporadic or low-volume Ethereum queries where a $0.001/call model is more cost-effective than a subscription RPC provider.

## Known failure modes

- Invalid JSON-RPC method name returns error code -32601
- Malformed params array causes -32602 invalid params error
- Payment failure or insufficient USDC balance returns HTTP 402
- Rate limiting or node unavailability returns HTTP 503 or timeout
- Requesting data for a non-existent block or tx hash returns null result

## How this service works

Multi-chain blockchain data API. 7 chains. x402 pay-per-call with USDC on Base.

## Output

A standard JSON-RPC response object containing the result field with Ethereum data (balances in wei, block objects, transaction receipts, contract return values, gas estimates, etc.) or an error object with code and message if the call fails.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": "integer"
  },
  "method": {
   "type": "string"
  },
  "params": {
   "type": "array"
  },
  "jsonrpc": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gpuops-ethereum-rpc-endpoint-a2e94d19/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chain.gpuops.io](https://www.zero.xyz/host/chain.gpuops.io/llms.txt)