Exchange Keys

Application screenshotXTester 1.0.0-preview.1

Enlarge screenshot

1. Choose the exchange and environment.
2. Inspect the selected connection’s status.
3. The required fields depend on the selected exchange.

Open account-key settings, choose the exchange and Mainnet or Testnet environment, then supply the fields required by that connection. DEX connections may include wallet-address and wallet-key fields.

Saved secrets are not read back into Studio; they go to encrypted engine storage. Saving, verifying and deleting keys are separate actions. Saving is not proof that the exchange is reachable: run the connection check.

External AI clients use the separate External Connections view, rather than the exchange-key fields.

Select the correct exchange and environment. Mainnet and Testnet are separate connections; verifying one does not verify the other. Use the fields and options offered for that connection.

CEX commonly needs API key/secret and sometimes a passphrase; DEX fields can differ. Follow the actual field hints rather than an example for another exchange. An AI-provider key does not belong in exchange fields.

Use the key window and secure storage rather than strategy source. Inspect files before publishing source or distributing a robot: a hard-coded string is not automatically protected.

Save confirms storage; Verify is a separate operation for the selected exchange, environment and current fields. Verify again after replacing keys or changing environment.

Missing required fields are listed, and the window may explain that no network request was made. That is not an exchange rejection of a complete valid key.

Stored secrets are not read back. An empty field with the stored-value hint preserves it during editing. Enter a new value to replace it; use the separate confirmed deletion action to remove it.

Deletion removes saved fields for the selected exchange/environment. A strategy or robot needing them will require a suitable connection again; it cannot recover the old secret by revealing a password.

Check selected exchange/environment and required fields, then the exact result. Network failure, unavailable secure storage and exchange rejection are different causes.

Do not paste a secret into support chat. Build version, exchange, environment, check time and a redacted exact error usually provide the first diagnostic context. A compromised key is revoked at the exchange; clearing the visible field alone does not revoke it.