Integration overview
What a platform builds, what Parity owns, and what runs today.
What you build
Three things. Everything else, catalogue, pricing, history, localization, portfolio, early exit, resolution, sits on Parity's side.
- 1
Identify the user
One server-to-server call maps your user to a Parity session. Parity never authenticates end users and never contacts them.
- 2
Place the vertical
An embedded surface that wears your brand, or the API directly if you build your own front end.
- 3
Receive settlement
A webhook endpoint for resolution and position events, so your ledger stays authoritative.
Who owns what
Your platform
- Customer relationship
- Account and balance
- KYC and AML on that account
- Brand, app and support
- Who may see the vertical
Parity
- Market catalogue and normalization
- Embedded UI and API
- Routing and execution orchestration
- Position abstraction
- Fee calculation and revenue share
- Venue integrations
Underlying venue
- Exchange liquidity and matching
- The underlying contracts
- Venue-side settlement
The final allocation of KYC, custody and regulatory responsibility depends on the commercial and legal structure agreed with each venue and on the jurisdiction you operate in. It is not a technical decision and this page does not settle it.
Order flow
- 1User opens Predictions inside your product
- 2You identify the user to Parity
- 3Parity maps the user to a prediction wallet or account
- 4User selects a market
- 5Parity returns an executable quote with an expiry
- 6User authorises the trade
- 7Parity routes to an eligible venue
- 8Venue fills the order
- 9Parity records the fill and the position
- 10Portfolio updates
- 11Venue resolves, or the user exits early
- 12Parity reports settlement back to you
Two properties hold throughout: the quote a user sees is the quote that executes or the order is rejected, and a retried submission returns the original fill rather than opening a second position.
What runs today
Live
- Continuous ingestion from multiple liquidity pools
- Tens of thousands of normalized markets
- Real prices, history and resolution rules
- Non-sports filtering from provider metadata
- Catalogue, portfolio, marks and early exit
- Settlement reconciliation with retry and review states
- EN / ES / PT with regional ordering
Not yet
- Authenticated execution: venue adapters are present and disabled
- Custody and real money movement
- Verified cross-venue routing equivalence
- Operator API authentication
On routing. Markets that appear on more than one venue are grouped by exact question match, and that grouping is a display fact: not a claim that the contracts are interchangeable. Two venues can word a question identically and still differ on cutoff time, resolution source or an edge case in the rules, so orders are never routed between listings on the strength of a matching title. Equivalence is tracked explicitly and starts unverified.
Economics
Parity charges a platform fee on the transaction, configured per partner, with revenue share back to the platform as a distribution channel. Parity does not take the other side of a user's position: the house-edge setting exists in the pricing pipeline because it must be expressible, and defaults to zero.
See it running
Live market data, simulated execution. No orders reach a venue and no funds move.
View live productPublic market-data access does not by itself grant commercial redistribution or execution rights. Production deployments require agreements with the underlying venues and jurisdiction-specific legal and compliance review.