Crux™ Help

Connect Binance.US

By , founder of Crux · Updated · Written with AI assistance and published by Mason Shoemate (how this page is written)

Binance.US is a US cryptocurrency exchange. Crux reads your Binance.US trades with a read-only API key.

Create a read-only API key in Binance.US.

Crux only reads. It has no order-entry code and cannot place, change or cancel a trade, or move money. Everything below asks for read-only access, and you can revoke it from your broker at any time.
How fills become trades: two buys and one sale of 0.12 BTC pair first in, first out into two trades, 0.10 BTC for +$400 and 0.02 BTC for +$40, with 0.03 BTC left open.
How Crux pairs an exchange's fills into trades, first in, first out.

In Binance.US, once

  1. Go to Profile → API Management → Create API.
  2. Leave Enable Reading on and every trading and withdrawal permission off.
  3. Copy the API key and Secret key.

In Crux

  1. Choose Add broker or prop firm → Connect Binance.US.
  2. Paste the API key and Secret key.
  3. Choose Connect and import. Crux checks the key with Binance.US first, then imports your fills and pairs your buys and sells into trades.
Crux refuses a key that can trade or withdraw and doesn’t save it.

Why are some older Binance.US trades missing?

Binance.US only reports trades one coin at a time. Crux reads every coin you hold now, plus any coin it has seen before. A coin you sold completely before connecting won’t be found — export those trades from Binance.US and import the file.

How does Crux turn Binance.US fills into trades?

It pairs your buys and sells first in, first out, into trades with an entry, an exit, fees and P&L. Binance.US reports fills (each buy and sell), not whole trades. A sell with no earlier buy stored — say, coins you bought before the history Crux can see — isn’t counted as a short. It’s left out rather than guessed.

Trades from Kraken, Coinbase, OKX, Crypto.com and Robinhood are paired the same way.

Which pairs does Crux ask about?

Binance.US has no way to list every pair an account has traded; it answers one pair at a time. So Crux asks for the pairs that can matter: each coin you hold now, against USD, USDT, USDC, BTC, ETH and BUSD, plus every pair it has already stored fills for. Once a pair is in your journal it is checked on every sync, even after you have sold out of it.

The one case this misses is a coin you sold completely before you connected, because there is nothing left in the account to say you ever held it. Export those trades from Binance.US and import the file; after that, Crux knows the pair and keeps it up to date.

Is the key checked?

Where Binance.US reports a key’s restrictions, Crux refuses one that can trade or withdraw. Create the key with reading enabled only.

An example

You buy 0.5 SOL against USDT at 150, then sell it against USDT at 162. That is one SOLUSDT trade with $6 of profit before fees. A sale of the same SOL against USD would be a different pair, and Crux pairs it within that pair.

Figures in the example are illustrative, to show the arithmetic. Your own come from your account.

Deposits and transfers

Only trades come in. Deposits, withdrawals and transfers aren’t trades, so they stay out of your P&L, and a sale of coins you deposited rather than bought here has no buy to pair with, so it is left out rather than counted as a short.

Keep reading