> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rook.pm/llms.txt
> Use this file to discover all available pages before exploring further.

# Combo interpretation

> Understand one combined payout under a supported settlement convention.

A Combo or parlay is one combined obligation. Its payout is not the sum of independent leg payouts. Rook analyzes listed Combos and newly composed tickets using supported venue settlement rules.

## Compose an analytical market

[`POST /markets:compose`](/api-reference/compose-market) requires at least two selected legs, a venue and a supported `settlement_convention_id`.

```json theme={null}
{
  "client_reference": "rfq_cut_no_hold",
  "venue": "polymarket",
  "settlement_convention_id": "demo_all_legs_win_v1",
  "legs": [
    {
      "outcome_id": "out_fed_dec_2026_cut_yes"
    },
    {
      "outcome_id": "out_fed_dec_2026_hold_no"
    }
  ],
  "scenario_pins": [
    {
      "family_id": "fam_fed_dec_2026",
      "scenario_version": "1"
    }
  ]
}
```

The convention above is illustrative. An integration must select an actually supported venue/product convention; there is no default product-of-legs assumption.

## Keep exceptional settlements

Voids, cancellations, pushes and product-specific exceptions can change how a ticket pays. Unsupported rules fail explicitly. Relationship findings can explain impossible or redundant legs under the supported scope.

The response returns a private analytical market for your account, coverage, versions and findings. It does not fabricate a venue listing, create a tradable instrument at the venue or submit an order.

## Cross-family tickets

When a Combo couples several families, its columns use compatible joint scenario tuples. It is not duplicated into separate additive family rows. Exact extrema and vectors require supported bounded joint analysis; oversize or unsupported scope is rejected explicitly.

Use the resulting outcome reference in [payout queries](/guides/payouts) or [candidate evaluation](/guides/exposure), then pass quoting and execution to your desk's venue or broker integration.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.