# AiSpace Venice EVM/Starknet JSON-RPC Proxy (Base Mainnet)

> AiSpace Venice EVM/Starknet JSON-RPC Proxy (Base Mainnet) is a paid API for AI agents from x402.aispace.bot, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Forwards JSON-RPC method calls to the Base Mainnet blockchain (and 20+ other EVM/Starknet networks) as a pay-per-call proxy, billed in USDC on Base via x402.

## Facts

- Endpoint: POST https://x402.aispace.bot/api/v1/crypto/rpc/base-mainnet
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aispace-venice-evm-starknet-json-rpc-proxy-base-mainnet-8fd4bb12
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gDfPsOtccgMJBAp22YYpw

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 aispace-venice-evm-starknet-json-rpc-proxy-base-mainnet-8fd4bb12 -d '<json body>'
```

Example prompt: Call eth_getBalance on Base Mainnet for address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 and return the balance in wei — use the Base Mainnet JSON-RPC proxy, no API key needed, pay per call in USDC.

## When to prefer this

Choose this endpoint when you need keyless, pay-per-call access to Base Mainnet (or other EVM/Starknet networks) JSON-RPC without provisioning your own RPC node or managing API keys. Ideal for agents that need occasional on-chain lookups billed in micro-USDC amounts, or for serverless pipelines where storing RPC credentials is undesirable. Not suited for high-frequency or write-heavy workloads where a dedicated node would be more cost-effective.

## Known failure modes

- Invalid JSON-RPC method name returns a JSON-RPC error object with code and message
- Unknown or unsupported network segment returns a 404 or error response
- Malformed params array causes a parse error or invalid params JSON-RPC error
- Insufficient USDC payment via x402 results in a 402 Payment Required response
- Network-level RPC node unavailability may return a temporary 503 or upstream error
- Passing a write method (eth_sendRawTransaction) may succeed or fail depending on network configuration

## How this service works

Pay-per-call JSON-RPC proxy to 20+ EVM and Starknet networks on Venice, paid per request in USDC on Base via x402, no API key. Resolve the {network} path segment from GET /api/v1/crypto/rpc/networks.

## Output

A standard JSON-RPC response object containing either a 'result' field with the on-chain data (block number, balance, call output, etc.) or an 'error' field describing what went wrong. The outer envelope also includes an 'ok' boolean indicating request success.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "description": "JSON-RPC request id."
  },
  "method": {
   "type": "string",
   "description": "JSON-RPC method name, e.g. eth_blockNumber."
  },
  "params": {
   "type": "array",
   "description": "JSON-RPC params array for the method."
  },
  "jsonrpc": {
   "type": "string",
   "description": "JSON-RPC version. Typically \"2.0\"."
  },
  "network": {
   "type": "string",
   "description": "Network id path segment. See GET /api/v1/crypto/rpc/networks (e.g. base-mainnet, ethereum-mainnet)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aispace-venice-evm-starknet-json-rpc-proxy-base-mainnet-8fd4bb12/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.aispace.bot](https://www.zero.xyz/host/x402.aispace.bot/llms.txt)