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

# Supported Prediction Markets

> Bravado provides a single API surface across multiple prediction markets. Compare venue coverage and which Bravado products are available on each.

A prediction market lets people trade on the outcome of a future event. Each possible outcome is a token that settles at \$1 if it happens and \$0 if it does not, so the live price doubles as the market's implied probability, a share trading at `0.62` means the market collectively puts the outcome at about 62%.

Bravado connects to these venues so you integrate once instead of per-venue. The same order types, copy-trading engine, and analytics model apply across every supported market.

<CardGroup cols={2}>
  <Card title="Polymarket" icon="https://mintcdn.com/bravado/nm6Bs4I1Kmd-W087/logo/polymarket.png?fit=max&auto=format&n=nm6Bs4I1Kmd-W087&q=85&s=4ce81507f8cf81b627f57e3ed782dbfd" href="/markets/polymarket/overview" width="148" height="148" data-path="logo/polymarket.png">
    The largest prediction market by volume, running on Polygon. Fully supported across every Bravado product.
  </Card>

  <Card title="Predict.fun" icon="https://mintcdn.com/bravado/cHy7EauylyRcAcVI/logo/predict-fun.png?fit=max&auto=format&n=cHy7EauylyRcAcVI&q=85&s=76b47997dd7baeaa9e263f802a25b0f0" href="/markets/predict-fun/overview" width="400" height="400" data-path="logo/predict-fun.png">
    Supported for a subset of Bravado products. See the coverage table before you build.
  </Card>
</CardGroup>

## How prediction markets work

The mechanics are broadly the same across venues, which is what makes a shared API possible.

<Steps>
  <Step title="A market is created">
    An event is framed as a question with mutually exclusive outcomes, most commonly a binary YES / NO pair, though some markets have more.
  </Step>

  <Step title="Collateral is split into outcome tokens">
    Depositing one unit of collateral mints one full set of outcome tokens. Because exactly one outcome can be true, a complete set is always redeemable for the original collateral.
  </Step>

  <Step title="Outcome tokens trade">
    Tokens trade freely against collateral. Prices sit between 0 and 1 and behave as implied probabilities.
  </Step>

  <Step title="The event concludes and resolves">
    An oracle reports the outcome on-chain. This step is not instant, and on some venues it can be disputed.
  </Step>

  <Step title="Winning shares redeem">
    Holders of the winning outcome redeem at \$1 per share. Losing shares are worth nothing.
  </Step>
</Steps>

## Product coverage by venue

| Bravado product                          | Polymarket | Predict.fun                     |
| ---------------------------------------- | ---------- | ------------------------------- |
| [Trade API](/products/trade-api)         | Supported  | Supported (LIMIT, MARKET, TWAP) |
| [Copytrade API](/products/copytrade-api) | Supported  | Not available                   |
| [Combos API](/api/combos/overview)       | Supported  | Not available                   |
| [Data API](/products/data-api)           | Supported  | Not available                   |
| [UMA API](/products/uma-api)             | Supported  | Not applicable                  |

<Info>
  Predict.fun is supported through the Trade API v2 by adding `"venue": "predictfun"` to a request. It runs on BNB Chain with USDT collateral. See the [Predict.fun overview](/markets/predict-fun/overview) for venue rules.
</Info>

## What differs between venues

Most of the Bravado surface is venue-agnostic, but a few things are not:

* **Settlement asset.** Collateral differs by venue, which changes what balances and PnL are denominated in — Polymarket settles in pUSD on Polygon, Predict.fun in USDT on BNB Chain.
* **Resolution mechanism.** Polymarket resolves through UMA's Optimistic Oracle, including a dispute path. Other venues may resolve differently.
* **Market microstructure.** Minimum resting order size, tick size, and notional minimums are set per venue and per market, and rejections that come from those limits are venue rules rather than Bravado errors.

<Note>
  Venue-specific constraints are documented on each venue's own pages. When a request is rejected for a reason that is not obviously a Bravado validation error, check the venue's constraints first, see [Error reference](/reference/errors).
</Note>