CRISP for partners
Build a prediction-market product with your own brand, managed trading and configurable revenue sharing.
CRISP provides the managed trading layer for your prediction-market product. You own the brand, customer relationship and user experience. CRISP handles trading accounts scoped to your organization, execution, funding workflows, fee allocation and referral payout records behind your backend. Users sign in to your product; they do not need a CRISP login.
These docs serve product teams evaluating the partnership, operators running it, and developers building the integration. Start with the product model below or go directly to the technical quickstart. See terms used in these guides for the distinction between your organization, your team and your users.
What you can build
| Capability | What it means for your product |
|---|---|
| Your own brand and login | Keep your interface, user authentication and customer relationship |
| Managed trading accounts | Map each stable user ID to a provisioned wallet and venue account |
| Prediction-market trading | Browse markets and books, place and cancel orders, show positions and fills, and redeem positions |
| Deposits and withdrawals | Present supported funding routes, balances, transfer status and approved withdrawals |
| Configurable trading fees | Allocate eligible fees among your treasury, CRISP revenue and referral beneficiaries |
| Multi-tier referrals | Configure up to five levels, each with its own rate, with missing levels paid to your treasury |
| Your operations | Review users, volume, fees and payouts; assign staff roles and pause new orders |
| Live account updates | Refresh your interface with account sync; use account-update cursor reads for backend consumers |
The current public integration supports Polymarket. Availability depends on your enabled features. Commercial terms and launch regions are agreed during onboarding.
Understand how CRISP supports your product
Fees and your revenue
Referral program
Wallets and funds
Dashboard and operations
Market data and your brand
Plan your launch
How responsibility is shared
Your application authenticates users, records referral eligibility, collects user approvals and explains fees and market rules. Its backend authorizes every account action and keeps your API credentials private. CRISP maps accounts to your organization, manages signing and execution, and reconciles financial activity. The venue supplies markets, liquidity and settlement rules.
The Partner Dashboard is for your staff. The Partner API is for your backend. The optional Node.js SDK wraps that API and helps developers with signing, routing and account updates; it does not replace your product or user login.
Your branded app → Your authenticated backend → CRISP → Venue execution
↑ │
└──────── Account-scoped updates ─────────┘
Your operations team → Partner Dashboard → Reports and permitted controlsTrading and money movement have distinct acceptance and completion stages. A queued order is not a fill, accrued rewards are not paid rewards, and a source transfer is not final bridge delivery. The product guides explain what to show users; the technical guides provide the exact states and recovery flows.
Build your integration
For Node.js, use the official server-side SDK. Other backends can use signed HTTP requests with the same account and execution model.
SDK quickstart
Integrate with AI
Technical concepts
HTTP API
Start with market discovery to build your public browsing experience. Follow the task guides for accounts, funding, trading, referral integration and realtime. Examples offer SDK and HTTP alternatives; you do not need to implement both.
From evaluation to launch
- Understand the product, revenue, referral and custody model with your team.
- Agree your program, regions, support arrangements and environment with CRISP.
- Build and verify the end-to-end user journey in the approved environment.
- Review user disclosures, dashboard reporting and the launch checklist.
- Open the agreed capabilities to your users and monitor operations.
The offline example uses no funds. There is no hosted test environment; live integration uses production services. SLA and service access are agreed separately. The onboarding guide explains what to establish before moving from evaluation to live activity.