Read Core Concepts first if you have not.Everything below assumes you know what a pod and a trader are, and the setup makes considerably more sense with that in hand.
1. Create a pod
A pod is a segregated book of capital. Everything else attaches to one. Create your first pod in the Platform and name it after whatever it represents: a strategy, a desk, a client book. Its wallet is provisioned automatically and belongs to the pod permanently. If you are not sure how to divide things up, start with one pod. Adding more later is straightforward; splitting a book that has been trading is not.Pods
How to think about pod structure, and what belongs to a pod.
2. Fund it
Each pod has its own deposit address. Send USDC to the address shown on the pod’s detail page and the balance credits to that pod. There is no organization-level balance that you then divide. Capital arrives at a pod and belongs to it. Kalshi works differently. You fund your Kalshi account directly at Kalshi, because our credentials there are trading-only and cannot move money. See Deposit.3. Connect your venues
On-chain venues need nothing: the pod’s wallet is already in place, and funds are bridged to venue deposit addresses automatically. For Kalshi, an administrator connects your organization’s Kalshi account once, and pods trade through it. The account is KYC’d to your entity, so it is yours to supply.Venues
How each venue connects, and what separation between pods looks like.
4. Whitelist a withdrawal address
Do this now rather than when you need it. Funds can only be withdrawn to an address whitelisted in advance, and whitelists are maintained per pod. Adding the destination at setup means a withdrawal later is one step instead of two.5. Add traders
A trader is a person on your desk. Add them to your organization as a trader, then to the pod. Each person you add is a member, and the role you choose decides where they sign in: admins at app.parlayx.com, traders at trade.parlayx.com. That is all an admin does. The trader signs in to the trading platform and trades the pod from there. Until they are on a pod they can sign in but not trade. Trading through the trading platform needs no key. If a trader will integrate programmatically, allow them to create API keys. They create one per pod from the trading platform: an Ed25519 keypair generated in their browser, the public half registered with ParlayX, the private half shown to them once. It never leaves their systems, and nothing is sent between people. Each key is bound to one trader and one pod, and that binding is fixed.Traders and Permissions
What a trader can do, and how to withdraw access.
6. Check the pod is ready
The pod’s readiness strip shows four states. All four must be green before it can trade.
A pod that is not venue-ready rejects orders rather than routing them somewhere unintended.
7. Trade
Through the trading platform, or through the API. If you are integrating programmatically, start by callingwhoami. It is the smallest signed request you can make, and a successful response confirms your signing implementation works before you build anything on top of it.
Authentication
How to sign a request, and what gets checked.
API Reference
Endpoints, parameters, responses.
Then
Portfolio and positions
Orders, fills, exposure, and P&L across every pod.
Market mapping
The same outcome, aligned across every venue that lists it.
Transfer funds between pods
Moving Kalshi cash from one pod to another
Common questions
What we get asked most by funds and desks.