Migrating from Tenderly
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.gateway.tenderly.co/ACCESS_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
Decodes to Solidity types, not financial ones
tenderly_decodeEvent turns bytes into typed Solidity values. It does not know that a UIMultiplierUpdated event changes what every holder's balance means.
No market data
There is no tape, no price reconciliation, no portfolio layer. Tenderly is a development tool, not a data vendor.
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 Tenderly 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
For contract development, debugging a failed transaction, or simulating before you sign, Tenderly's tooling is better than ours and we accept their tenderly_* method names precisely so you can keep using it. Many teams should run both.
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.