For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
Join CommunityStart Trading
HomeOverviewTradingRisk & LiquidationsParadex ChainEcosystemREST APIWebSocket APIAgentic AI HubRelease Notes
HomeOverviewTradingRisk & LiquidationsParadex ChainEcosystemREST APIWebSocket APIAgentic AI HubRelease Notes
  • Getting Started
    • Overview
    • Privacy Perps
    • Trading Fees
    • Trader Profiles
    • Retail Price Improvement
    • FastFills
    • TradFi Markets
  • Spot Trading
    • Supported Order Types
    • Quoting & Settlement
    • Non-USDC Balances & Collateral
    • Naming Convention
  • Dated Options
    • Overview
    • Expiries and listing schedule
    • Mark price
    • Greeks
    • Margin requirements
    • FAQ
  • Orders
    • Placing Orders
    • Order Instructions
    • VWAP Price Protection for Market Orders
    • Price Impact and Slippage
    • How to Change Max Slippage
    • Margin Calculator
    • Self Trade Prevention
    • Receive Window
  • Instruments Guide
Join CommunityStart Trading
On this page
  • Attributes
  • Identifying as Retail via API

Trader Profiles

Users can choose between two trader profiles that best suits their strategy
Was this page helpful?
Edit this page
Previous

Retail Price Improvement

Better pricing for retail traders with selective order visibility
Next
Built with
Retail

UI traders enjoy lower fees
when trading

Pro

API traders have access to Pro rates

Attributes

RetailPro
Speed BumpOrder Submission: 300ms
Order Cancellation: 300ms		None
Rate Limit3 orders / sec
30 orders / min
300 orders / hr
1000 orders / 24 hrs		800 orders / sec
17,250 orders / min
Retail orders exceeding rate limits automatically switch to Pro trader profile and lose access to RPI liquidity.

For detailed fee information, see Trading Fees.

Identifying as Retail via API

By default, all orders submitted through the API are treated as Pro orders. To have your API orders treated as Retail orders, request a JWT token with the token_usage=interactive query parameter.

When using an interactive token:

  • The order is subject to Retail speed bumps and rate limits
  • The order qualifies for Retail trading fees based on Retail volume tiers
  • The order is eligible for Retail Price Improvement (RPI) liquidity
  • The order receives queue priority at each price level

Orders placed with an interactive token are subject to Retail rate limits. If rate limits are exceeded, the account automatically switches to the Pro trader profile and loses access to RPI liquidity.

1

Get an interactive JWT token

Add token_usage=interactive when requesting a JWT:

$POST /v1/auth?token_usage=interactive

See the Get JWT endpoint for details.

2

Authenticate requests with the token

Use the returned token for all authenticated requests. Orders placed with this token are treated as Retail.