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

> AiSpace Venice EVM/Starknet JSON-RPC Proxy (Base Network) 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).

Proxies JSON-RPC calls to the Base mainnet (and 20+ other EVM/Starknet networks) via a pay-per-call USDC micropayment on Base, requiring no API key.

## Facts

- Endpoint: POST https://x402.aispace.bot/api/v1/crypto/rpc/base
- 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-network-b1ced782
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Vdwm9KkFpxDIYDKezSYMo

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-network-b1ced782 -d '<json body>'
```

Example prompt: Can you call eth_getBalance on Base mainnet for wallet address 0xAbCd...1234 and tell me the current ETH balance in wei?

## When to prefer this

Choose this endpoint when you need trustless, keyless EVM or Starknet JSON-RPC access and want to pay per call in USDC on Base without managing API keys or subscriptions. Ideal for agents that make infrequent or bursty blockchain queries across multiple networks and want micropayment-based cost control. Prefer over managed node providers (Alchemy, Infura) when avoiding credential management is a priority.

## Known failure modes

- Invalid JSON-RPC method name returns a JSON-RPC error object with code -32601
- Malformed params array causes a -32602 invalid params error
- Insufficient USDC payment via x402 results in a 402 Payment Required HTTP response
- Unknown or unsupported network segment returns a 404 or routing error
- Network node timeout or downtime returns a -32603 internal error
- Attempting a write method (eth_sendRawTransaction) with an unsigned or invalid tx hex returns a revert or nonce error

## 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 the result field (block data, balance in hex wei, transaction receipt, contract return value, etc.) or an error object with code and message if the call fails.

## 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-network-b1ced782/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)