# AiSpace Crypto RPC Proxy

> AiSpace Crypto RPC Proxy is a paid API for AI agents from x402.aispace.bot, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-07).

Proxies HTTP GET/HEAD/DELETE requests to a specified blockchain network's RPC endpoint via the AiSpace platform, enabling paid crypto network interactions.

## Facts

- Endpoint: POST https://x402.aispace.bot/api/v1/crypto/rpc/%7Bnetwork%7D?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-07
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aispace-crypto-rpc-proxy-8df9d4a3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GnP2tpwaVWBtKnp-Rf18U

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-crypto-rpc-proxy-8df9d4a3 -d '<json body>'
```

Example prompt: Can you proxy a GET request to the Base network RPC endpoint using AiSpace's crypto RPC proxy?

## When to prefer this

Choose this endpoint when you need to make read-only or status-check RPC calls to a blockchain network (GET, HEAD, DELETE) without maintaining your own node infrastructure, and you are comfortable with micro-payment per call via x402 protocol. Best for lightweight, infrequent blockchain queries where self-hosting is impractical.

## Known failure modes

- Invalid or unsupported network name returns an error or ok:false
- HTTP method not in allowed enum (GET, HEAD, DELETE) causes validation failure
- Missing required 'network' path parameter causes request rejection
- Payment of $0.001 USDC not provided results in 402 Payment Required
- Network RPC endpoint unreachable returns error response

## How this service works

Pay-per-request Venice inference via x402. Chat, image, video, audio, search, and RPC — USDC on Base, no API key. OpenAI-compatible /api/v1 at x402.aispace.bot.

## Output

Returns a JSON object with an 'ok' boolean indicating whether the proxied RPC request to the specified blockchain network succeeded.

## 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)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": 1,
  "result": "0x3058842",
  "jsonrpc": "2.0"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aispace-crypto-rpc-proxy-8df9d4a3/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)