Your users do not care which RPC you use. They care that the buy landed, at the price you showed them, before the candle moved.
Ordo runs its own Robinhood Chain and Arc nodes in Chicago and Frankfurt, with one endpoint in front of them. It exists because the four ways a trading app loses a fill are all infrastructure, and all fixable.
A public RPC hands you a nonce from a node ten seconds behind the head. You sign, the sequencer refuses, the user sees a failure they did not cause.
We read nonces, balances and receipts from whichever node is at the head, checked every second.
An aggregator quotes, you sign with a wide slippage so it "never fails", and the difference is somebody else's profit.
Our router quotes the exact output, splits across pools when one is thin, and writes the floor into the calldata.
Approvals not yet mined, slippage already gone, a dead deadline: gas burnt on a transaction that could never succeed.
Every send is executed against current state first. If it would revert, it never leaves, and nothing is spent.
On chains with a public mempool, a big buy is a signal. Bots read it and sell it back to you.
Sends go straight to the sequencer's own ingress. No public relay, no mempool to read, no sandwich.
Those are today's numbers and they are checkable: status.ordofi.network measures every endpoint from your own browser, including how far each of our nodes is from the chain head, and publishes a week of availability measured from the other continent. If something is degraded when you look, it will say so.
Point your backend, your bundler and your wallet at https://rpc.ordofi.network (or arc.ordofi.network). Standard JSON-RPC, WebSocket subscriptions, full tracing, no key required to try it.
curl -s https://rpc.ordofi.network \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'
# {"jsonrpc":"2.0","id":1,"result":"0x1237"}
Protection is the default on eth_sendRawTransaction: simulate, refuse a revert, refuse a transfer to an address nobody controls, then deliver privately. Nothing to opt into, no separate method. If you want the raw behaviour for one call, you can ask for it explicitly.
One POST returns the best route across Uniswap V3, V4 and hooked pools, compared against the aggregators, with the output, the price impact, your own fee, and the calls ready to execute, including an atomic batch for an ERC-4337 smart account.
POST https://rpc.ordofi.network/swap/v1/build
{
"tokenIn": "0x0000000000000000000000000000000000000000",
"tokenOut": "0xfe2f0fb0c00d19786a8abf98d4b1f1ac8763b167",
"amountIn": "1000000000000000000",
"from": "0x<the user's account>",
"slippageBps": 50,
"appFee": { "bps": 50, "recipient": "0x<your fee address>" },
"simulate": true
}
Slippage is capped at 10% by design: a wider floor is the thing this API exists to end. With simulate: true the whole batch is run from the user's account before you sponsor its gas, and if it would fail you are told which call and why. Full reference.
Plans are published at app.ordofi.network/pricing: Free is 1,000 requests a minute, Builder $29 for 12,000, Pro $199 for 60,000, Dedicated $999 for 250,000. Anything above that, or anything that needs its own hardware, is a conversation rather than a page. There is no fee on swap volume and no charge per transaction.
Start on the free tier without talking to anyone; the endpoint above works right now, unauthenticated, from wherever you are reading this.
Or say hello: t.me/ordofi · @ordofi. If you tell us your peak requests per second and which methods you lean on, we will tell you plainly whether we can take you today or what we would have to add first.