> For the complete documentation index, see [llms.txt](https://docs.lighter.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lighter.xyz/trading/rfq.md). # RFQ Trade all markets in size, even when visible liquidity is limited. RFQ lets traders submit large order interest directly to market makers, who can provide liquidity within 10 seconds. RFQ orders are subject to a 1 bps fee for Standard Accounts. #### **How it works** RFQ is open to all traders and all markets, both perpetuals and spot. The RFQ option appears in the order panel when any of the following conditions are met: * Estimated slippage exceeds 0.1%, and the order’s notional value is at least $10,000. * The order book cannot fully fill the order. * The order’s notional value is at least $500,000. Maker Makers will only see the requested size, not the trade side, and can choose whether to provide liquidity. If a quote is provided, an estimated execution price and slippage will then be shown within 10 seconds, allowing you to decide whether to execute the trade. Your execution window is 2 minutes, but the quote can be dynamically adjusted based on price movements. Market makers must be whitelisted to respond to RFQs: [request here](< https://t.me/lighter_customer_bot?start=rfq_docs>). ## Developer guide For REST and WebSocket integration, including market-maker, requester and integrator workflows, see the [RFQ developer guide](https://docs.lighter.xyz/developers/integration-guides/rfq). --- # 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://docs.lighter.xyz/trading/rfq.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.