Meet TTC
TTC (Tetrac) builds trading tools based on a decade of trading experience. We're here to make innovative trading tools to increase your productivity and make you more money in your trading journey.
What is Tetrac
Tetrac is a comprehensive trading terminal designed for cryptocurrency traders. It provides real-time market data, advanced charting capabilities, and streamlined trading interfaces to help traders make informed decisions. Built with modern web technologies, Tetrac offers a responsive and feature-rich experience for both novice and professional traders. TTC.BOX is also the first to integrate a multi exchange Crypto Bridge to MetaTrader5 for charting, trading, and a unified robot framework.
Why We Built This
We built Tetrac to address the lack of intuitive, feature-rich trading platforms specifically designed for cryptocurrency markets. Traditional trading platforms often lack the specialized tools needed for crypto trading, while existing crypto platforms can be overwhelming or lack professional-grade features.
Tetrac bridges this gap by combining the best aspects of professional trading platforms with the accessibility and flexibility needed for cryptocurrency markets. We needed to take the headache out of trading across several exchanges. Therefore, we streamlined the process to manage accounts easily across the ever expanding crypto derivatives markets.
Who This Is For
- •Professional cryptocurrency traders
- •Day traders looking for real-time data visualization
- •Investors who want to monitor multiple assets
- •Developers building trading applications who need a reference implementation
Features
API Documentation
Tetrac provides a comprehensive API for accessing market data, executing trades, and managing user accounts.
For detailed API documentation, please refer to the API Documentation page.
MCP Integration
The TTC MCP server exposes every trading, market-data, and wallet tool in your MCP-capable host (Claude Desktop, Cursor, Windsurf, Claude Code, etc.). Once connected, you can ask your agent to place orders, fetch tickers, or read balances just by talking to it — no manual curl, no per-endpoint auth wiring.
Endpoint: https://ttc.box/api/v1/mcp
Step 1 — Copy your MCP config
Log in and go to the trading dashboard. Next to the Skills button at the top, click MCP Config. This copies a ready-to-paste JSON block containing your ttc-auth-token and ttc-public-key session headers.
Heads up: the session token expires every 24 hours. When tool calls start failing with 401, login again, re-copy and paste again.
Step 2 — Paste into your MCP client config
Open your MCP host's config file and paste the block into the mcpServers object. For Claude Code, the file is .mcp.json in the project root. For Claude Desktop, it's ~/Library/Application Support/Claude/claude_desktop_config.json.
{
"mcpServers": {
"ttc": {
"type": "http",
"url": "https://ttc.box/api/v1/mcp",
"headers": {
"ttc-auth-token": "<paste>",
"ttc-public-key": "<paste>"
}
}
}
}Step 3 — Restart your MCP client
MCP hosts read the config at startup, so quit and reopen the app (or run /mcp in Claude Code to reconnect). The TTC server should appear in your tools list with tickers, orders, positions, and wallet actions exposed.
Try asking: “show me Binance BTC ticker via TTC” — the agent will call get_tickers with your session headers and return live data, no x402 payment needed.
Troubleshooting
- Payment Required / 402 on every tool: your headers aren't being sent. Re-copy from the dashboard and confirm the
headersblock is inside your server entry (not at the root). - 401 Unauthorized after ~24h: session token expired. Re-copy from the dashboard and paste over the old headers.
- Tool not showing up:your MCP client may have cached the old server. Fully restart it; don't just reload the window.
MT5 Documentation
Tetrac provides enhanced MetaTrader 5 integration with additional features and capabilities.
For detailed MT5 documentation, please refer to the MT5 Documentation page.
Debug Tooling
For detailed error codes, please refer to the Debugging utility. page.
Trading Functionality
Advanced Order Management
Our trading panel provides comprehensive order management capabilities:
- •Multiple order types: Market, Limit, Stop, and Reduce orders
- •One-Click limit orders at best Bid | Ask
- •Toast notifications
- •Batch operations: Cancel all orders or close all positions
Position Management
Comprehensive position tracking and management tools:
- •Real-time position monitoring with PnL calculations
- •One-click position closing
- •Position scaling with breakeven and lock-in features
- •Margin mode selection (Isolated/Cross)
- •Hedge mode support for two-way positions
Risk Management Tools
Advanced risk management features to protect your capital:
- •Dynamic leverage adjustment (1.5x to 50x)
- •Stop-loss and take-profit order placement
- •Position liquidation price monitoring
- •Auto-detection of hedge/one-way mode based on existing positions
- •"Save Me" feature to place protective orders near liquidation price
Exchange Integration
Seamless integration with multiple cryptocurrency exchanges:
- •Secure API key management with encrypted storage
- •Supports most Perp CEX and DEX. See full list below.
- •Automatic market data fetching and symbol search
- •Real-time balance and position synchronization
Signal Copier
Automatically mirror DAO trading signals to your Orderly Network account. The signal copier compares DAO positions against your own portfolio and executes trades to stay in sync — with built-in risk controls and equity thresholds.
- •Automatic position synchronization with configurable polling intervals
- •Equity threshold protection — copier stops if account balance drops below configured limits
- •Symbol blacklist to exclude specific markets from being copied
- •Activity log with full history of executed signals and sync events
- •Responsive design with dedicated mobile bottom-sheet interface and desktop dashboard layout
- •Real-time account overview with balance, open positions, and pending orders
Access at /trading/copier. Requires Orderly Network credentials configured via the desktop trading page.
Trading Analytics
Overview
Tetrac provides comprehensive trading analytics tools to help you analyze your trading performance across multiple exchanges. Our analytics dashboard includes position history tracking, PnL analysis, win/loss statistics, and advanced charting capabilities.
Exporting Trade History
Export your complete position history to CSV or PDF format for offline analysis, backup, or sharing.
How to Export
- Navigate to the Trading Analytics page
- Select your exchange from the dropdown
- View your position history and analytics
- Click the CSV or PDF export buttons in the Position History section
- The file will download automatically
CSV Export Format
Filename: EXCH_WALL_YYYY-MM-DD.csv
Where:
EXCH- Exchange name (first 4 letters, uppercase)WALL- Wallet identifier (4 characters, uppercase)YYYY-MM-DD- Export date
CSV Columns:
Symbol,Side,Qty,Open Price,Close Price,Duration,Closed At,Realized PnLPDF Export Features
- Professional landscape layout
- Includes all position history data
- Color-coded PnL (green for profit, red for loss)
- Side badges (green for LONG, red for SHORT)
- Export summary with total positions and total PnL
Importing Trade History
Import previously exported CSV files to analyze your trading history without connecting to exchanges. Perfect for:
- • Historical analysis of trades from closed accounts
- • Combining data from multiple time periods and accounts
- • Offline analysis without API dependencies
How to Import
- Navigate to the Trading Analytics page
- Click the Import CSV button (green button with upload icon)
- Select your CSV file from the file picker
- The system validates the filename and imports the data
- Imported exchange appears in dropdown with 📊 (Imported) label
- All analytics charts update automatically
CSV File Requirements
- • Must follow filename format:
exchange_wallet_date.csv - • Must include all required columns (see CSV Export Format above)
- • Duration format supports:
2h,30m,1.5d,1w - • Exchange name must be at least 2 characters
- • Date must follow format:
YYYY-MM-DD
Merging Data
When you import a CSV for an exchange that already has imported data:
- • System automatically detects existing data
- • Merges new positions with existing data
- • Deduplicates by: symbol + close timestamp + side
- • Shows how many new positions were added
- • Example: "Merged 45 new positions with existing PHEM data. Total: 105"
Tip: You can import multiple CSV files for the same exchange to build a complete historical dataset over time.
Virtual Exchanges
Imported exchanges are "virtual" - they exist only for analytics:
- • No API keys required
- • Only analytics and visualization
- • Marked with 📊 (Imported) in dropdown
- • Data stored in memory (not persistent across page refresh)
Analytics Features
Our Trading Analytics dashboard provides comprehensive tools to analyze your trading performance:
Statistics Cards
- • Total PnL with color coding
- • Win rate percentage
- • Max drawdown calculation
- • Average position duration
- • Largest profit and loss
- • Win/loss streaks
Charts
- • Cumulative PnL line chart
- • Drawdown visualization
- • Win/loss streak chart
- • Position duration chart
- • Volume by symbol pie chart
- • Daily PnL calendar heatmap
Period Filtering
- • 30-day period slices
- • Navigate between periods
- • Each period has independent statistics
- • Period labels show date ranges
Position History Table
- • Pagination (30 positions per page)
- • Sortable by close timestamp
- • Color-coded PnL display
- • Side badges (LONG/SHORT)
- • Export buttons (CSV/PDF)
Best Practices
Regular Exports
Export your trade history regularly to maintain backups of your trading data, especially before making significant changes to your strategy or exchange accounts.
Consistent File Naming
Use consistent wallet identifiers in your filenames to easily organize and identify your exports (e.g., ABCD for main trading wallet).
Validate Imports
After importing, verify that the number of positions and statistics match your expectations. Check the charts and table for accuracy.
Period Review
Use the 30-day period filtering to analyze specific time ranges and identify patterns or trends in your trading performance.
Privacy Mode
Use the "Blur USD Values" toggle when sharing your screen or streaming to hide sensitive financial information while still showing relative performance.
Real-time Data
Comprehensive Market Data
Tetrac aggregates real-time market data from multiple leading cryptocurrency exchanges to provide you with the most accurate and up-to-date information:
- •Price updates for all supported cryptocurrencies across SPOT and FUTURES markets
- •Order book depth and real-time changes
- •Trade execution notifications and volume data
- •Open interest and funding rate information for futures markets
- •Market sentiment indicators and trending assets
Supported Exchanges
Our platform aggregates data from multiple leading cryptocurrency exchanges:
Data is refreshed every 60 seconds and cached for optimal performance while maintaining accuracy.
Advanced Data Filtering
Customize your market view with powerful filtering options:
- •Volume-based filtering to focus on high-liquidity markets
- •SPOT vs FUTURES market toggle
- •Search functionality to quickly find specific assets
- •Real-time sorting by price, volume, or change percentage
Customization
Multi-Device Support
Tetrac is designed to work seamlessly across all your devices:
- •Desktop: Full-featured trading terminal with advanced charting
- •Tablet: Optimized touch interface with essential trading tools
- •Mobile: Streamlined interface for on-the-go market monitoring
Advanced Charting & Data Views
- •Full screen tick charts for detailed price action analysis
- •Heat-map visualization for market overview and trending assets
- •Crypto screener with customizable filters and sorting options
Personalized Dashboard
Create your perfect trading environment with our customizable dashboard:
- •Favorite markets dashboard with integrated charts
- •Real-time tick-charts for quick price movements
- •Orderbook depth visualization for market insight
Dual Trading Interfaces
Choose the interface that matches your trading style:
Perp DEX Terminal
Simple UI designed for perpetual futures trading with essential tools
Multi-Terminal
Connect to multiple CEX | DEX to take control of several trading accounts. An advanced interface with comprehensive scanning tools for professional traders.
Visual Themes
Personalize your trading experience with our theme options:
- •Light Theme: Clean, bright interface for daytime trading
- •Dark Theme: Eye-friendly interface for extended trading sessions
Biometric Vault
PrivaC — Client-Side Encryption
All private keys (Solana, Orderly ed25519, EVM, EVM Signing) are AES-encrypted in your browser and never stored as plaintext. Decryption happens on-demand and is gated by WebAuthn passkeys — Touch ID or Face ID — so even XSS attacks cannot silently access your keys.
Your encryption key is derived deterministically from your credentials: a wallet signature for Web3 users, or a passkey for email users. It never touches our servers, never enters localStorage, and is cleared when you close the browser tab.
How It Works
Register & Derive Key
Sign up with email or connect a Web3 wallet. Your encryption key is derived via PBKDF2 — no passwords or KYC required.
Encrypt & Store
Wallets are generated automatically. Private keys are encrypted with AES-GCM (passkey) or AES-256 (string key) and stored in your browser.
Decrypt On-Demand
When a key is needed (signing an order, viewing credentials), it is decrypted in memory with biometric verification and discarded after use.
Security Guarantees
- •Biometric gating— Touch ID or Face ID required to decrypt any private key
- •Zero plaintext on server— wallets are created client-side, encrypted, and sent as encrypted blobs for backup. The server never sees plaintext keys
- •Memory-only encryption key— lives in memory only, backed by sessionStorage for page refreshes, cleared when you close the tab
- •Cross-platform— one set of encrypted credentials for Orderly Network, Vest Exchange, and all integrated platforms
Biometric protection is not enabled by default.
To activate it, open Settings Panel → Authentication → Biometric Protection and click “Enable Touch ID Protection”. After enabling, you can configure auto-lock duration, lock-on-tab-switch, and migrate existing exchange credentials to passkey protection.
Learn more about the PrivaC encryption system on the dedicated PrivaC page.
Email Signin
Web3 Wallet Alternative
Tetrac offers a seamless email signin option for users who prefer not to use a Web3 wallet. This feature provides a simplified onboarding process while maintaining security and control over your assets.
- •No gas fees required for signin
- •No need for wallet setup or seedphrase management
- •No bridging or Dapp connections needed
- •No signature signing required for basic access
Security Features
Our email signin system maintains the highest security standards:
- •100% Non-custodial - You retain full control of your assets
- •100% On-chain trading - All transactions are recorded transparently
- •Enhanced Private Key Security - Keys are never stored unencrypted
- •Main Wallet Control - Your main wallet controls all asset actions
Getting Started
Register with any email address, no verfication code required. No email recovery possible. backup your main wallet private for both SVM and EVM. Signing wallets can be regenerated at anytime.
X402 Payments
Overview
Tetrac supports the x402 payment protocol for pay-per-request API access. If you don't have an API key, you can access any /api/v1/* endpoint by paying $0.05 USDC per request on Solana.
Price per Request
$0.05 USDC
Blockchain
Solana
Token
USDC
How It Works
The x402 protocol uses HTTP status code 402 (Payment Required) to enable machine-to-machine payments. When you call an API endpoint without an API key, the flow is:
Request the Endpoint
Call any /api/v1/* endpoint. If you don't have an API key, the server responds with 402 Payment Required and includes payment details (amount, wallet address, token).
Pay with USDC on Solana
Send 0.05 USDC to the treasury wallet address provided in the 402 response. Use any Solana wallet (Phantom, Solflare, etc.) or SDK.
Replay with Payment Proof
After the transaction confirms, resend your API request with the x-x402-payment header containing the transaction signature.
Receive Data
The server verifies the payment on-chain and returns the API data. Each payment is single-use.
Quick Example
Step 1: Call an endpoint without credentials:
curl -s https://ttc.box/api/v1/markets/newsReturns 402 with payment details including the treasury wallet address and price.
Step 2: After paying, replay with the payment header:
curl -s https://ttc.box/api/v1/markets/news \
-H "x-x402-payment: x402:<base64-encoded-payment>"Payment Header Format
The x-x402-payment header contains x402: followed by a base64-encoded JSON object:
{
"signature": "<solana-tx-signature>",
"payer": "<your-wallet-address>",
"amount": "50000",
"timestamp": 1709827200000,
"payTo": "2v4XjdTjHK7qKEc8BkCeCWFrZmGSJv32ZGyv27zw3jc5"
}Amount is in microUSDC (50000 = $0.05). The payTo address is returned in the 402 response.
Available Endpoints
All /api/v1/* endpoints accept x402 payment. Key endpoints include:
/api/v1/markets/hybrid-tickers- Aggregated Tickers/api/v1/markets/funding-rates- Funding Rates/api/v1/markets/open-interest- Open Interest/api/v1/exchanges- Agent Trading/api/v1/markets/ttc-scanner- TTC ScannerSecurity
- •On-chain verification: Every payment is verified directly on the Solana blockchain
- •Replay protection: Each transaction can only be used once (24-hour cache)
- •No keys on server: The server never holds or manages your private keys
- •Time-limited: Payments expire after 5 minutes for safety
API Key vs. X402 Payment
Tetrac API endpoints support dual authentication. Either method grants full access to the same data:
API Key (Free Tier)
- • Register for free on Tetrac
- • Unlimited requests (rate limited)
- • Send
ttc-auth-tokenandttc-public-keyheaders
X402 Payment (Pay-per-Request)
- • No registration needed
- • $0.05 USDC per request on Solana
- • Send
x-x402-paymentheader
Subscription Tiers
Overview
Tetrac offers two paid tiers — Pro and Elite — purchased with Solana USDC via the x402 payment protocol. Subscriptions unlock higher API rate limits and premium product surfaces on top of the free tier.
Free
1×
baseline limits
Pro
3×
rate limit multiplier
Elite
10×
rate limit multiplier
Pricing
All prices are in USDC. Elite is priced at 2× Pro across every billing period.
| Billing | Pro | Elite |
|---|---|---|
| Daily | $3 | $6 |
| Monthly | $88 | $176 |
| Annual | $777 | $1,554 |
Rate Limits
Each tier multiplies the per-endpoint baseline. Limits are evaluated per window (60s) per caller identifier (publicKey for authenticated users, payer wallet for x402 requests, or client IP).
| Endpoint | Free | Pro | Elite |
|---|---|---|---|
/api/v1/markets/* | 30/min | 90/min | 300/min |
/api/v1/exchanges | 20/min | 60/min | 200/min |
Exceeding a limit returns HTTP 429 with Retry-After, X-RateLimit-Tier, and X-RateLimit-Remaining headers.
Pro
- • Full access to Pro Terminal
- • DAO participation & position sharing
- • MT5 Bridge
- • 3× API rate limits on gated routes
- • Priority x402 micropayment routing
Elite
- • Everything in Pro
- • 10× API rate limits on gated routes
- • Elevated burst capacity for bulk trading
- • Early access to experimental features
- • Priority support channel
Activation
Subscriptions are settled on Solana mainnet in USDC. Once payment is confirmed, the tier is attached to your account's public key and applied automatically on every gated request — no API key swap required.
- • Authenticated callers are keyed by their publicKey
- • x402 one-shot callers rate-limit at the free tier by payer wallet
- • Upgrading mid-window lifts the cap without resetting the counter
Solana Wallet Sweeper
Overview
The Solana Wallet Sweeper consolidates funds from multiple Solana wallets into a single destination address. It transfers all SPL tokens, closes empty token accounts to reclaim rent, and sends remaining SOL — all in one workflow.
Security: Private keys are never stored or transmitted — all signing happens locally in your browser.
How It Works
Set Destination
Enter the Solana wallet address where all funds will be consolidated.
Add Source Wallets
Add one or more wallets by entering both the public address and private key (base58). The tool validates that the key matches the address.
Fetch Balances
Click "Fetch" on each wallet to load SOL balance, SPL token balances, and detect empty token accounts with reclaimable rent.
Sweep
Sweep individual wallets or all at once. The tool closes empty accounts, transfers SPL tokens (creating destination ATAs as needed), and sends remaining SOL.
Features
Multi-Wallet Support
Add unlimited source wallets and sweep them all in one session.
SPL Token Transfer
Automatically detects and transfers all SPL tokens, creating ATAs on the destination if needed.
Rent Reclamation
Detects empty token accounts and closes them to reclaim ~0.00204 SOL per account.
Key Validation
Validates that each private key matches its public address before signing any transactions.
Access
Navigate to /crypto/solana-wallet-sweeper to use the wallet sweeper tool.
Solana Ledger Sweeper
Overview
The Solana Ledger Sweeper works with your Ledger hardware wallet to sweep funds and burn unwanted SPL tokens. All transactions are signed on the device — no private keys ever leave the hardware wallet.
Hardware Wallet Security: Every transaction must be confirmed on your Ledger device. Private keys never leave the hardware wallet.
Ledger Sweeper
Sweep SPL tokens and SOL from Ledger-derived addresses to a destination wallet. Optionally mark tokens for burning instead of transferring.
Connect Ledger
Connect your Ledger via USB, unlock with your PIN, and open the Solana app. Click "Connect Ledger" to establish the connection via WebUSB or WebHID.
Derive Addresses
Derive up to 20 addresses using the standard Solana BIP-44 derivation path m/44'/501'/x'/0'. Fetch balances to see SOL, SPL tokens, and empty accounts.
Set Destination & Sweep
Enter a destination address, then sweep individual wallets or all at once. Each transaction requires confirmation on your Ledger.
SPL Token Burner
Permanently destroy unwanted SPL tokens and reclaim the ~0.00204 SOL rent locked in each token account. This is a separate section from the sweeper — no destination wallet needed.
Irreversible: Burned tokens are permanently destroyed and cannot be recovered. Only burn tokens you are certain you no longer need.
Select Wallet
Choose a derived Ledger wallet from the dropdown.
Fetch & Select Tokens
Click "Fetch Tokens" to load all SPL tokens. Select individual tokens or use "Select All" to mark them for burning.
Burn & Reclaim
Click the burn button to execute. Each token is burned and its account closed in a single transaction, reclaiming rent SOL back to your wallet. Empty token accounts are also batch-closed.
Technical Details
Derivation Path
Uses standard BIP-44 m/44'/501'/x'/0' compatible with Ledger Live and Phantom.
Connection
Connects via WebUSB (primary) or WebHID (fallback). Requires Chrome or Edge browser.
Burn + Close
Each burn combines burnInstruction + closeAccountInstruction in one tx to destroy tokens and reclaim ~0.00204 SOL rent.
Batch Processing
Empty accounts are closed in batches of 10 per transaction to stay within Solana's transaction size limits.
Access
Navigate to /crypto/solana-ledger-sweeper to use the Ledger sweeper and token burner.
Adrena Integration
Trading Panel Credentials
API Key → TBD
Refer to the Adrena docs for the API Key field.
API Secret → TBD
Refer to the Adrena docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Adrena doesn't require one.
Aevo Integration
Trading Panel Credentials
API Key → TBD
Refer to the Aevo docs for the API Key field.
API Secret → TBD
Refer to the Aevo docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Aevo doesn't require one.
Apex Integration
Trading Panel Credentials
API Key → TBD
Refer to the Apex docs for the API Key field.
API Secret → TBD
Refer to the Apex docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Apex doesn't require one.
Ascendex Integration
Trading Panel Credentials
API Key → TBD
Refer to the Ascendex docs for the API Key field.
API Secret → TBD
Refer to the Ascendex docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Ascendex doesn't require one.
Asterdex Integration
Trading Panel Credentials
API Key → Signer address
The EVM address of the agent wallet created on AsterDEX (e.g. 0x21cF8Ae…). Sent as the signer param on every signed request.
API Secret → Agent private key
The private key of the agent wallet. Used locally to produce EIP-712 signatures — never transmitted to AsterDEX servers.
Passphrase → User — main wallet address
Your main EVM/Solana login wallet address. Sent as the user param on every signed request — this is your login wallet, not the signing agent wallet.
Binance Integration
Trading Panel Credentials
API Key → TBD
Refer to the Binance docs for the API Key field.
API Secret → TBD
Refer to the Binance docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Binance doesn't require one.
Bingx Integration
Trading Panel Credentials
API Key → TBD
Refer to the Bingx docs for the API Key field.
API Secret → TBD
Refer to the Bingx docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Bingx doesn't require one.
Bitget Integration
Trading Panel Credentials
API Key → TBD
Refer to the Bitget docs for the API Key field.
API Secret → TBD
Refer to the Bitget docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Bitget doesn't require one.
Bitmart Integration
Trading Panel Credentials
API Key → Access Key
The API Access Key generated by BitMart. Sent as the X-BM-KEY header on every request.
API Secret → Secret Key
The Secret Key used to compute HMAC-SHA256 signatures. Never transmitted — used locally to sign each request.
Passphrase → Memo (required)
The memo passphrase you set when creating the API key. BitMart includes it in every signing string (timestamp#memo#body) — must match exactly what you entered on BitMart.
Bitmex Integration
Trading Panel Credentials
API Key → TBD
Refer to the Bitmex docs for the API Key field.
API Secret → TBD
Refer to the Bitmex docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Bitmex doesn't require one.
Bitrue Integration
Trading Panel Credentials
API Key → API Key
The API Key issued by Bitrue. Sent as the X-CH-APIKEY header on every authenticated request.
API Secret → Secret Key
The Secret Key used to compute HMAC-SHA256 over timestamp + method + path + body. Never transmitted — used locally to sign each request.
Passphrase → Leave blank
Bitrue's auth scheme uses only the API Key and Secret — leave this field blank.
Blofin Integration
Trading Panel Credentials
API Key → TBD
Refer to the Blofin docs for the API Key field.
API Secret → TBD
Refer to the Blofin docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Blofin doesn't require one.
Bulktrade Integration
Trading Panel Credentials
API Key → Solana wallet public key
Your Solana wallet public key (base58).
API Secret → Solana keypair secret key
Your Solana keypair secret key (base58-encoded 64-byte array).
Passphrase → Leave blank
Not used by BulkTrade — leave this field blank.
Bullet Integration
Trading Panel Credentials
API Key → TBD
Refer to the Bullet docs for the API Key field.
API Secret → TBD
Refer to the Bullet docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Bullet doesn't require one.
Bybit Integration
Trading Panel Credentials
API Key → TBD
Refer to the Bybit docs for the API Key field.
API Secret → TBD
Refer to the Bybit docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Bybit doesn't require one.
Coinbase Integration
Trading Panel Credentials
API Key → TBD
Refer to the Coinbase docs for the API Key field.
API Secret → TBD
Refer to the Coinbase docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Coinbase doesn't require one.
Deepcoin Integration
Trading Panel Credentials
API Key → API Key
The API Key string DeepCoin issues when you create an API key under DeepCoin → API Management.
API Secret → Secret Key
The Secret Key shown once, alongside the API Key, at key-creation time.
Passphrase → Passphrase (required)
A password you choose yourself when creating the DeepCoin API key — DeepCoin does not issue it.
Dydx Integration
Trading Panel Credentials
API Key → Your dYdX address
Your main dYdX account address (dydx1…) where your funds are deposited. Used by the indexer API to read balance, positions, orders, and fill history.
API Secret → API wallet private key
The private key (0x…) of your API Trading Key wallet — it signs order and cancel transactions via dYdX's on-chain authenticator system and cannot withdraw funds. Generate one from dYdX → Settings → API Keys. Never leaves your browser.
Passphrase → Not used
Leave this field empty — it is not required for dYdX.
Extended Integration
Trading Panel Credentials
API Key → TBD
Refer to the Extended docs for the API Key field.
API Secret → TBD
Refer to the Extended docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Extended doesn't require one.
Flash Integration
Trading Panel Credentials
API Key → Solana wallet public key
Your Solana wallet public key (base58).
API Secret → Not used
Not used by Flash Trade — leave empty or enter any value.
Passphrase → Not used
Not used by Flash Trade — leave this field empty.
Gmtrade Integration
Trading Panel Credentials
API Key → TBD
Refer to the Gmtrade docs for the API Key field.
API Secret → TBD
Refer to the Gmtrade docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Gmtrade doesn't require one.
Grvt Integration
Trading Panel Credentials
API Key → API key string
The API key string from grvt.io → Account → API Keys.
API Secret → API secret
The API secret — used to mint the gravity session cookie on every login.
Passphrase → Sub-account ID
The sub-account ID (numeric string) the API key is scoped to.
Hyperliquid Integration
Trading Panel Credentials
API Key → Main wallet address
The EVM address (0x…) of the Hyperliquid account that holds your USDC, equity, and positions. Find it in the Hyperliquid app under your account profile (top-right → click address). TTC uses it to query balances, positions, and orders for that account.
API Secret → API (agent) wallet private key
The 64-char hex private key (0x… prefix optional) of an API wallet you generate on Hyperliquid → top-right profile → API → Generate API Wallet. The agent key signs each order/cancel action via EIP-712 on behalf of your main wallet. It cannot withdraw funds.
Passphrase → Not used
Hyperliquid has no passphrase concept — leave this field empty. (Only OKX-family venues use a passphrase.)
Kraken Integration
Trading Panel Credentials
API Key → API Key
The public API key from Kraken Futures → Settings → API Keys. Sent as the APIKey header on every authenticated request.
API Secret → API Secret (private key)
The base64 private key issued alongside the API key. Used locally to compute the Authent signature (SHA-256 + HMAC-SHA-512) — never transmitted to Kraken.
Passphrase → Leave blank
Kraken Futures authenticates with only the API Key and Secret — leave this field blank.
Kucoin Integration
Trading Panel Credentials
API Key → TBD
Refer to the Kucoin docs for the API Key field.
API Secret → TBD
Refer to the Kucoin docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Kucoin doesn't require one.
Lighter Integration
Trading Panel Credentials
API Key → TBD
Refer to the Lighter docs for the API Key field.
API Secret → TBD
Refer to the Lighter docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Lighter doesn't require one.
Mexc Integration
Trading Panel Credentials
API Key → TBD
Refer to the Mexc docs for the API Key field.
API Secret → TBD
Refer to the Mexc docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Mexc doesn't require one.
Okx Integration
Trading Panel Credentials
API Key → TBD
Refer to the Okx docs for the API Key field.
API Secret → TBD
Refer to the Okx docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Okx doesn't require one.
Orderly Integration
Trading Panel Credentials
API Key → Trading wallet public key
The ed25519 public key of your Orderly trading wallet — not your main Solana/EVM wallet address. The ed25519: prefix is added automatically, so enter the raw key.
API Secret → Trading wallet private key
The ed25519 private key (hex string) of your trading wallet. Signs every authenticated request and never leaves your browser.
Passphrase → Broker ID
The broker your Orderly account is registered under (e.g. ttc, woofi_pro). Leave empty to default to ttc — the wrong broker ID causes an account mismatch.
Ostium Integration
Trading Panel Credentials
API Key → Trader address
The 0x… Arbitrum EVM address that holds your USDC collateral and owns the open trades and limit orders.
API Secret → EVM private key
The EVM private key that signs trade transactions. Required for order placement, cancel, and close — balance and position reads work without it.
Passphrase → Not used
Not used by Ostium — leave this field blank.
Pacifica Integration
Trading Panel Credentials
API Key → Main account wallet address
Your main account wallet address (Solana pubkey) — the wallet that holds your funds on Pacifica. Used for all balance, position, and order queries.
API Secret → Agent wallet keypair
A base58-encoded 64-byte Solana keypair generated from app.pacifica.fi/apikey.
Passphrase → Not used
Not used by Pacifica — leave this field blank.
Papertrade Integration
Trading Panel Credentials
API Key → EVM main wallet address
Your EVM main wallet address (0x…) — the wallet that holds your Papertrade balance and signs the SessionKey registration intent.
API Secret → Session-key EVM private key
A session-key EVM private key (0x…, 32-byte hex) that signs openPositionBySig / closeBySig intents on your behalf. Never the main wallet's private key.
Passphrase → Not used
Not used today — reserved for an optional relayer endpoint URL once Papertrade ships gasless submission.
Paradex Integration
Trading Panel Credentials
API Key → TBD
Refer to the Paradex docs for the API Key field.
API Secret → TBD
Refer to the Paradex docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Paradex doesn't require one.
Phemex Integration
Trading Panel Credentials
API Key → TBD
Refer to the Phemex docs for the API Key field.
API Secret → TBD
Refer to the Phemex docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Phemex doesn't require one.
Phoenix Integration
Trading Panel Credentials
API Key → Solana main-wallet address
Your main wallet address (Solana pubkey) — the trader `authority` on Phoenix Eternal. Used for all balance, position, and order queries; these reads are public, so no login is required.
API Secret → Solana signing key
The Solana keypair that signs Phoenix transactions. Only the order write path uses it (a later release); the current read-only integration does not need it.
Passphrase → Not used
Not used by Phoenix — leave this field blank.
Propr Integration
Trading Panel Credentials
API Key → TBD
Refer to the Propr docs for the API Key field.
API Secret → TBD
Refer to the Propr docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Propr doesn't require one.
Reya Integration
Trading Panel Credentials
API Key → TBD
Refer to the Reya docs for the API Key field.
API Secret → TBD
Refer to the Reya docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Reya doesn't require one.
Standx Integration
Trading Panel Credentials
API Key → JWT access token
JWT access token returned by POST /v1/offchain/login (7-day expiry).
API Secret → Session private key
Hex ed25519 session private key used to sign request bodies.
Passphrase → x-session-id (optional)
Optional x-session-id — when set it must match your WebSocket session.
Variational Integration
Trading Panel Credentials
API Key → TBD
Refer to the Variational docs for the API Key field.
API Secret → TBD
Refer to the Variational docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Variational doesn't require one.
Vest Integration
Trading Panel Credentials
API Key → VEST API Key
Received after registration — a JWT token that authenticates your requests to the VEST API.
API Secret → Signing wallet private key
The private key of your signing wallet (not your main wallet). Used to sign every order and cancellation.
Passphrase → Account Group ID
Your VEST account group number — in most cases this is 0.
Woox Integration
Trading Panel Credentials
API Key → TBD
Refer to the Woox docs for the API Key field.
API Secret → TBD
Refer to the Woox docs for the API Secret field.
Passphrase → Optional
Optional — only required by exchanges that issue an extra passphrase alongside the key/secret (e.g. OKX). Leave blank if Woox doesn't require one.
Changelog
Track all updates, new features, and bug fixes across releases.
View full changelog