Trading verification · Bitget
Connect Bitget with a read-only API key and the trades DT Terminal reads from it carry the verified seal, so your record is something another person can check. Then the journal shows which pair, session and setup is paying for the rest.

How it works
In Bitget's API settings, create a key with read-only permission, so trading and withdrawal stay off, and choose a passphrase for it.
On Pro, pick Bitget and paste the API key, the secret and the passphrase. DT Terminal checks them with Bitget before saving, encrypted, and the first sync starts.
Fills pair into trades with the fee on each one and funding on the perpetuals, and every synced trade carries the seal.
Verified
A trade read from Bitget is marked Broker-Verified on your journal and your public page. A trade you typed stays self-reported, which is exactly why the seal means something.

Insights
Filter by pair, session, setup or tag and the win rate, expectancy and profit factor recompute, with fees and funding already inside the net figure.

Backtester
Replay a crypto chart bar by bar on real historical candles, trade it as if it were live, and read the session's numbers beside the Bitget record.

What is free
Bitget sync and the verified seal are Pro, $18 a month or $149 a year.
| Feature | Free | Pro |
|---|---|---|
| Broker auto-syncMT4, MT5, cTrader, TradeLocker and supported crypto exchanges | ||
| Read-only broker connections | ||
| Verified accountsSynced trades arrive with proof they were real | ||
| Linked broker accounts | Up to 3 | |
| Import per batch | 10 trades | Unlimited |
Full comparison on the pricing page.
Questions
Your fills on spot and on USDT-margined perpetuals, paired into trades, with the trading fee on each one and funding payments where Bitget reports them against a synced position. Coin-margined contracts are skipped with a note on the sync rather than given a P&L we cannot stand behind.
Bitget gives every API key a passphrase you choose when you create it, and its API will not answer without it. So DT Terminal asks for the API key, the secret and the passphrase together, and checks all three with Bitget before anything is saved.
Not with a read-only key, which is what the steps ask you to make. DT Terminal reads fills, fees, funding and balances, and never places, changes or closes an order. The key is stored encrypted.
DT Terminal values an exchange balance in cash and stablecoins only, and never guesses a coin price. While the account holds a coin such as BTC or ETH, the balance is left unsynced and the sync tells you why. Your trades keep arriving as normal.
No. Exchange sync is Pro, $18 a month or $149 a year, and it is what puts the verified seal on a trade. A free account can still journal Bitget trades by hand or by CSV, marked self-reported. Bitget is one of 10 exchanges that connect this way.
Soon. We are building an MCP connector that opens the whole of DT Terminal to Claude: every workspace and every piece of your data, to read and to act on, with your consent per scope. It works with any assistant that speaks MCP, and it is in development, not live yet.
Journaling by hand is free. Bitget sync and the seal are Pro.
Essential storage keeps DT Terminal working. Optional: product analytics and 60-day referral attribution. Change it any time in our Privacy Policy.