Connect a trading venue safely.
Live AI trading needs an authorized connection to the user's own venue account. QENOVRA keeps that authority narrow: trading only, bounded capital, bounded order size, hard loss limits and explicit user control.
Binance Spot — API key setup
Open API Management
Sign in to your own Binance account, open account/profile settings and enter API Management.
Create a dedicated key
Create one key only for QENOVRA AI Trading. Give it a recognizable label such as QENOVRA-AI.
Restrict permissions
Enable only the Spot trading permission needed for execution. Do not enable withdrawals. Do not enable futures, margin or unrelated transfer permissions.
Connect in Wallet
QENOVRA Wallet → AI Trading → Exchange connection → Binance → enter API Key + Secret → test connection → set capital and risk limits.
If Binance offers IP restrictions, use them only when QENOVRA Wallet displays the current production connector policy. Do not guess a server IP.
QENOVRA crypto pair checklist
For the current QENOVRA crypto universe, the quote asset is USDT. You do not manually “open” these pairs in Binance API Management. The Binance account must have Spot trading available; then the user selects which pairs QENOVRA is allowed to trade.
exchangeInfo: pair status, Spot eligibility, USDT quote, lot size and minimum notional. If the selected capital/order size is too small for the exchange minimum, the task/order is blocked instead of waiting forever.Tokenized stocks / bStocks are a separate Binance Stocks flow and may depend on region/account eligibility. QENOVRA should display only the symbols returned as tradable for that specific connected account; users should not copy a static stock list into Binance.
What QENOVRA may do
Read the permitted Spot account state, obtain market/rule data and submit Spot orders inside the task authorization. The current live engine is designed to reject withdrawals and transfers.
What QENOVRA must not do
No withdrawal permission, no arbitrary transfers, no leverage expansion, no futures/options and no trading outside the user's authorized asset/capital/risk scope.
Polymarket — different connection model
Polymarket is not the same as Binance API-key setup. Public market probabilities can be read without a private trading key. Real order execution requires an eligible Polymarket account/wallet and a signed wallet session / trading authorization. QENOVRA currently keeps live prediction execution gated until that wallet-session flow is complete and passes geoblock/eligibility checks.
| Capability | Status |
|---|---|
| Read public markets / probabilities | Available |
| Read portfolio by public wallet address | Available where provider data is reachable |
| PAPER prediction task | Available |
| Real Polymarket order execution | Wallet-session integration required / gated |
What a normal user should prepare
- Keep enough USDT in the Binance Spot wallet for the authorized capital plus fees.
- Choose only the pairs you want AI to be allowed to trade. Selecting 20 pairs is permission, not a command to buy all 20.
- Set capital, per-order amount/percentage, maximum loss and duration in QENOVRA Wallet.
- If QENOVRA says a pair/order is below Binance minimum notional, increase the per-order allowance or remove that pair; do not keep a task running that can never execute.
Before starting any live task
- Use a dedicated venue connection instead of your primary unrestricted key.
- Start with a small authorized capital amount.
- Set per-order %, maximum-loss %, duration and approved assets.
- Confirm withdrawals/transfers are disabled.
- Review fees, spread and estimated round-trip cost.
- Use Pause immediately if the live behavior differs from the stated strategy.