Tetrac Documentation

TTC (Tetrac) builds trading tools based on a decade of trading experience. They keep execution, analysis and account management for many venues in one place, so you spend less time switching between exchanges.

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.

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 that require trade history reporting, account management, and execution algorithms.
• •Day traders looking for advanced execution, signals ranked by strength, self-custody on decentralized venues, and many venues in one terminal.
• •Investors who want to monitor multiple assets and accounts across venues.
• •Developers building trading applications and agents that want a plug and play environment for data and trading access.

Trading

Elite Tools

Automation & AI

Payments & Agent Rails

Security & Wallets

Platform

Tetrac as a Progressive Web App

Tetrac is a Progressive Web App (PWA) — you can install it on your phone, tablet, or computer straight from the browser. No App Store, no Play Store, no download links. Once installed, Tetrac launches in its own window like a native app, with its own icon on your home screen, dock, or taskbar.

Why Install the Tetrac App?

• •Native-app experience — full-screen standalone window with no browser tabs or address bar
• •One-tap access from your home screen, dock, or taskbar — your charts and positions are seconds away
• •Lightweight — installs in seconds with no app-store download or account required
• •Always up to date — new features ship instantly with the web app, no store updates to wait for
• •Same secure login, encrypted vault, and sessions as the browser — nothing to reconfigure

The TTC MCP server exposes Tetrac's exchange tools — tickers, best bid/ask, balances, positions, orders, leverage, deposit addresses and withdrawals — 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. It requires a signed-in session; x402 payments are not accepted here.

Endpoint: https://www.tetrac.xyz/api/v1/mcp

Step 1 — Copy your MCP headers

Log in and go to the trading dashboard. In the bottom-right corner of the Dashboard header card, click MCP Headers. It copies only your two session headers, as JSON:

{
  "ttc-auth-token": "<your session token>",
  "ttc-public-key": "<your public key>"
}

Heads up: the session token expires 24 hours after you sign in. When tool calls start failing with 401, sign in again, click MCP Headers again and replace both values.

Step 2 — Add the server entry to your MCP client config

Open your MCP host's config file and add the server entry below to its mcpServers object, with the two copied values under headers. Pasting the copied JSON straight into mcpServers makes an invalid config. 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://www.tetrac.xyz/api/v1/mcp",
      "headers": {
        "ttc-auth-token": "<your session token>",
        "ttc-public-key": "<your public key>"
      }
    }
  }
}

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

• 401 on connect or on every tool: the headers are missing, sit outside your server entry, or the 24-hour session expired. Sign in again, click MCP Headers, and replace both values inside the headers block of the TTC server entry.
• 429 Rate limit exceeded: the MCP server allows 20 requests per minute per account. Wait for the Retry-After seconds.
• Tool not showing up:your MCP client may have cached the old server. Fully restart it; don't just reload the window.

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 trading signals to your account on any supported exchange. The signal copier compares 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 API credentials for the exchange you copy to, configured via the desktop trading page.

Settings you must not change while a position is open

Three settings are construction inputs: changing any of them rebuilds the trading machine from scratch rather than adjusting it. The interface will let you edit them at any time — nothing stops you — so this is the one rule worth knowing before you trade.

• •Feed — the venue whose order book builds the bricks
• •Symbol — the market being traded
• •Brick % — the grid every price coordinate is measured against

Editing one of these while a position is open discards the running machine and starts a fresh one. Four things are lost, none of them visibly:

• •Auto trading switches itself off. The new machine starts disarmed, so nothing manages the position until you turn it back on.
• •The session PnL resets to zero. The daily loss limit is measured from it, so a limit that was nearly tripped starts counting again from nothing.
• •Resting orders are abandoned. Your entry and protective stop still exist at the exchange, but the new machine holds no reference to them — so Cancel orders can no longer reach them. They have to be cleared from the exchange itself.
• •The trail forgets its high-water mark. Trailing distance is measured from the best price seen since entry, and that history does not survive the rebuild.

Changing Brick % additionally re-scales the grid, so brick boundaries, pattern history and every stop level are recomputed against a different ruler.

Safe order of operations

• •Close the position first — Flatten, or let the trailing exit take it.
• •Confirm the top bar reads IDLE with no quantity.
• •Then change Feed, Symbol or Brick %, and switch auto trading back on.

Everything else — Size, Trail, Lock, Clearance, Loss limit, Max stale, patterns and the side toggles — is applied to the running machine in place and is safe to adjust with a position open.

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.

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

Analytics Features

Our Trading Analytics dashboard provides comprehensive tools to analyze your trading performance:

Best Practices

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 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 connects to these cryptocurrency exchanges (market-data coverage varies by endpoint):

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
• •Search functionality to quickly find specific assets
• •Real-time sorting by price, volume, or change percentage

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:

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

Drive the Chart from Telegram

Pair your own Telegram bot and control the app from any chat: switch the chart’s market with a message, check what’s currently loaded, and pull an on-demand Tetrac trade signal — entry, stop, targets and R:R — without leaving Telegram. It’s your bot and your chat: commands from any other chat are ignored.

A single polling loop runs app-wide (in the background, independent of which page you’re on), reads new messages every few seconds, and applies your commands to the shared chart symbol every open tab follows.

How It Works

Commands

Rate Limits

Because a bot can live in a public group, each command is throttled on a rolling 60-second window. Over the limit, the bot replies once with “Please slow down — wait Ns” and then stays quiet until the window clears (so a flood of commands can’t become a flood of replies).

Security & Privacy

• •Encrypted at rest, never on our servers — the bot token is saved in this browser only as ciphertext under your vault key. Once decrypted it stays in memory for the rest of your login session, so alerts keep running after the vault auto-locks, and it is dropped when you log out. Polling and replies go from your browser straight to Telegram.
• •Vault-gated— the first start in a login session decrypts the token through the vault. If the vault is locked, the control shows “Unlock Vault” first.
• •Chat allow-list— only messages from your configured Chat ID are acted on; anyone else in a shared group is silently ignored.
• •No backlog replay— messages sent before you press Start are skipped, so an old command can’t fire the moment you connect.
• •Read-only market data— commands change the chart and return analysis only. They never place orders or move funds.

Cross-Tab Symbol Sync

By default, the market you pick — from a chart dropdown or via a Telegram /chart command — is mirrored to every open tab through your browser’s local storage, so all your charts stay on the same symbol at once.

You can turn this off with the Cross-Tab Symbol Sync toggle in Settings Panel → Cross-Tab Symbol Sync. With it off, each tab keeps its own symbol independently and no longer follows the others. The preference is shared across your tabs and remembered between sessions.

PrivaC — Client-Side Encryption

Your wallets (Solana and EVM, including the Orderly signing wallet) are generated in your browser, and each private key is encrypted there before it is uploaded. Our servers store only that ciphertext with your account and never receive the key that decrypts it.

The key that decrypts them (your app key) is derived in your browser from how you sign in: a signature from your Web3 wallet, PBKDF2 over your passkey phrase salted with your email, or the WebAuthn PRF output of a device passkey. It is held in memory only — never sent to our servers and never saved in localStorage — and the vault locks 60 seconds after you unlock it (some signing steps restart that timer). Reloading the page also drops it.

How It Works

Security Guarantees

• •Unlock per account type— a device-passkey account unlocks with your biometric or PIN check; a wallet account by signing with the wallet; an email account with your passkey phrase, unless you turn on Biometric Unlock (below)
• •Zero plaintext on server— wallets are created client-side, encrypted, and stored on our servers only as ciphertext. The server never sees plaintext wallet keys
• •Memory-only app key— held in memory while the vault is unlocked, never written to browser storage, and gone when the vault locks or the page reloads
• •Exchange keys— API keys you save in the trading panel are encrypted under the same app key and kept in this browser. Once decrypted they stay in memory until you log out. Whether they are sent to Tetrac's server depends on the exchange's routing: see each exchange's section below

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 wallet signature prompts to sign in

Security Features

How an email account protects your keys and funds:

• •Self-custody on decentralized venues - On decentralized venues your funds stay in your own wallet. On centralized exchanges, the exchange holds your balance and Tetrac trades it with the API keys you provide.
• •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 verification code is required. There is no email recovery: Tetrac never sees your passkey phrase and cannot reset it, so back up the private keys of your Solana and EVM main wallets. Signing wallets can be regenerated at any time.

Overview

Tetrac supports the x402 payment protocol for pay-per-request access to its paid market-data and exchange endpoints (listed below). Without a session, each call is paid in USDC on Solana: $0.05 per call, or $0.50 for /api/v1/markets/ttc-scanner-cache. /api/v1/markets is a free index that lists every market endpoint with its price. Other /api/v1 routes are not for sale.

Paid Endpoints

These endpoints accept x402 payment. Parameters, responses and errors for each are in the API reference.

ttc-scanner-cache costs more because one call returns the whole multi-market Quadrant snapshot rather than one per-symbol result. Pass ?full=1 to receive the signals; without it the same price buys only the freshness timestamps.

How It Works

x402 uses HTTP status 402 (Payment Required) for machine-to-machine payment. When you call a paid endpoint without a session, the flow is:

Quick Example

Payment Header Format

Canonical x402 v2. PAYMENT-SIGNATURE carries standard base64 of this JSON, with no prefix. accepted is the accepts entry you paid against, echoed unchanged:

{
  "x402Version": 2,
  "accepted": {
    "scheme": "exact",
    "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
    "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
    "amount": "50000",
    "payTo": "<payTo from the 402>"
  },
  "payload": {
    "signature": "<solana-tx-signature>",
    "payer": "<your-wallet-address>"
  }
}

Instead of a landed signature, the payload may be { transaction: <base64 signed transaction> }. The server relays it but never pays its fee, so your wallet must sign as the fee payer.

v1 (still supported). x-x402-payment carries x402: followed by base64 of this JSON:

{
  "signature": "<solana-tx-signature>",
  "payer": "<your-wallet-address>",
  "amount": "50000"
}

Amounts are micro-USDC (50000 = $0.05, 500000 = $0.50). Take the amount and the payTo address from the 402 response rather than hardcoding them.

MPP (Machine Payments Protocol)

Agents that speak MPP pay through one gateway: POST /api/v1/mpp (GET also works) with { method, path, parameters } naming the endpoint. The gateway answers with its own 402 (terms in the WWW-Authenticate: Payment header), charges USDC on Solana, then forwards the call and returns the data with a payment receipt. It sells the same endpoints at the same prices, and checks the request before charging.

Full guide: MPP payments skill.

Security

• •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 Tetrac key involved: You sign the transfer and pay its fee; the server never holds a key for your payment
• •Time-limited: A transfer must be at most 5 minutes old when you present it

Session vs. X402 Payment

A signed-in session and an x402 payment unlock the same paid endpoints. Two things need a session: POST /api/v1/markets/ttc-scanner-cache (uploading the scanner snapshot) and the MCP server.

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.

Pricing

All prices are in USDC. Elite is priced at 2× Pro, and is sold on monthly and annual billing only — the daily plan is a Pro-only option. Annual billing is 12× the monthly rate less 10%.

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).

Exceeding a limit returns HTTP 429 with Retry-After, X-RateLimit-Tier, and X-RateLimit-Remaining headers.

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

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.

How It Works

Features

Access

Navigate to /crypto/solana-wallet-sweeper to use the wallet sweeper tool.

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.

Ledger Sweeper

Sweep SPL tokens and SOL from Ledger-derived addresses to a destination wallet. Optionally mark tokens for burning instead of transferring.

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.

Technical Details

Access

Navigate to /crypto/solana-ledger-sweeper to use the Ledger sweeper and token burner.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to ADEN, signing it where ADEN requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Aevo, signing it where Aevo requires a signature, and does not store them.

Leverage

Leverage is set per market (up to 20x on the majors); the shield icon in the trading panel reads each market's live cap from Aevo.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Leverage

Leverage is set per market and capped by that market's initial-margin fraction — 40x on BTC-USD (2.5%), 25x on ETH-USD, and lower on equities. The shield icon in the trading panel reads the live cap and the real maintenance-margin ratio straight from Arcus. Note that Arcus gates trading behind an address access whitelist: until your address is granted access, orders are rejected with 403 even with a valid key.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server. The trading panel opens on Lite; click the Lite badge in its header to switch.
• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to AsterDEX, signing it where AsterDEX requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Binance, signing it where Binance requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to BingX, signing it where BingX requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Bitfinex, signing it where Bitfinex requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Bitget, signing it where Bitget requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Bitrue, signing it where Bitrue requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Blofin, signing it where Blofin requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Bullish, signing it where Bullish requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Bybit, signing it where Bybit requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Coinbase, signing it where Coinbase requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Decibel, signing it where Decibel requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to DeepCoin, signing it where DeepCoin requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server. The trading panel opens on Lite; click the Lite badge in its header to switch.
• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to DojiFunded, signing it where DojiFunded requires a signature, and does not store them.
• •The Perp Aggregator's best bid/ask read for DojiFunded needs your keys, so when you use the aggregator they are sent to Tetrac's server for that read.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Evedex, signing it where Evedex requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request, so a private key or secret entered here is never sent to Tetrac's server. Hibachi rejects browser calls from our site, so these requests pass through Tetrac's relay, which forwards the API-key header and the signed request to Hibachi and does not log or store them. The trading panel opens on Lite; click the Lite badge in its header to switch.
• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Hibachi, signing it where Hibachi requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server. The trading panel opens on Lite; click the Lite badge in its header to switch.
• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Hyperliquid, signing it where Hyperliquid requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Kraken Futures, signing it where Kraken Futures requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to KuCoin, signing it where KuCoin requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to MEXC, signing it where MEXC requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to OKX, signing it where OKX requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Ondo Perps, signing it where Ondo Perps requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server. The trading panel opens on Lite; click the Lite badge in its header to switch.
• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Orderly Network, signing it where Orderly Network requires a signature, and does not store them.
• •The Perp Aggregator's best bid/ask read for Orderly Network needs your keys, so when you use the aggregator they are sent to Tetrac's server for that read.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server. The trading panel opens on Lite; click the Lite badge in its header to switch.
• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Pacifica, signing it where Pacifica requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Phemex, signing it where Phemex requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Propr, signing it where Propr requires a signature, and does not store them.

Leverage

Max leverage: 5x on BTC and ETH, 2x on all other crypto.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to Vanta Trading, signing it where Vanta Trading requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request itself. These credentials are not sent to Tetrac's server.

Trading Panel Credentials

Where These Credentials Go

• •Lite routing (browser): your browser signs each request, so a private key or secret entered here is never sent to Tetrac's server. Vest rejects browser calls from our site, so these requests pass through Tetrac's relay, which forwards the API-key header and the signed request to Vest and does not log or store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to WOO X, signing it where WOO X requires a signature, and does not store them.

Trading Panel Credentials

Where These Credentials Go

• •Pro routing (server): your browser sends these credentials to Tetrac's server over TLS with every request. The server uses them to authenticate that request to XBTFX, signing it where XBTFX requires a signature, and does not store them.
• •The Perp Aggregator's best bid/ask read for XBTFX needs your keys, so when you use the aggregator they are sent to Tetrac's server for that read.