Onboarding and launch planning
Agree the product, commercial and operational details before opening trading to users.
Start by describing your product, intended users and launch regions to CRISP. Then agree the fee program, enabled capabilities and operating arrangements. Your team can explore the offline SDK example while live access is being arranged.
Decide how your product will operate
| Topic | What to establish |
|---|---|
| Product and identity | Your brand, login method, stable user IDs and account lifecycle |
| Revenue | Total program rate, buy/sell charging, CRISP allocation and your treasury allocation |
| Referrals | Number of levels, each level's rate, attribution rules and end-user disclosures |
| Funds | Treasury address on Polygon, deposit/withdrawal experience and payout policy |
| Staff | Initial dashboard owner, operators and analysts |
| Audience | Approved regions, eligibility controls and any verification requirements |
| Operations | Expected traffic, support contacts, recovery process and launch timing |
Read fees and revenue and referrals before choosing rates. The total collected fee and your net income are different amounts.
Obtain environment access
Production uses https://partner-api.crisp.trade, with routes under /v1.
CRISP supplies your production API credentials through a secure channel and enables
the agreed features. Tell us which features you need; CRISP manages the underlying
permission scopes. Withdrawals require explicit enablement.
CRISP does not provide a test environment. The Polymarket integration uses mainnet; there is no Polymarket testnet for this integration. The downloadable SDK quickstart includes an offline mock for validating your code without funds. It is not a sandbox, does not simulate venue settlement, and has no resettable hosted test data. Any live account, order or transfer uses production services and may involve real funds.
The Node.js SDK is licensed under Apache-2.0, permitting commercial use, modification and redistribution under that license. The SDK download includes the full license. Hosted API access, service fees, trademarks and Polymarket data rights are separate. Direct HTTP integrations are also supported. See SDK setup and HTTP setup.
Configure your launch
Your organization’s owner can manage exact production and staging realtime origins in the Partner Dashboard under Trading → Realtime browser origins. Use account sync for application updates, or the account-updates cursor API for backend consumers. Agree event retention and replay support for your operational needs. Webhooks are not part of standard onboarding; share any server-to-server automation requirement with CRISP for separate assessment.
Provide your treasury destination and confirm fee disclosures before collection is enabled. CRISP provisions the collection wallet; you do not supply its signing keys. Assign a dashboard owner and verify that your team can see your organization and the agreed configuration.
Eligibility, terms and recovery
Your organization handles geoblocking and KYC separately where required. CRISP's Partner API does not provide end-user geolocation enforcement or a KYC-document workflow. Your application must implement the checks required for your users and jurisdictions; do not use your backend's location as the user's location. Venue restrictions still apply.
Establish your end-user terms, privacy responsibilities, fee consent, verification requirements, liability and data-retention arrangements before launch.
Agree support for outages, account closure and remaining funds. The current managed-wallet API does not provide an independent end-user key-export or outage-withdrawal feature. See wallets and recovery boundaries.
Capacity and service arrangements
The authentication guide lists current default request limits. These budgets are shared across your keys, and bursts and concurrency controls also apply. Confirm your actual allocation before a load test or traffic increase.
Agree any SLA, support response targets, maintenance windows, incident notices, additional commercial charges and minimum-volume commitments explicitly. Implementation defaults and a working integration are not contractual promises.
Validate the complete user journey
Use the technical launch checklist to verify account creation, funding, trades, referral attribution, claims, withdrawals and recovery. Your business review should also confirm that users see the correct rates, missing-upline behavior, pending-versus-paid rewards, custody disclosures and support route. Validate reconciled treasury income in the dashboard rather than using gross fee collections as revenue.
Complete the agreed launch review with CRISP, then open the approved capabilities to users. The dashboard and operations guide describes the controls your team uses after launch.