Questions, before you quote.

You do not need to choose a winner for every request. The engine starts with market prices and applies your rules. You do need to understand the exposure you are accepting: prices can be wrong, related outcomes can move together, and a book can lose money. Start by watching the Floor and learning what each limit controls.

You are taking financial risk on sports outcomes as the counterparty to a bettor. You keep the ticket's premium if the parlay loses; you lose the ticket's capital at risk if every leg wins. A margin above an estimated fair value is not a guaranteed profit. The math page explains both the estimated return and the possible loss.

You can explore the public Floor before funding. To quote, your account needs access, a ready wallet, and enough available collateral for its rules. Add funds shows the current minimum for each supported deposit option.

Choose dollar limits you can afford to lose. Total open risk limits simultaneous exposure; it is not a daily loss limit. Settled tickets can release room for new fills.

Preseason lets you explore real requests and the desk's controls before your account can quote. Eligible means a request passes the visible rules; it does not mean an order was sent or that it would have filled. Your access and engine status appear beside Start quoting. An open browser, a funded wallet, or an included game does not start the desk.

Polymarket sends the parlay request to competing makers. A quoted price still needs acceptance and confirmed execution before it becomes a filled ticket. The Floor shows those stages separately.

1. Request arrives
2. Makers quote
3. Bettor accepts
4. Execution confirmed

Polymarket's RFQ flow ↗

For the house side of a standard fully collateralized parlay, capital at risk is the possible payout minus the premium. A $50 payout with a $10.50 premium puts $39.50 of your capital at risk, before fees. The engine checks available collateral and your limits before quoting. Several tickets can lose together, and repeated fills can produce losses beyond a single open-book snapshot.

Quoting uses the wallet assigned to your account on Polygon. Open Combo positions commit collateral on-chain; that capital is distinct from the available wallet balance. Open Account → Wallet & funds to see the wallet balance and deposit options. Your account's wallet arrangement determines signing and custody; an account wallet should not be mistaken for a self-custody guarantee.

The engine runs independently of your browser while the desk is enabled and its safeguards pass. Closing the page does not stop it. Limits constrain new quotes, and safety checks can halt the engine, but they cannot prevent every loss or detect every market problem. Use Stop quoting when you want to stop taking new exposure, then wait for the confirmed status.

Explore the Floor, sign in, and check your account's access. Review the selected sports, pricing mode, and risk limits. Fund only through the token and network shown in Add funds. When your desk is ready and you choose to start it, watch the confirmed engine status and incoming decisions. Filled tickets appear in the Sweat room, where you can pin them and follow shared outcomes. Settlement follows confirmed market results; it is not promised by a particular time.

1. Explore
2. Review rules
3. Check funds
4. Quote when ready
5. Follow tickets

Stop quoting asks the desk to stop submitting new quotes and cancel outstanding ones. The control shows Stopping until the server confirms the change. Previously filled tickets still carry risk and continue toward settlement; a stop is not a way to undo a fill. If the connection is unavailable, do not infer that the engine stopped from the button press alone.

A final score, a 100¢ market price, and a confirmed settlement are different things. The Sweat room uses confirmed ticket and market resolution data to move a ticket into Settled. A connection or reconciliation delay can postpone that update; the page shows its freshness and any delay. Open the ticket to inspect the known leg results. Refreshing prices alone cannot settle it.

The bell collects new confirmed fills, ticket settlement changes, and engine alerts observed in this tab session. Open an item to follow it, or use Mark all read. It is an in-app activity panel, not an email or phone push service. The ticket book remains the place to review the full set of tickets.

There is no universal profitable setting. Autopilot uses resolved auction evidence, your target auction win rate, and an economic floor. The pricing panel shows the engine's current targets or identifies the fallback when it lacks enough data. Manual control sets the base margin for each leg count; explicit team adjustments still apply. Neither mode guarantees a fill or a positive return. Compare prices, confirmed fills, fees, and realized results together.

First check that the engine is connected and quoting, then inspect the request's desk response. A submitted quote may lose on price, expire without acceptance, or fail to become a confirmed trade. Compare the pricing panel's target with its market evidence, and check whether limits or market-data gates are excluding requests. A lower margin can improve competitiveness, but changing price alone does not guarantee fills.

A request can be outside your sports, team, leg-count, or price rules; exceed available capacity; lack usable market data; contain detected related legs; or arrive too late to quote. The Floor explains visible rule failures. When no quote acknowledgment exists, Not quoted is not proof of a particular engine rejection. Open the request for the information actually available.

There is no fixed number. Request flow, selected markets, prices, available collateral, and your daily-fill limit all matter. A quiet desk is not necessarily broken. Review the decision feed and engine status before changing a limit; more fills also mean more exposure.

It excludes new parlays containing that team from your rules across games. It does not close existing tickets or remove their exposure. Check the rule-save status after changing a team, especially on a weak connection. The Teams panel also lets you set a dollar cap for that team's exposure.

Offset follows the market with your chosen adjustment, such as +2¢. Pin price fixes your chosen value until you clear it; it does not follow later market moves. These are pricing inputs, not display preferences. Inspect the shown market snapshot and the pin's age or drift, and return to Market to clear the override.

Costs depend on the trade, the account's fee terms, and the funding route. Autopilot includes the desk's configured fees in its pricing floor; Manual control does not automatically add them. Deposit minimums appear in Add funds. A historical ticket's fees are not a quote for your next trade: use current account and venue terms when evaluating a margin.

The engine multiplies fresh CLOB leg midpoints, after the books pass its spread, depth, freshness, and movement checks. Explicit market offsets or pins can replace those marks. In Autopilot, spread and measured adverse-selection reserves enter the margin floor separately. This is a model estimate, not a known true probability. Browser price animations do not replace the engine's quote-time inputs.

The engine rejects detected duplicate legs and legs sharing a game, event, or team instead of applying a same-game probability model. That gate does not prove every remaining outcome is independent. Different tickets can also share an outcome, so the Sweat room groups shared picks and the book view shows concentration.

Resolved auctions the desk entered, grouped by sport, leg count, fair-price band, and request size. A lost auction can reveal an accepted competing price; winning does not reveal an exact next-best price, so it is treated as censored evidence. Thin groups use bounded broader evidence or a fallback. The pricing console reports the engine's calibration rather than inventing a separate target in the browser.

Polymarket's current quote-submission window is 400ms. Pregame checks the request's absolute deadline and reserves time for delivery; a late request is skipped. A historical response time is not a latency guarantee.

Polymarket's maker documentation ↗

Money uses integer micro-dollars: $1 = 1,000,000 units. For a BUY request expressed as notional, the engine derives shares from notional divided by price, then computes collateral from shares × (1 − price), with explicit rounding and final risk checks. Caps can reduce the quoted size. The ticket displays confirmed premium and capital at risk; rounded screen figures are not fed back into order sizing.

The engine combines market-data gates, request deadlines, exposure checks, and revaluation of outstanding firm quotes. Autopilot's floor includes configured costs and risk reserves, including measured adverse selection and spread. Manual control bypasses automatic pricing additions, while the execution safeguards remain. These controls reduce specific risks; they cannot establish that every accepted quote has positive expected value.