Integration overview

What you build

Three things. Everything else, catalogue, pricing, history, localization, portfolio, early exit, resolution, sits on Predicta's side.

1. 1

   Identify the user

   One server-to-server call maps your user to a Predicta session. Predicta never authenticates end users and never contacts them.

2. 2

   Place the vertical

   An embedded surface that wears your brand, or the API directly if you build your own front end.

3. 3

   Receive settlement

   A webhook endpoint for resolution and position events, so your ledger stays authoritative.

Who owns what

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

1. 1User opens Predictions inside your product
2. 2You identify the user to Predicta
3. 3Predicta maps the user to a prediction wallet or account
4. 4User selects a market
5. 5Predicta returns an executable quote with an expiry
6. 6User authorises the trade
7. 7Predicta routes to an eligible venue
8. 8Venue fills the order
9. 9Predicta records the fill and the position
10. 10Portfolio updates
11. 11Venue resolves, or the user exits early
12. 12Predicta 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

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

Predicta charges a platform fee on the transaction, configured per partner, with revenue share back to the platform as a distribution channel. Predicta 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.