Every plan runs on the same node with the same private sends and protection. Paid plans add budget, throughput and priority. Priced in dollars. Paid in ETH or USDG on Robinhood Chain, never a card.
Robinhood Chain publishes its sequencer feed in Nitro's own framing, and there is no public mempool to watch instead. We hold one upstream connection, decode it once and fan it out, timestamped on receipt.
A request costs what it costs a node to answer. Most methods are one unit. The ones below cost more, and the schedule is the same on every plan, so a plan is only a budget and a speed, never a different price list.
| Method | Units |
|---|---|
Every eth_* and net_* read not listed below; eth_getBlockByNumber / ByHash without transactions; eth_call | 1 |
eth_feeHistory | 2 |
eth_estimateGas · eth_createAccessList · eth_getProof · ordo_simulate · eth_getLogs up to 100 blocks, or by block hash | 3 |
ordo_explain | 5 |
eth_getBlockByNumber / ByHash with full transactions | 6 |
eth_getLogs up to 1,000 blocks, or an open range · ordo_quoteSwap | 10 |
eth_sendRawTransaction · ordo_sendRawTransaction · ordo_sendPrivateTransaction · ordo_sendBundle (per transaction) | 12 |
eth_getBlockReceipts | 13 |
eth_getLogs up to 10,000 blocks | 25 |
eth_simulateV1 · debug_traceTransaction · debug_traceCall | 30 |
eth_getLogs over 10,000 blocks · debug_traceBlockByNumber / ByHash | 50 |
Anonymous wallet traffic is limited per IP and never billed. WebSocket subscription notifications are not metered.
Request units pay for reads. Execution is priced on what it protects: a share of the value each confirmed keyed transaction moves, charged when its receipt lands.
The fee is known only once a transaction confirms and its value is priced, so that is when it is charged, to the key's prepaid credit. Value is what the sender moved: ETH attached plus tokens transferred out. Nothing is skimmed on-chain and nothing is added to what your users sign.
Anonymous wallet traffic has no key and is never billed. Ordo Swap is separate: it pays the surplus from its own back-run back to the user and keeps a tenth of that surplus, never a share of the principal.
Where the fee goes: protocol revenue buys $ORDO on the open market, one public transaction at a time.
Three steps, no account with a card company anywhere in them.
Sign a message, no transaction, no gas. Your keys and plans live under that address.
On Robinhood Chain, from any wallet. Paste the transaction hash and the credit lands in dollars: USDG one to one, ETH at the price of that moment.
The fee comes out of your credit and renews every 30 days while credit lasts. Overage draws from the same credit. Run out and you are back on Free, nothing is cut off mid-period.
No. Add https://rpc.ordofi.network as the network RPC and every send is private and revert-protected. Anonymous traffic is limited per IP (3,000 reads and 60 sends a minute) and never billed. Keys are for apps, bots, indexers and terminals.
On Free, requests return -32005 with a message naming the plan and this page, until the calendar month turns. On a paid plan, requests keep flowing and the overage is drawn from prepaid credit at the plan's per-million rate. When credit is gone, the same -32005 tells you to top up.
0.05% of the value a confirmed transaction moves, charged to the key once the receipt lands: fifty cents on a thousand dollars, five dollars on ten thousand, nothing on an approval or a call that moves no value. There is no per-transaction charge, nothing is added to what your users sign, and anonymous wallet traffic is never billed.
Because a trace is not a block number. A method's unit cost reflects what it costs our node to answer, the same way every provider on this chain prices. The schedule is public above and identical on every plan.
Not yet. Both are on Robinhood Chain, where your users already are. There is no card, no invoice terms, no minimum.
Priority on our node for every request class, the highest concurrency on the log-scan lanes, 250,000 requests a minute, and a person to message. If you are building a trading terminal, this is the plan; talk to us before launch.
Not in writing yet. Availability, latency and every other number we publish are measured on the box that answers you and shown at /compare. A written SLA arrives with the second origin.
A key takes ten seconds and the first five million request units are on us.