Review the exact setup before any order can be prepared.
TRADING SETUP / SECURITY GUIDES
Crypto exchange API
key setup guides.
Step-by-step instructions for creating trade-only exchange keys, selecting the minimum permissions and setting risk limits before connecting any trading tool.
START WITH THE EXCHANGE
Create the key correctly the first time.
Each exchange names permissions differently. The safe principle stays the same: use a dedicated key, allow only the access the product needs, restrict it by IP and never enable withdrawals.
AVAILABLE FOR CONNECTION TESTINGBinance
How to Create a Binance API Key Safely
Create a Binance API key for futures trading, choose the correct permissions, disable withdrawals and connect it safely to Crypto Pulse.
Read step-by-step guide ↗INTEGRATION PLANNEDBybit
How to Create a Bybit API Key Safely
Learn how to create a Bybit API key, select trade-only permissions, protect the secret and prepare it for a future Crypto Pulse connection.
Read step-by-step guide ↗INTEGRATION PLANNEDOKX
How to Create an OKX API Key Safely
Create an OKX API key with Read and Trade permissions, configure an IP allowlist and store the required API passphrase safely.
Read step-by-step guide ↗INTEGRATION PLANNEDBitget
How to Create a Bitget API Key Safely
Set up a Bitget API key for futures trading with read and trade permissions, an IP restriction and withdrawals disabled.
Read step-by-step guide ↗SAFE STARTER SETTINGS
Recommended limits for learning the workflow
These conservative product defaults are intended for testing the interface, not personal financial advice.
Calculated from available balance and stop distance.
A hard notional cap while testing the system.
Keep leverage low while learning execution behavior.
Avoid overlapping exposure during initial tests.
Pause new execution after the threshold is reached.
Reject a preview when the market moves too far.
Keep margin assigned to individual positions.
COMMON QUESTIONS
API access without custody
Can an API key withdraw my funds?
Only if withdrawal permission is enabled. Crypto Pulse does not need or request it. Keep Withdraw, Transfer and similar asset-movement permissions disabled.
Why use an IP allowlist?
An IP restriction limits where authenticated requests can originate. It materially reduces the usefulness of a stolen API credential.
Should I reuse an existing API key?
No. Create a dedicated key for each service so you can audit, restrict and revoke it independently.
Which exchange works with Crypto Pulse now?
Binance USDⓈ-M Futures connection testing is available to eligible portal accounts. Bybit, OKX and Bitget are planned. Live order submission remains disabled.
NEXT STEP
Understand the controls before connecting.
Read how Signals, Execute and Auto differ, then review the full trading-risk disclosure.