How to evaluate MEV execution tools
There is no universally best MEV bot. The right fit depends on the chain, transaction workflow, custody model, execution route, and risks you can independently verify.
This page is a due-diligence guide, not a ranking. Products in this space serve different roles, and capabilities or terms can change. Confirm current details in each provider’s official documentation before relying on them.
A practical evaluation checklist
- Chain and venue
- Confirm the exact networks, protocols, and transaction types supported by the current release. Do not infer support from marketing labels.
- Custody and signing
- Find out where keys are created and stored, what process signs transactions, and whether an operator can withdraw or move assets.
- Execution route
- Identify whether the workflow uses a public mempool, private transaction endpoint, bundle relay, block engine, or your own RPC. These are not interchangeable.
- Simulation and failure handling
- Check what is simulated, against which state, and how reverts, stale quotes, missed inclusion, and fees are reported.
- Permissions and controls
- Review approval scope, revocation steps, spending limits, local logs, update provenance, and recovery procedures.
- Fees and terms
- Read current fee rules, eligibility, billing triggers, refund terms, and any provider or network charges in primary documentation.
- Evidence, not promises
- Ask for reproducible measurements with methodology and sample boundaries. Treat claims of no delay or certain transaction outcomes as red flags.
Compare like with like
A private transaction service, a bundle submission interface, and a desktop execution client solve different parts of a workflow:
- A private transaction endpoint routes an individual signed transaction to participating infrastructure; routing cannot ensure that a transaction lands or remove execution risks.
- A bundle groups transactions with ordering and validity conditions for a supported builder or relay path; acceptance and final inclusion are separate outcomes.
- An execution client helps an operator configure, inspect, simulate, and submit transactions; it may depend on external RPCs and execution providers.
For protocol behavior, consult primary documentation and verify the supported network and endpoint directly.
What FRB Agent does
FRB Agent is a non-custodial Windows execution assistant. Its documented product boundaries are:
- Signing keys remain local to the user’s environment.
- Simulation is part of the review workflow; it is not a guarantee that a later transaction will succeed.
- Private bundle workflows are available on supported routes and depend on the selected provider and network.
- Download and use are free; a 20% fee applies only to qualifying net-profitable executions where the fee mechanism applies. See the current pricing terms.
FRB does not guarantee profit, transaction inclusion, protection from every MEV strategy, or a particular latency. Check current release notes and route availability before use.
Method and limitations
This guide avoids ranking providers because a reliable comparison requires current, like-for-like evidence across the same networks, routes, transaction scenarios, and measurement period. Recheck official product documentation and terms when making a decision.
Editorial scope: Neutral evaluation criteria; no performance ranking or competitor pricing claims.
Review FRB for your workflow
Start with the setup and security documentation, then confirm that your network and execution route are supported.
Read the quickstart