Migrating from Bitquery
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://graphql.bitquery.io+ 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
Token identity, not equity mechanics
Stock tokens are decoded as tokens with symbols and trades. The corporate-action taxonomy, multiplier series and pause windows are not exposed as queryable entities.
No point-in-time multiplier
Balance history is served as raw amounts, so historical valuations carry the same arithmetic error as the rest of the market.
No consolidated sequencing
Trades are queryable per venue and per pool. There is no monotonic cross-venue tape sequence, so two consumers replaying a range can disagree on order.
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 Bitquery 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
Bitquery's breadth across 40+ chains is real, and their unified schema is genuinely good engineering. For cross-chain analysis, or for AML and money-flow work, they do things we have no plans to build.
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.