Supported exchanges, chains and wallets

Coverage

• Spot trades: supportedQueried per symbol from currently held assets - see the note on the connection.
• USD-M perpetual futures trades: supportedRequires futures read permission on the key.
• Funding payments: supported
• Realised P&L: supportedTaken from the values Binance reports for futures fills.
• Open futures positions: supported
• Leverage: supportedRead from open position data.
• Options: not supportedNot implemented yet.
• COIN-M futures: not supportedNot implemented yet.

Connecting

1. Open API Management in your Binance account settings and create a new API key.
2. Leave every trading permission OFF. Only "Enable Reading" is needed.
3. Do not enable withdrawals, universal transfer, or futures trading.
4. If your account supports it, restrict the key to trusted IPs.
5. Paste the key and secret here. The secret is encrypted before it is stored and is never shown again.

Never enable: Enable Spot & Margin Trading, Enable Futures, Enable Withdrawals, Permit Universal Transfer. Credentials are encrypted before storage.

Coverage

• Spot trades: supported
• Perpetual / linear futures trades: supported
• Options trades: supportedImported when the account has options activity.
• Trading fees: supported
• Funding payments: supported
• Open positions: supported
• Leverage: supportedRead from open position data.
• Inverse contracts: not supportedNot implemented yet.

Connecting

1. Open API Management in your Bybit account and create a new System-generated API key.
2. Choose "Read-Only" for the API key permission type.
3. Enable only the read scopes you need: Positions, Orders, Trade History and Wallet.
4. Do not enable Trade, Transfer, Withdraw, or Sub-account transfer.
5. Paste the key and secret here. The secret is encrypted before it is stored and is never shown again.

Never enable: Unified Trading - Trade, Wallet - Withdraw, Wallet - Account Transfer, Exchange - Convert. Credentials are encrypted before storage.

Coverage

• Spot trades: supportedFrom the fills history endpoint - the last 3 months on first import.
• Perpetual swap trades: supportedContract sizes are converted to base-currency quantities.
• Funding payments: supported
• Realised P&L: supportedTaken from the values OKX reports on closing fills.
• Open swap positions: supported
• Leverage: supportedRead from open position data.
• Options: not supportedNot implemented yet.
• Dated futures: not supportedNot implemented yet.

Connecting

1. Open API keys in your OKX account settings and create a new API key.
2. Set the permission to "Read" only. Do not grant Trade or Withdraw.
3. Choose a passphrase - OKX requires it for every request, so you will enter it here too.
4. If your account supports it, bind the key to trusted IPs.
5. Paste the key, secret and passphrase here. All three are encrypted before storage and never shown again.

Never enable: Trade, Withdraw. Credentials are encrypted before storage.

Coverage

• Spot trades: supportedComplete history from the TradesHistory endpoint - no per-symbol limitation.
• Margin spot trades: supportedImported as spot fills; Kraken does not report the leverage used.
• Futures: not supportedKraken Futures uses a separate API and keys - not implemented yet.
• Funding payments: not supportedOnly applies to futures, which are not imported.
• Open positions: not supportedSpot has none; margin position tracking is not implemented.
• Realised P&L: not supportedComputed by this platform from fills, not reported by Kraken.

Connecting

1. Open API settings in your Kraken account and create a new key.
2. Grant only "Query Funds" and "Query Closed Orders & Trades". Nothing else is needed.
3. Do not grant "Create & Modify Orders", "Withdraw Funds", or any export permission.
4. Paste the API key and private key here. The private key is encrypted before storage and never shown again.

Never enable: Create & Modify Orders, Cancel/Close Orders, Withdraw Funds, Deposit Funds. Credentials are encrypted before storage.

Coverage

• Perpetual trades: supportedComplete fill history with reported closed P&L.
• Named spot pairs: supportedPairs like PURR/USDC. Index-coded pairs are skipped with a note.
• Funding payments: supported
• Realised P&L: supportedTaken from the values Hyperliquid reports on closing fills.
• Open perp positions: supported
• Leverage: supportedRead from open position data.
• Vaults / sub-accounts: not supportedConnect each address separately.

Connecting

1. Paste the wallet address you trade with on Hyperliquid.
2. No API key or secret exists for this connection: fills, positions and funding are public per-address data on Hyperliquid, the same data anyone can see on-chain.
3. Because there is no key, this connection cannot place orders or move funds under any circumstances.

Coverage

• Futures fills: supportedCME group micro and standard contracts, complete fill history.
• Fees: supportedCommission, clearing, exchange and NFA fees per fill.
• Open positions: supported
• P&L: supportedComputed from fills at USD contract value (points x point value) - exact, never estimated.
• Read-only credential: not supportedTradovate has no read-only scope; the elevated-access warning always shows.
• Funding: not supportedFutures have no funding payments.

Connecting

1. Tradovate API access requires the API Access add-on on your Tradovate account.
2. In Tradovate settings, create a DEDICATED password for API use - never your main password.
3. Enter your Tradovate username and that dedicated password here. Both are encrypted before storage and never shown again.
4. Plain honesty: Tradovate has no read-only credential - this login could trade. This platform contains no code path that places an order, but treat the password accordingly and revoke it in Tradovate settings any time.

Coverage

• Spot trades: supported
• US futures (CFTC-regulated): supportedClassified by product code; contract-specific details beyond price/size are not parsed.
• International perpetuals (INTX): not supportedCoinbase is retiring this product line in September 2026 in favour of a different API; not implemented.
• Options: not supportedNot implemented yet.
• Funding payments: not supportedNot implemented yet.
• Realised P&L: not supportedComputed by this platform from fills, not reported by Coinbase.
• Open positions: not supportedThis adapter reads fills only; not implemented yet.
• Leverage: not supportedNot reported on fills.

Connecting

1. Open the Coinbase Developer Platform API key manager and create a new "Secret API Key".
2. Choose the ECDSA key type. Ed25519 keys are not supported here - this adapter signs with ES256 only.
3. Under permissions, grant "View" only. Leave "Trade" and "Transfer" disabled.
4. Download the key. Coinbase gives you both a key name and a PEM private key.
5. Paste the key name into the first field and the full PEM block - including the BEGIN and END lines - into the secret field. It is encrypted before storage and never shown again.

Never enable: Trade, Transfer. Credentials are encrypted before storage.

Coverage

• Spot trades: supportedUp to 30 days per request; older history is paged in 30-day windows.
• USDT-margined perpetual futures: supported
• BTC-margined perpetual futures: supported
• USD1-margined and delivery futures: not supportedNot implemented yet.
• Funding payments: not supportedNot implemented yet - Gate.io reports these on a separate account-book endpoint.
• Realised P&L: not supportedNot reported per-fill by the Gate.io trade-history endpoint.
• Open futures positions: supported
• Leverage: supportedRead from open position data.
• Options: not supportedNot implemented yet.

Connecting

1. Open API Key Management in your Gate.io account settings and create a new key.
2. Grant read-only access to Spot Trading and Futures. Do not enable Withdrawal or Transfer.
3. If your account supports it, bind the key to trusted IPs.
4. Paste the key and secret here. Both are encrypted before storage and never shown again.

Never enable: Withdrawal, Transfer, Trading. Credentials are encrypted before storage.

Coverage

• Spot trades: supported
• Margin trades: supportedImported as spot fills; margin-specific details like used leverage are not reported by this endpoint.
• Perpetual futures: supportedSymbols like BTCF0:USTF0 are recognised and imported as perp fills.
• Funding payments: not supportedBitfinex funding/lending is a distinct product from perp funding fees; not implemented.
• Realised P&L: not supportedNot reported per-fill by Bitfinex; computed by this platform from fills.
• Open positions: supported
• Leverage: supportedRead from open position data when a position is active.
• Options: not supportedBitfinex has no options product.

Connecting

1. Create a new API key in Bitfinex account settings.
2. Bitfinex requires choosing scopes explicitly per category: enable read-only access for "Account History", "Orders" and "Wallets".
3. Leave every "Write"/create-order/withdraw toggle disabled.
4. Paste the key and secret here. Both are encrypted before storage and never shown again.

Never enable: Orders (write), Withdrawals, Account (write). Credentials are encrypted before storage.

Coverage

• Spot trades: supportedComplete history via user_transactions - no per-symbol limitation.
• Perpetual futures: not supportedBitstamp added perpetual futures in 2025; not implemented yet.
• Funding payments: not supportedOnly applies to futures, which are not imported.
• Realised P&L: not supportedComputed by this platform from fills, not reported by Bitstamp.
• Open positions: not supportedSpot has none; futures are not implemented.
• Leverage: not supportedNot applicable to spot; futures are not implemented.

Connecting

1. Open API Access in your Bitstamp account security settings and create a new key.
2. Under Permissions, enable only "Account balance" and "User transactions". Nothing else is needed.
3. Optionally restrict the key to trusted IP addresses.
4. Paste the API key and secret here. The secret is encrypted before storage and never shown again.

Never enable: Open orders, Order placement/cancellation, Withdrawals, Transfers. Credentials are encrypted before storage.

Coverage

• Spot trades: supportedLast 7 days only - matches this platform's own sync window in practice.
• Margin trades: not supportedNot implemented; margin fills are a separate endpoint family.
• Futures: not supportedKuCoin's futures fill-history endpoint only covers the last 24 hours and 1000 records, too limited to import reliably - not implemented.
• Funding payments: not supportedOnly applies to futures, which are not imported.
• Realised P&L: not supportedComputed by this platform from fills, not reported by KuCoin.
• Open positions: not supportedSpot has none.
• Leverage: not supported

Connecting

1. Open API Management in your KuCoin account and create a new key.
2. Choose a passphrase - KuCoin requires it for every request, so you will enter it here too.
3. Under Permissions, enable only "General" (read access) and leave "Spot Trading", "Margin Trading", "Futures Trading", and "Transfer" all disabled.
4. Optionally restrict the key to trusted IPs.
5. Paste the key, secret and passphrase here. All three are encrypted before storage and never shown again.

Never enable: Spot Trading, Margin Trading, Futures Trading, Transfer. Credentials are encrypted before storage.

Coverage

• Perpetual trades: supportedComplete fill history for subaccount 0.
• Spot trades: not supporteddYdX v4 is perpetuals-only; there is no spot product.
• Funding payments: not supportedNot supported, not implemented - dYdX does not expose an itemized funding feed via this adapter; net funding is visible on open positions only.
• Realised P&L: not supportedComputed by this platform from fills, not reported per-fill by dYdX.
• Open positions: supported
• Leverage: not supportedNot reported by the positions endpoint used here.
• Multiple subaccounts: not supportedOnly subaccount 0 is read; connect a different address for other subaccounts.

Connecting

1. Paste the wallet address you trade with on dYdX.
2. No API key or secret exists for this connection: fills, positions and funding are public per-address data on dYdX's Indexer, the same data anyone can query.
3. Because there is no key, this connection cannot place orders or move funds under any circumstances.
4. Only the address's default subaccount (0) is read.