Run your bot on a venue that does not hold your money
Hummingbot, ccxt and Freqtrade connect natively, and anything that speaks REST and WebSocket works the same way. The key trades and cannot withdraw, and the collateral stays in a wallet you hold.
- 257 msmedian order round trip
- 71 marketsone margin balance
- 1.4 billiontraded on the venue
From key to first fill
- 1
Create a trading account
Non-custodial and no identity check. The collateral sits in a wallet whose key you hold, and TRUE cannot sign for it.
- 2
Create an API key
Choose whether it may trade perpetuals, spot or both, and copy it once. It has no withdrawal permission at all.
- 3
Point your bot at it
Select the venue in Hummingbot or Freqtrade, change an exchange id in ccxt, or send a signed request straight from a terminal.
- 4
Run small, then scale
Read the fills and the funding entries back through the API and confirm your accounting agrees with ours before you size up.
Built for unattended trading
Long running, thousands of orders, nobody watching. These are the parts that decide whether a strategy survives its first month.
A key that cannot withdraw
An API key is scoped to trading. It opens, closes and manages positions on the account that created it and nothing else, so a leaked key is a bad day rather than a lost balance. Pause or revoke it from the screen that created it: a paused key stops accepting orders at once while open positions stay exactly where they are.
Hummingbot, ccxt and Freqtrade, natively
The connectors are maintained on our side, so you configure a venue rather than writing or patching one. For most existing ccxt strategies that means changing an exchange id and supplying a TRUE key rather than rewriting the execution layer.
Three ways to authenticate
OAuth 2.1 with PKCE for a hosted product where each end user signs in to their own account, an MCP key for plugging an AI client into one account, and the Sequencer API with signed requests for unattended trading. Most bots use the third: a key, a millisecond timestamp and an HMAC-SHA256 signature over method, path and body.
Seventy one markets, one collateral pool
Crypto majors and alts, US equities including NVDA, TSLA, AAPL and MSTR, index products, gold, silver, oil and the major currency pairs, all as perpetuals on a single account with a single margin balance. One connector and one risk model across asset classes that would otherwise mean three brokers.
Leverage stated per market
100x on BTC, EUR, gold and silver. 75x on ETH and SOL. 30x on most other crypto, 25x on US equity perpetuals, and deliberately lower on newer listings while they build liquidity. The per market cap is in the API, so your bot should read it rather than assume a headline number.
Keys that report themselves
Each key shows its own call count, rate limit headroom and last used time, so you can see what a strategy is actually doing rather than inferring it from your own logs. One Hummingbot key on one account in this system has made 53,858 calls and placed 21,603 orders.
Most venues ask you to deposit first and trust them second. TRUE does not take custody: you create an API key on your own account, the collateral stays in a wallet you control, and the key can place orders but can never move funds out. This page gives you the numbers a systematic trader asks for before writing a line of code.
Latency, measured rather than claimed
Over the last thirty days TRUE accepted 84,203 live perpetual orders. Median total round trip, from our API receiving the request to the venue acknowledging the order, was 257 milliseconds. The 95th percentile was 806 milliseconds and the 99th was 2.3 seconds. The median time attributable to the venue itself was 256 milliseconds, which tells you most of the round trip is the exchange and very little of it is us. These are the real distributions from production telemetry, not a best case from an empty afternoon, and they are the numbers to design your timeouts and your retry logic against. A strategy that needs single digit milliseconds colocated next to a matching engine is not what this venue is for, and we would rather say that here than after you have built.
What non-custodial actually costs you
There is no deposit to be frozen and no withdrawal queue to be stuck in, and equally no support desk that can reverse a trade you asked for. That is the trade. Moving funds out requires a signature from the wallet you hold, which is why a leaked trading key cannot drain an account, and also why losing the wallet key is final in a way that a password is not. Several bots can share one account, with one caveat worth planning for: they share a margin balance, so two strategies that both size against free collateral can starve each other. Separate accounts give separate collateral pools and separate keys.
Frequently asked questions
Can an API key withdraw my funds?
No. Trading keys have no withdrawal permission. A key can open, modify and close positions on its own account and nothing else, and moving funds out requires a signature from the wallet you control.
Does ccxt work with TRUE?
Yes, natively. For most existing ccxt strategies that means changing an exchange id and supplying a TRUE key rather than rewriting the execution layer.
Is Hummingbot officially supported or is it a community connector?
It is integrated natively and maintained on our side, as is Freqtrade. You configure a venue rather than writing or patching a connector yourself.
What latency should I design for?
Median 257 milliseconds and 95th percentile 806 milliseconds for order round trip, measured over 84,203 live orders in the last thirty days. Set timeouts against the 95th percentile rather than the median, and expect the tail to be dominated by the venue rather than by our API.
Do I have to pass KYC before I can run a bot?
No. The account is non-custodial and trading does not require an identity check. You are responsible for whether trading perpetuals is permitted where you live.
Can I run several bots on one account?
Yes, with one caveat worth planning for: they share a margin balance, so two strategies that both size against free collateral can starve each other. Separate accounts give separate collateral pools and separate keys.
Where is the documentation?
The quick start and the full REST and WebSocket reference are at docs.truefinance.ai, including authentication, order types, funding, and the per market leverage and tick size definitions.
How much volume has the venue done?
Over 1.4 billion dollars cumulatively, counting all flow on the exchange including market making. Milestones are announced publicly as they are passed.
Related pages
Create a key and send one order
Non-custodial, no KYC, on iOS, Android and the web.