> For the complete documentation index, see [llms.txt](https://www.aevo.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.aevo.xyz/docs/aevo-products/aevo-builder-codes.md). # AEVO BUILDER CODES ## **Build on Aevo, earn on every trade** Aevo Builder Codes let any application that routes trades to Aevo (a **builder**) earn a fee on the trades its users make. Trading terminals, bots, wallets, portfolio apps and AI agents can plug into Aevo's perpetuals and options markets and get paid for the volume they bring. Users stay in control. A builder can only charge a user after that user approves it, and never more than the maximum the user approved. *** ## How it works 1. **A builder registers.** Any Aevo account can register a builder in a few seconds. Aevo generates its `builder_id`, and the account becomes the builder's fee account. 2. **A user approves the builder** once, with a wallet signature that sets the maximum fee, for example 5 bps. 3. **The builder's app places the user's orders** with its `builder_id` and a fee rate at or below that maximum. 4. **On every fill,** the builder fee is paid by the user in USDC and credited to the builder's fee account, separately from Aevo's trading fee. *** ## Highlights * **Perpetuals and options.** Builder fees work on both. Option fees follow the same premium-based cap as Aevo's own option fee, so cheap options stay cheap to trade. See [Perpetuals vs Options Fees](/docs/aevo-products/aevo-builder-codes/perps-vs-options-fees.md). * **Per-order pricing.** Builders choose their fee on each order, within the user's approved maximum and Aevo's protocol cap: **up to 5 bps on perpetuals**, and **up to 3 bps on options, never more than 5% of the premium**. * **User-controlled.** Users see and revoke their approvals at any time under **Settings → Builders → Connected Builders**. * **Built-in analytics.** Builders get a dashboard and a reporting API for volume, fees, traders, markets and individual fills, with CSV export for reconciliation. * **Self-service.** No application or manual onboarding is needed to register a builder. *** ## Get started * **Building an app?** See [For Builders](/docs/aevo-products/aevo-builder-codes/for-builders.md). * **Trading through an app?** See [For Traders](/docs/aevo-products/aevo-builder-codes/for-traders.md). * **Integrating?** See the [Builder Codes API reference](/docs/api-reference/builder-codes.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.aevo.xyz/docs/aevo-products/aevo-builder-codes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.