Market Creation
Create clear markets that players and support teams can understand
A good listing and market are easy to find, easy to understand before a player orders, and easy to resolve after the real-world event is known.
Do not publish a listing until the listing title, market question, claims, close time, and resolution rule all agree with each other.
Publish only resolvable markets
A market is ready only when support can explain it, operators can resolve it from the published rule, and players can understand the outcome choices before ordering.
Creation Flow
Build the listing
The iframe is listing-first. Players browse a listing card or page before they choose a market.
Before creating markets, decide:
- What player-facing page this prediction belongs to.
- Where the listing should appear in player-facing discovery.
- Whether the listing should be public, unlisted, or private.
- Whether the listing needs one market or several related markets.
- What image, description, and support text help players understand the event.
The market should feel like a natural action on the listing, not a disconnected trading object.
Make the required decisions
| Decision | Operator guidance |
|---|---|
| Listing title | Name the event or prediction page players are opening. |
| Market question | Ask a single clear question. Avoid jokes, vague wording, or multiple conditions. |
| Claims | Make side A and side B mutually exclusive and complete. |
| Close time | Close before the event or data point can be known. |
| Resolution rule | Name the source of truth and exactly what value or event decides the outcome. |
| Discovery placement | Put the listing where players will naturally look for it. |
| Image | Use an image that supports the market without implying a different rule. |
What the market does not configure
Every market is a binary order-book market. The trading engine, currency, order limits, and tick size are not set when you author a market:
- Trading engine is operator-level configuration, applied forward-only to venues opened after a change.
- Currency and order limits are inherited from the operator's per-currency configuration (one venue per operator, environment, and currency).
- Tick size is a fixed platform constant of
0.01: limit prices sit on the0.01to0.99probability grid.
Review before publishing
Review the market as if you were a player seeing it for the first time:
- Can the player understand what they are predicting?
- Are the possible outcomes complete?
- Is there a clear moment when trading should stop?
- Is the source of truth named clearly?
- Would support know how to explain the result?
- Could the market become unfair if the real-world event changes?
For listing setup, also confirm the selected placement matches how players will browse. A technically correct market can still fail if players cannot find it or misunderstand why it appears where it does.
Multiple Markets on One Listing
Use multiple markets when players naturally expect related predictions on the same event page.
Good examples:
- Match winner, total goals, and first scorer on one match listing.
- BTC close direction, price range, and volatility on one daily crypto listing.
- Election winner, turnout, and margin on one election listing.
Avoid grouping unrelated markets only because they share an internal campaign or reporting code. Players should understand why the markets are together.
Good Market Wording
Prefer wording that makes the resolution path obvious:
| Weak | Better |
|---|---|
| BTC up today? | Will BTC close above its previous daily close on the named price source? |
| Team A wins? | Will Team A win the scheduled match against Team B on the official result? |
| Will it rain? | Will the named weather source report measurable rain in the selected city on the selected date? |
Launch Checklist
Before promoting a market:
- The market appears in the intended player-facing discovery.
- The operator's currency limits and risk settings suit the expected demand.
- The resolution owner knows when and how to resolve it.
- Support can find the market and understand the rule.
- Compliance and responsible gaming requirements are satisfied.
Common Mistakes
- Publishing a market whose title and resolution rule do not match.
- Letting trading remain open after the outcome is effectively known.
- Creating outcomes that do not cover the real result.
- Using a source that can change or disappear after settlement.
- Launching high-volume markets before the team understands the risk.