Builder Types & Integration
Every builder uses the same builder code. What differs is how users are onboarded and who places their orders.
Builder types
| Builder type | Use case | Who places orders | Typical integration | What you'll use |
|---|---|---|---|---|
| Wallets | Trade every TxFlow market without leaving the wallet | The user, from your wallet UI | ~2 weeks, full | REST API |
| Trading apps and terminals | Pro terminal, mobile app or aggregator on TxFlow's order book | The user, from your interface | ~1 week, light | REST + WebSocket |
| Bots, Telegram apps and AI agents | Strategies, copy trading, chat or agent-driven trading | Your agent, on the user's behalf | ~1 week, light | REST + WebSocket |
| Institutions and brokers | Route client flow at scale | Your platform | Case by case | Custom integration |
Integration depth
| Depth | What you build | Typical effort |
|---|---|---|
| Light | Add your builder code to an existing trading flow | ~1 week |
| Full | Approval UI, deposits, withdrawals and fee display | ~2 weeks |
Wallets
Enable users to trade across all TxFlow markets without leaving your app, while they keep control of their keys.
User flow
- Connect wallet. The user's wallet address is their TxFlow account. No separate sign-up is required.
- Deposit funds. Transfer USDC to the user's TxFlow Perps account. See Gas-Free Deposit for details.
- Approve builder fees. The user signs
approveBuilderFeeonce from their main wallet to authorize your builder fee. - Authorize trading. The user signs a one-time, gasless authorization (
approveAgent) so your app can place orders. - Place orders. Your app submits orders with your builder object attached.
- Withdraw funds. The user withdraws funds from their Perps account back to their wallet.
Steps 2–4 must happen in this order — see Set up an account.
Approval screen
The approval happens in your wallet's own signing UI. Before the user signs, show:
| Field | What to show |
|---|---|
| Builder | Your app or platform's name and builder address |
| Max fee rate | The highest rate you may charge, for example 0.05% |
| Trading permission | What your app can do on the user's behalf |
| Duration | Permanent until the user revokes it |
Fee display
Show the TxFlow trading fee and your builder fee as separate lines in your trade ticket. On spot, the builder fee is charged on sells only, so a buy ticket should show no builder fee — see Spot: sell fills only.
Trading apps and terminals
Build a trading terminal, mobile app or aggregator on TxFlow's order book — without running a matching engine or holding user funds.
| You build | TxFlow provides |
|---|---|
| Interface, charts, order entry | Order book, matching, margin and liquidation |
| User onboarding and fee display | Settlement and custody on TxFlow L1 |
| Your own features (alerts, analytics, strategies) | Market data across all TxFlow markets |
Integration steps
- Read market data from the TxFlow API — the Info API and WebSocket API.
- Onboard users: connect wallet, deposit, enable trading. See Wallets for the full flow.
- Ask each user to approve your builder fee once.
- Add your builder object to every order.
- If a user hasn't approved you, prompt them to approve before routing, or route without a fee.
Aggregators: attach your builder code to every order you send to TxFlow. Each user approves you once, regardless of how many TxFlow markets they trade.
Bots, Telegram apps and AI agents
Build trading bots, copy-trading tools, Telegram trading apps or AI agents on TxFlow. Users authorize once, your service places orders on their behalf, and you earn builder fees on every fill.
| Signature | What it allows | Who can grant it |
|---|---|---|
approveBuilderFee | You charge a builder fee up to maxFeeRate | The user's main wallet only. Agents cannot grant it |
Enable trading (approveAgent) | Your agent places and cancels orders for the user | The user's main wallet |
Integration steps
- Direct users to a signing page to connect their wallet.
- Collect both signatures — builder fee approval, then trading authorization — clearly displaying the fee rate and the agent's permissions.
- Attach your builder object to every order your agent submits.
- Display builder fees on each trade confirmation in your chat or dashboard.
Institutions and brokers
For brokers, large wallets, exchanges and distribution partners routing client flow at scale.
| Standard builders | Institutions and brokers | |
|---|---|---|
| Onboarding | Self-serve testnet, then mainnet application | Direct with the TxFlow BD team |
| Commercial terms | Program tiers | Bespoke terms available |
| Support | Docs and community channel | Dedicated BD contact |
| Verification | Not required at entry level | Entity verification required |
Custodial products: if your platform holds client funds, a separate integration path is available. Contact the TxFlow BD team before you start building — apply as a builder.
Treasury: builder addresses must be EVM externally owned accounts. Multi-sig and contract addresses are not supported, so claim to the builder address and then transfer to your treasury.