Migrating from Alchemy
Both endpoints speak standard JSON-RPC over HTTPS and WebSocket, so ethers, viem and web3.py need no code changes. Everything we add is additive.
The change
- RPC_URL=https://robinhood-mainnet.g.alchemy.com/v2/YOUR_KEY+ RPC_URL=https://rpc.robinhoodrpc.io/v1/YOUR_KEYOur extra namespaces are additive — nothing you already call changes shape.
Run both in parallel and diff the responses before you cut over. Our free tier makes that cost nothing.
What you gain
No trace namespace on this chain
Alchemy's own Robinhood Chain documentation lists Trace API as unsupported. There is no plan tier that adds it.
No full debug namespace
Only debug_executionWitness and debug_executionWitnessByHash are available. debug_traceTransaction is not.
No simulation, no gRPC
User-operation simulation and gRPC are both listed as unsupported on Robinhood Chain, alongside the transaction-receipts and block-timestamp APIs.
Nothing equities-aware
The Token API returns ERC-20 metadata. It does not model the uiMultiplier, so historical balances are raw and portfolio values are wrong across any split or dividend.
Evaluate before you commit
Get a key
Sign up and copy your key. RPC is free, so this costs nothing to evaluate.
Change one line
Replace your Alchemy endpoint with ours. Both speak standard JSON-RPC, so ethers, viem and web3.py need no code changes.
Run both in parallel
Mirror traffic and diff the responses. For standard eth_* calls they should be identical.
Test the pre-split block
Ask both providers for a wallet's position value at a block preceding a corporate action. This is the test that separates them.
When to stay
If you are already standardised on Alchemy across several chains and need account abstraction — the bundler and gas manager are real products we do not offer — the operational simplicity of one vendor may outweigh the missing namespaces. If you never trace a transaction, the gap costs you nothing.
Gotchas
Our namespaces are additive: nothing you already call changes shape. The one behavioural difference worth knowing is that historical portfolio queries require an as_of parameter and will return 400 without one, rather than quietly answering with today’s multiplier.