A Request for Quote (RFQ) is a trading protocol where a market participant solicits firm, executable price quotes for a specific instrument and quantity from multiple competing liquidity providers simultaneously. Unlike a central limit order book, the RFQ model is a negotiation mechanism where the requester retains control over trade execution, accepting or rejecting quotes based on price competitiveness.
Glossary
Request for Quote (RFQ)

What is Request for Quote (RFQ)?
A trading protocol where a buyer or seller solicits executable price quotes for a specific instrument and quantity from multiple liquidity providers, common in fixed income and OTC derivatives.
RFQ is the dominant execution protocol in over-the-counter (OTC) derivatives and fixed income markets, where instruments are less standardized and liquidity is fragmented across dealers. The process creates a competitive auction environment, allowing the requester to achieve price discovery and best execution without revealing their trading intent to the broader market, thereby minimizing market impact and information leakage.
Key Features of RFQ Trading
The Request for Quote (RFQ) protocol is a negotiation-driven execution model distinct from continuous limit order book matching. It is the dominant mechanism for trading illiquid, bespoke, or large-notional instruments in over-the-counter (OTC) markets.
Bilateral Negotiation Protocol
Unlike anonymous order book matching, RFQ is a disclosed negotiation between a requester and a selected panel of liquidity providers. The requester broadcasts a specific inquiry—defining the instrument, direction (buy/sell), and notional size—to multiple dealers simultaneously. This creates a competitive auction for that specific block, allowing the requester to trade large sizes without revealing their full intention to the broader market and minimizing information leakage.
Quote Lifecycle & Firmness
An RFQ quote is a binding, executable price with a finite lifespan, not an indicative signal. The lifecycle proceeds through strict states:
- Inquiry: Requester specifies CUSIP/ISIN, quantity, and direction.
- Quoting Window: Dealers submit firm bids or offers, typically within seconds.
- Quote Firmness: Once submitted, a quote is irrevocable for a defined window (e.g., 30 seconds), meaning the dealer must honor it if the requester executes.
- Execution or Pass: The requester trades on the best quote or lets the window expire.
Relationship-Based Liquidity
Access to RFQ streams is permissioned and relationship-driven. A requester does not see quotes from the entire market; they only see prices from dealers with whom they have established a bilateral credit relationship and legal agreement (e.g., ISDA Master Agreement). This gatekeeping mechanism protects dealers from adverse selection by unknown counterparties and ensures that quoted prices are backed by a pre-negotiated credit line, making it the standard for credit-sensitive instruments like corporate bonds and interest rate swaps.
Last Look & Trade-Through Logic
A controversial but common feature in electronic RFQ platforms is the Last Look mechanism. After a requester accepts a quote, the dealer has a final, sub-millisecond window to reject the trade if the market has moved against them. This protects the liquidity provider from latency arbitrage but can disadvantage the requester. Additionally, unlike Reg NMS equities, RFQ markets often lack a strict trade-through rule, meaning execution is not guaranteed at the best available quote across all platforms, prioritizing relationship execution over strict price priority.
Protocol Automation & Auto-Quoting
Modern RFQ workflows are heavily automated through Auto-Quoting (AQ) engines. Instead of a human trader manually pricing each inquiry, algorithms ingest the RFQ request, calculate a price based on internal risk models, inventory, and market data, and stream a firm quote back within milliseconds. This enables dealers to handle thousands of daily inquiries across credit, rates, and FX without manual intervention, while embedding dynamic toxicity filters to detect and reject flow from potentially informed counterparties before quoting.
Streaming vs. Snapshot RFQ
The protocol bifurcates into two execution styles:
- Snapshot RFQ: A one-shot auction where the requester asks for a price, receives quotes, and decides to execute or pass. Common for large, block-sized trades.
- Streaming RFQ: Dealers continuously stream executable prices to a requester's screen, which are refreshed in real-time. The requester clicks to trade on a live stream, combining the negotiation aspect of RFQ with the immediacy of a central limit order book. This is prevalent in spot FX and government bonds.
RFQ vs. Central Limit Order Book (CLOB)
Structural comparison of the Request for Quote negotiation protocol against the continuous, transparent Central Limit Order Book matching mechanism.
| Feature | RFQ | CLOB | Hybrid RFQ-CLOB |
|---|---|---|---|
Matching Mechanism | Bilateral negotiation; dealer provides quote to specific requester | Continuous multilateral auction; anonymous matching engine | RFQ initiates negotiation; CLOB executes if no dealer interest |
Pre-Trade Transparency | Partial; quotes visible to requester only | ||
Liquidity Discovery | Discrete; requester contacts known counterparties | Continuous; full order book depth visible | Discrete then continuous |
Anonymity | Negotiable; requester identity known to dealers | Full pre-trade anonymity | Anonymous on CLOB leg; known on RFQ leg |
Primary Asset Classes | Fixed income, OTC derivatives, structured products | Equities, futures, listed options | Corporate bonds, some FX |
Execution Certainty | Firm quote; executable upon acceptance | Price-time priority; no guarantee of fill | Conditional on dealer response |
Typical Latency | Seconds to minutes | Microseconds | Variable; < 1 sec to minutes |
Information Leakage Risk | High; dealers see request details | Low; only aggressive orders reveal intent | Moderate; RFQ leg leaks intent |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Explore the operational mechanics and strategic applications of the Request for Quote protocol in modern electronic markets.
A Request for Quote (RFQ) is an electronic trading protocol where a buyer or seller solicits executable, firm price quotes for a specific financial instrument and quantity from multiple competing liquidity providers simultaneously. Unlike a central limit order book, the RFQ process is a bilateral negotiation mechanism initiated by the requester. The workflow proceeds as follows: the initiator broadcasts an anonymous or disclosed inquiry containing the instrument identifier, direction (buy/sell), and notional quantity to a selected panel of dealers. Each dealer responds with a binding two-way price (bid and offer) within a defined time window. The requester then has the option to execute against the best quote or decline all responses. This protocol is the dominant execution method for over-the-counter (OTC) derivatives, corporate bonds, and structured products where continuous liquidity is fragmented.
Related Terms
Core concepts that interact with or define the mechanics of the Request for Quote (RFQ) protocol in modern electronic trading.
Bid-Ask Spread
The difference between the highest bid and lowest ask quoted in response to an RFQ. In OTC markets, this spread reflects the liquidity provider's compensation for inventory risk and adverse selection. A wider spread signals lower liquidity or higher volatility for the requested instrument.
Adverse Selection
The risk that the RFQ initiator possesses superior information about the asset's true value. Liquidity providers must model this probability when quoting, as a quote accepted too quickly may indicate they underpriced the risk. This is the primary cost component in RFQ-driven markets.
Dark Pool
A private Alternative Trading System (ATS) where pre-trade prices are hidden. Institutional investors often use RFQ protocols within dark pools to source liquidity for large blocks without revealing their full trading intention to the broader market, minimizing information leakage.
Toxic Flow
Order flow from a counterparty that is likely to be informed, meaning the price will move against the liquidity provider shortly after execution. In an RFQ context, dealers must assess whether a quote request originates from a toxic source and adjust their spread or decline to quote accordingly.
Smart Order Router (SOR)
An automated system that analyzes liquidity across venues. When an RFQ is broadcast to multiple dealers, a SOR on the buy-side can aggregate the responses and algorithmically select the best combination of quotes to achieve optimal execution, considering price, size, and counterparty risk.
Pre-Trade Risk Check
A set of automated validations performed before a quote is sent or an order is executed. In an RFQ workflow, this ensures the requested notional does not breach credit limits, the instrument is within the trading mandate, and the quote is arithmetically valid before being exposed to the counterparty.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us