Polymarket RFQ and Combo Maker Guide

Polymarket combo markets and RFQ tools are where prediction markets start looking less like a simple Yes/No click and more like a trade desk.

That does not mean the process has to be mysterious. It means the review has to be stricter. A combo can tie multiple outcomes together. An RFQ flow can ask makers for a quote instead of relying only on the visible order book. The edge is not in pressing buttons faster. The edge, if any, is in understanding exactly what is being quoted, what can go wrong, and where the execution controls are.

This page is educational. It explains the workflow, vocabulary, and review checklist. It does not tell you what to trade.

Key concepts in plain English

• ▸RFQ: Request for quote. Instead of only lifting displayed liquidity, a taker requests a quote and a maker can respond with executable terms.
• ▸Combo: A linked package of outcomes or legs that is meant to be evaluated together, not as one isolated binary market.
• ▸Maker: A participant or system providing quotes.
• ▸Taker: The participant requesting or accepting liquidity.
• ▸Leg: One component of a combo. If a combo has three legs, the weakest leg can control the real quality of the package.
• ▸Pre-execution control: A check that happens before any action, such as price bounds, max notional, balance checks, allowance checks, and cancel rules.

What Polymarket documents support

Polymarket's current docs and SDK notes reference combo markets, RFQ status, market-level parameters, combo market catalogs, and RFQ quoter sessions. The docs also reference CLOB market information fields such as tokens, tick size, base fees, rewards, RFQ status, and fee details.

That is the useful SEO answer: Polymarket is not only a list of simple markets. It also has infrastructure for more advanced market and builder workflows. But a reader should not jump from "advanced tools exist" to "the quote is automatically good." Every complex quote still needs a rules check, liquidity check, fee check, and exposure check.

The clean RFQ workflow

Use this simple sequence before you treat an RFQ or combo as actionable:

1. ▸Define the exact event. Write the market question and resolution source before reviewing price.
2. ▸List every leg. For a combo, each leg needs its own question, outcome, price, size, end date, and resolution condition.
3. ▸Check whether the legs share one driver. A sports combo, election combo, or macro combo may have correlated legs.
4. ▸Review visible liquidity anyway. RFQ does not make spread, depth, or slippage irrelevant.
5. ▸Set price bounds first. Know the maximum price or minimum acceptable execution before a quote arrives.
6. ▸Check fees and builder attribution. If a builder code or platform fee applies, model the full cost.
7. ▸Use a cancel rule. Stale quotes, moved news, or changed liquidity should pause the workflow.
8. ▸Journal the result. Save quote time, legs, prices, size, spread, reason, and exit/review plan.

Combo math example

Suppose a combo includes three event legs priced like this:

Leg A: 62%
Leg B: 55%
Leg C: 48%

The mistake is to average them and say the package is "about 55%." That may miss correlation, conditional probability, fees, and leg-specific resolution risk.

A better review asks:

What has to be true for every leg?
Which leg is the bottleneck?
Are the legs independent, related, or almost the same thesis twice?
What happens if one leg resolves differently from the headline narrative?
How wide is the effective spread after fees?
What is the maximum loss if the full package is wrong?

In prediction markets, clean math starts with clean definitions. If the legs are not clean, the quote is not clean.

Common mistakes

• ▸Treating an RFQ quote as automatically better than the order book.
• ▸Ignoring the weakest-liquidity leg in a combo.
• ▸Forgetting that related legs can create hidden concentration.
• ▸Failing to model fees, builder fees, or the bid/ask gap.
• ▸Accepting a quote after new information hits the market.
• ▸Reviewing the headline but not the resolution rules.
• ▸Building automation without a kill switch for stale quotes or access changes.

RFQ and combo review checklist

Market / combo name:
Date and time:
All legs listed:
Resolution source for each leg:
Current displayed bid/ask per leg:
RFQ quote received:
Quote expiration / freshness:
Size:
Estimated spread cost:
Platform / builder fee reviewed:
Correlation notes:
Max loss:
Exit or review trigger:
Cancel condition:
Journal link:
Decision: pass, watch, or act manually

The most important line is the last one. "Pass" is a valid decision. Not every complex quote deserves capital.

Where Bucko fits

Bucko is useful as the notebook around the trade, not a magic button. Use it to map legs, log assumptions, track quote quality, write down max exposure, and compare the result with the original thesis after resolution.

If you are eligible for the US app offer, use code BUCKO for a $50 deposit bonus on the Polymarket US app: https://www.poly.market/BUCKO. Confirm current app screens and offer terms before depositing.

Internal links

• ▸Read next: Polymarket combo markets guide
• ▸Review costs: Polymarket fees, spreads, and costs explained
• ▸Add controls: Polymarket API automation risk checklist

Sources and last-verified notes

Last verified: 2026-07-07 PDT.

Sources reviewed: Polymarket docs llms.txt and llms-full.txt; Polymarket CLOB market information docs; Polymarket SDK notes referencing combo market catalogs, RFQ quoter sessions, RFQ status, production combo RFQ endpoints, quote rejections, and pre-execution reservation failures; Polymarket public Gamma market samples for active category structure.