FRB fee policy explains the 20% net performance fee model and dispute process.
FRB Agent is free to download and use. A 20% fee applies to qualifying net profitable executed trades where the on-chain fee logic applies. This page outlines how fees work, how to dispute errors, and what risks remain.
Linkable summary
Fee policy at a glance
FRB is free to use. A 20% fee applies to qualifying net profitable executed trades where fee logic applies. Gas, slippage, failed transactions, and market losses can still occur.
Performance Fee Model
FRB charges a 20% fee on qualifying net profitable executed trades where fee logic applies. The fee split is intended to be visible on-chain where supported. If an execution is net losing, no FRB performance fee applies, but gas, slippage, failed transactions, and market losses remain possible.
Simulation Mode (Free)
You can test strategy logic in Simulation Mode before live execution. It does not move live funds, but simulated outcomes can differ from real execution because of latency, liquidity, gas, and competing searchers.
Fee Disputes
Since fees are automatically calculated on-chain, all fee splits are verifiable on public block explorers. If you believe a fee was incorrectly charged, contact support@ai-frb.com within 48 hours with your transaction hash and wallet address for review.
How to request a review
- Collect your invoice ID, account email, and a short description of the issue.
- Email support@ai-frb.com within 48 hours.
- We confirm receipt within one business day and respond within five business days.
All requests are logged in our ticketing system for auditability. Approved adjustments appear on the next statement.
What is disputable?
- Fee charged on a trade that was not actually profitable (after gas costs).
- Smart contract miscalculation confirmed via on-chain verification.
- Fraudulent activity confirmed via our risk review.
All fee splits are recorded on-chain and fully transparent. We encourage users to verify transactions on public block explorers and use Simulation Mode to test before going live.
Example timeline
- Day 0: Customer notices duplicate charge and emails support.
- Day 1: Support acknowledges receipt, requests invoice ID + screenshot.
- Day 3: Billing team confirms issue and issues reversal; customer receives written confirmation.
Keep these timestamps in your internal compliance log to prove timely responses.
Finance & localization checklist
Keep your internal billing workspace tidy by pairing this FRB refund policy with the artifacts finance and compliance typically request.
- Store invoices plus SHA-256 verification screenshots next to this policy so auditors see both commercial and technical evidence.
- Link to the pricing page, support, and Knowledge Base entries referenced in your ticket.
- Document any translated summaries inside your own wiki; FRB currently publishes English-language policies only.
These habits keep refunds, invoices, and MEV governance conversations anchored inside ai-frb.com without mixing them with unrelated tax portals or external references.
Put the FRB refund policy to work
Loop in the right teams by pairing this policy with the links below before you request adjustments or escalate tickets.
Need help with the FRB refund policy? Email support@ai-frb.com FAQ entry when opening a ticket.
Related FRB resources
- Support & SLA for ticketing expectations.
- Telemetry policy and security overview if refunds stem from technical incidents.
For ecosystem context
Ecosystem research: how FRB's telemetry and policies fit next to Flashbots and Blocknative