Robinhood Chain public RPC and the free trial key

Triport's keyless Robinhood Chain URL is https://triport.io/public/robinhood: JSON-RPC over HTTPS with no key and one budget shared by every caller. Plan limits, WebSocket and the sequencer feed need an API key — try them with a 7-day Free trial key.

Endpoint and plans: Robinhood Chain RPC endpoint.

There are three ways to start without paying. Chain ID 4663 (0x1237) is the same behind all of them.

Without a key: /public/robinhood

curl https://triport.io/public/robinhood \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

{"jsonrpc":"2.0","id":1,"result":"0x1237"}

What it serves, checked with a live probe on 2026-10-24:

• the read methods of the Robinhood contract, including eth_getLogs, eth_getBlockReceipts, eth_feeHistory, eth_getProof and the debug_* trace methods;
• eth_sendRawTransaction and the other submission routes, at 3 req/s;
• JSON-RPC batches (a batch of 20 calls is answered) and bodies up to 256 KiB; a larger body is refused with HTTP 413;
• POST only — a GET is answered with 405 — and CORS is open, so a page in a browser can call it.

What it does not serve:

• trace_* and txpool_*: they are not part of the Robinhood contract on any Triport URL and are refused with HTTP 403 method_unknown;
• state at the very first blocks of the chain, which is outside coverage;
• WebSocket subscriptions and the sequencer feed;
• a budget of your own: the 15 req/s is shared by everyone who uses the URL, with no per-IP share. When it is spent the answer is HTTP 429; a Retry-After header is passed through when the origin sends one.

It is a way to test, not a plan: there is no account behind it to raise. Steady traffic belongs on a key. How requests to Triport are handled is described in the privacy policy.

Start with a Free trial key

Create a key in the console — see Getting started and Authentication — then make the first call:

curl https://triport.io/rpc/robinhood \
  -H "x-token: $TRIPORT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

{"jsonrpc":"2.0","id":1,"result":"0x1237"}

0x1237 is 4663 — mainnet. The key can travel three ways: the x-token header (or Authorization: Bearer) from server code, the ?api-key= query parameter, or the keyed URL https://triport.io/r/<API_KEY>/robinhood for wallets and config files that cannot send headers. A key in a URL is the credential itself — keep such URLs out of logs, screenshots and bug reports.

The trial covers JSON-RPC only. WebSocket subscriptions (newHeads, logs) start at Basic and the sequencer feed at Pro — see Limits for every plan.

A keyed URL without a key

curl https://triport.io/rpc/robinhood \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

{"error":"unauthorized","message":"Missing or unknown API key. Pass your key as ?api-key=<key> or the header Authorization: Bearer <key>. Create or copy a key at https://triport.io/app/keys","keys_url":"https://triport.io/app/keys"}

The body is a flat object with no jsonrpc field, so a JSON-RPC client reports it as a transport error, not as an RPC error. Every path under https://triport.io/rpc/robinhood answers this way without a key, including any older "public" path you may find in a configuration: replace it with https://triport.io/public/robinhood or with a keyed URL.

Adding the network to a wallet

A wallet needs a URL that works without headers. Three choices are honest:

• the keyless https://triport.io/public/robinhood — no key, but the budget is shared and a wallet polls, so it is for trying the network, not for daily use;
• the keyed URL https://triport.io/r/<API_KEY>/robinhood — your plan's limits, and the key is stored in the wallet;
• the network's public RPC https://rpc.mainnet.chain.robinhood.com — no key, rate-limited and not meant for production.

A keyed Triport URL without its key fails when the wallet checks the network, because the eth_chainId call it makes is answered with 401. The Robinhood Chain network config page has the full set of values for MetaMask, viem, ethers, Hardhat and Foundry.

When a keyless endpoint is enough

• A one-off script, a local experiment or a balance check.
• Traffic that is occasional, with no need to plan against a request rate of your own.
• Nothing that depends on subscriptions or a resumable feed with an explicit gap signal.

Once traffic is steady, or you need those surfaces, move to a key: Quickstart and Migrate from a public RPC.

Notes

• The testnet (chain ID 46630) is not proxied by Triport; the network publishes its own testnet endpoint — see External ecosystem.
• Error shapes, batch accounting and the 4 MiB body ceiling of the keyed endpoint are documented in Limits and Errors.