# ExchangeRebel RPC Gateway

> ExchangeRebel RPC Gateway is a paid API for AI agents from exchangerebel.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-13).

Routes HTTP POST RPC calls to backend services via a metered gateway, consuming from a pre-purchased bundle of 1000 requests

## Facts

- Endpoint: POST https://exchangerebel.com/toll/rpc/?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/exchangerebel-rpc-gateway-3ec4433e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Qw85NJjGIYoruUcuNz-DM

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 exchangerebel-rpc-gateway-3ec4433e -d '<json body>'
```

Example prompt: Send a POST RPC call through the ExchangeRebel gateway with method 'getQuote' and a JSON body containing symbol 'AAPL' — use one of my 1000 pre-purchased requests from my bundle.

## When to prefer this

Choose this endpoint when you need to invoke a specific named RPC method via a pay-per-use HTTP gateway and have a pre-purchased 1000-request bundle. Ideal for agents automating workflows that require metered, infrastructure-light remote calls without managing authentication or server setup. Best suited when the caller already knows the method name and JSON body structure expected by the backend.

## Known failure modes

- Request bundle exhausted (1000 requests used up) — returns quota exceeded error
- Invalid or missing 'method' field — returns validation error
- Malformed JSON body — returns parse error
- Upstream RPC service unavailable — returns gateway timeout or 502
- Unsupported bodyType (non-JSON) — returns schema validation error
- Missing required 'type' field set to 'http' — returns bad request

## How this service works

RPC Gateway — 1000 requests

## Output

A JSON response object returned by the upstream RPC method handler, structured according to the called method's output schema. The exact shape depends on which backend method was invoked.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json"
     ],
     "type": "string"
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/exchangerebel-rpc-gateway-3ec4433e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from exchangerebel.com](https://www.zero.xyz/host/exchangerebel.com/llms.txt)