nexroute Capture is a backrun service for partner orderflow. It identifies MEV opportunities behind partner swap transactions and atomically attaches a backrun, monetizing flow that would otherwise leak to searchers, builders, or validators. Capture supports two integration modes. Pick the one that matches how your stack constructs and submits user transactions.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.
RPC mode
Submit a fully user-signed transaction to a dedicated nexroute endpoint. nexroute acknowledges synchronously, evaluates the transaction for backrun opportunity, and forwards the bundle through private partnerships. The partner-signed transaction is forwarded byte-for-byte; the backrun is a separate transaction signed by nexroute and bundled behind it. Recommended when feasible. Faster (one round trip from partner to nexroute, then direct dispatch via private partnerships), cleaner separation of concerns (the partner submits a raw transaction and nexroute owns the backrun), and privacy by default.Embedded mode
The backrun runs in the same on-chain transaction as the user’s swap. nexroute provides backrun calldata via API; the partner composes it into the user transaction. The user signs once (typically a Permit2 typed-data message), and the swap and backrun execute atomically. Use when RPC mode isn’t possible. The typical reason: the user’s wallet (or another party the partner doesn’t control) dispatches the transaction, so the partner can’t relay it through nexroute’s endpoint. The backrun API call sits in the user-facing critical path, and the partner takes on backrun integration in its own transaction construction. Privacy is the dispatcher’s responsibility; if mempool exposure is a concern, the dispatcher must use a private relay.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
RPC mode
Submit signed transactions to a dedicated private endpoint.
Embedded mode
Backrun inside the user’s own transaction.