In RPC mode, you submit a fully user-signed transaction to a dedicated nexroute endpoint. nexroute acknowledges synchronously and routes the transaction through private partnerships for fast, private inclusion. Where on-chain opportunities exist, a backrun is appended atomically behind the user’s transaction. This is one of two integration modes for Capture. Pick RPC mode when you already produce a fully signed user transaction and want privacy, delivery, and backrun in one move. For an alternative where the backrun lands inside the user’s own transaction, see Embedded mode.Documentation Index
Fetch the complete documentation index at: https://docs.nexroute.io/llms.txt
Use this file to discover all available pages before exploring further.
What you get
- Private execution: submitted transactions never enter the public mempool
- Guaranteed delivery: every acknowledged transaction is forwarded. Internal failures fall back to direct routing, never a silent drop
- Backrun monetization: where on-chain opportunities exist, nexroute appends a backrun behind the user’s transaction; otherwise the transaction is delivered alone
- Low-latency routing: super-fast inclusion through private partnerships
How it works
- You sign a user transaction in your normal flow
- You POST it to your dedicated Capture endpoint as a standard
eth_sendRawTransactionJSON-RPC request - nexroute responds immediately with the transaction hash
- nexroute evaluates the transaction for backrun opportunity and forwards through private partnerships
- The transaction lands on-chain; if a backrun was found, it lands atomically behind it
Reporting
A per-transaction explorer and aggregated reporting dashboard for inclusion status and partner activity is in active development. Contact nexroute for the current status.Get started
Quickstart
Submit your first transaction to your Capture endpoint.
Authentication
How endpoints are secured per partner.
Security
Privacy and integrity guarantees.
Rate Limiting
Burst handling and capacity behavior.