Create a restricted key on your exchange
Create the key in your own exchange account. Permission names and key formats vary by exchange. Enable the read and Spot trading access needed for the supported connection.
Do not enable withdrawals. Keep transfer permissions disabled where offered, and do not grant unrelated access just to make validation pass.
The Exchanges page shows the fields required for the selected exchange, including a passphrase where needed.
Save, then review validation
Saving a key and validating a connection are different steps. Review the validation result and the reported permissions before using Real Spot.
An exchange may not report every permission through its API. If the interface says a permission is not reported, check the key on the exchange itself. Unknown does not mean disabled.
Use the connection's existing Check control and read its messages. Review the trading pair's rules when they are available.
Keep secrets out of messages and screenshots
Treat API secrets, private keys and passphrases as credentials. Enter them only into the relevant connection fields; do not include them in support messages or screenshots.
If a key has been exposed, revoke it on the exchange. Before replacing or removing a connection, follow the application's instructions about stopping its Real Spot bots.
AiNiBoTS displays a fingerprint for a saved key rather than showing the full secret again.