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.
Polymarket
The largest prediction market by volume, running on Polygon. Fully supported across every Bravado product.
Predict.fun
Supported for a subset of Bravado products. See the coverage table before you build.
How prediction markets work
The mechanics are broadly the same across venues, which is what makes a shared API possible.1
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.
2
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.
3
Outcome tokens trade
Tokens trade freely against collateral. Prices sit between 0 and 1 and behave as implied probabilities.
4
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.
5
Winning shares redeem
Holders of the winning outcome redeem at $1 per share. Losing shares are worth nothing.
Product coverage by venue
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 for venue rules.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.
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.