# Robinhood Chain eth_call – Contract View Function Query

> Robinhood Chain eth_call – Contract View Function Query is a paid API for AI agents from x402-services-production.up.railway.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Executes a read-only eth_call against any contract view function on Robinhood Chain, returning the result without submitting a transaction.

## Facts

- Endpoint: POST https://x402-services-production.up.railway.app/api/rhchain/call
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/robinhood-chain-eth-call-contract-view-function-query-b7bb0761
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_f76XesKZUMcAPs-pbkI_I

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 robinhood-chain-eth-call-contract-view-function-query-b7bb0761 -d '<json body>'
```

Example prompt: Call the balanceOf view function on the Robinhood Chain token contract at 0xABC...123 for wallet 0xDEF...456 — give me the raw return value.

## When to prefer this

Choose this endpoint when you need to read state from any smart contract on Robinhood Chain specifically (not Ethereum mainnet or other EVM chains). It is ideal for agents that need live on-chain data — balances, reserves, prices, ownership — without sending transactions or paying gas. Prefer it over generic EVM RPC endpoints when you want a pay-per-call model with no infrastructure setup.

## Known failure modes

- Invalid contract address returns an error or empty result
- Malformed calldata (bad ABI encoding) causes a revert response
- Contract does not exist at the given address on Robinhood Chain
- View function reverts with an on-chain reason string
- Network congestion or RPC node unavailability causes a timeout
- Missing required 'to' or 'data' fields returns a 400-level error

## How this service works

Robinhood Chain read-only eth_call: query any contract view function. Send { to, data, from? }.

## Output

The raw ABI-encoded return value from the contract's view function, reflecting the current on-chain state at the time of the call. No transaction is broadcast; this is purely a read operation.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json"
     ],
     "type": "string"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/robinhood-chain-eth-call-contract-view-function-query-b7bb0761/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-services-production.up.railway.app](https://www.zero.xyz/host/x402-services-production.up.railway.app/llms.txt)
