01 · START
Quick start
Velora Nexus supports financial research and assisted trading. Ask market questions directly in conversation. Sign in when you need persistent personal data, paper trading, or an exchange connection.
Create an account
Register or sign in from the home page. Velora Chat, the account center, and the trading console share the same account session.
Open Velora Chat
Describe the asset, timeframe, objective, and constraints in natural language. Fixed commands are not required.
Research before acting
Check timestamps, evidence, risks, and invalidation conditions. Trading assistance is not a return guarantee and does not transfer responsibility for your decision.
02 · RESEARCH
How to request market analysis
A useful request usually includes four elements: asset, timeframe, objective, and constraints. Velora may ask for missing details. For position reviews, include direction, entry price, size, and risk tolerance.
Market direction
"Analyze BTC on the 4-hour timeframe using volume, OI, and funding. Conclude bullish, bearish, or neutral."
Position review
"I hold a long SNDK position from 1770. Can I keep it? Show support, stop references, and invalidation."
Event impact
"Analyze how this news may affect TSM. Separate observed price reaction from possible future paths."
On-chain research
"Check large ETH transfers over 24 hours, exclude news, and combine them with 1-hour indicators to assess entry conditions."
Trading plan
"Build a 4-hour BTCUSDT plan with an entry zone, stop, TP1, reward-to-risk, and no-trade conditions."
Relative strength
"Compare BTC and ETH using trend, volatility, OI, funding, and structure levels."
Specify the timeframe and purpose. A short-term entry, swing position, and event study require different evidence.
03 · RESULTS
How to read the analysis
Conclusion
Bullish, bearish, or neutral describes the current evidence. It is not a certain forecast. Neutral is a valid result when evidence is weak or conflicting.
Evidence
Check data time, primary timeframe, price structure, volume, trend strength, and the source of news or on-chain evidence.
Entry and structure levels
Support and resistance combine swing pivots, ATR-width clustering, volume concentration, and repeated recent touches rather than simple highs and lows.
Expected R and TP1 RR
Expected R combines directional probability with payoff structure. TP1 RR uses the actual first target and stop distance. Neither replaces position sizing or a stop.
Model factors
Kalman, Hurst, ADX, and realized volatility help evaluate local trend, regime, directional strength, and chasing risk. The summary explains only the main factors on the primary timeframe.
Invalidation
Re-run the analysis when price, time, or an event crosses the stated invalidation boundary.
04 · CONTINUITY
Charts, alerts, and memory
Continue editing a chart
After generating a chart, ask to add EMA200, Bollinger Bands, a trend channel, or a different timeframe. Velora continues the current chart task.
Watchlists and alerts
Use natural language to manage watchlists and create price, funding, OI, whale-activity, or market-session alerts. Monitoring runs only after you explicitly create and enable it.
Personal memory
Authorized watchlists, alerts, positions, and trade records can support follow-up questions. Before an important trade, restate current direction, cost, and size instead of relying only on memory.
05 · TRADING
Trading modes and current limits
Read these limits first
- Create and confirm trades in natural language through Velora Chat, or use deterministic forms and buttons in the trading console.
- Exchange connections, risk settings, order state, and journals are managed in the Web account center.
- Submit API Key, Secret, and Passphrase only in the account center, never through Telegram, Discord, or a chat message.
- The live executor currently submits entry orders only.
- Stop-loss and take-profit values are recorded in the plan and audit trail but are not automatically placed as exchange conditional orders.
- After a live entry, immediately verify the exchange order and place or verify protective orders yourself.
- Velora rejects API keys with withdrawal or transfer permissions.
06 · EXCHANGE API
How to create an exchange API key
Start with a read-only key or a test environment. Create a separate live trading key only after account and environment verification. Do not reuse an old high-privilege key.
47.245.162.22Allow this public IP for live keys. If the console later shows a different value, use the latest value shown there.
Binance
- Open API Management. Sign in to Binance and create a new API key.
- Use minimum permissions. Enable reading first; add the required trading permission only for execution.
- Disable withdrawals. Do not grant withdrawal, transfer, or fund-movement permissions.
- Restrict the IP. Allow only
47.245.162.22for a live key. - Store the one-time Secret. Delete and recreate the key if it is lost or exposed.
- Match environments. Use Testnet credentials for a Binance Testnet connection and live credentials for Live.
Binance API key guide ↗Binance developer documentation ↗
OKX
- Open API. Sign in to OKX, open API settings, and create a key.
- Select the environment. Create Demo credentials in Demo Trading and live credentials in the live account.
- Select permissions. Use Read for read-only access or Read + Trade for execution. Never enable Withdraw.
- Add the IP allowlist. Use
47.245.162.22for a live key. - Save the Passphrase. This is the password chosen when creating the key, not your account password. It cannot be recovered.
- Keep all three values. Save API Key, Secret Key, and Passphrase and do not mix Demo and Live credentials.
07 · CONNECT
Connect an exchange to Velora
- Sign in and open the Trading Console, then open Exchange Connections.
- Select Binance or OKX and choose Testnet, Demo, or Live.
- Select Read-only or Trade. This must match the permissions granted by the exchange.
- Enter a connection name, API Key, and API Secret. OKX also requires the Passphrase.
- For Live, confirm that the server IP allowlist is configured, then save the encrypted credentials.
- Run online verification. After status becomes
verified, read account, position, and open-order data.
The backend encrypts them immediately and stores ciphertext. The page displays only a key fingerprint. Never send a full Secret in a screenshot, chat, or support message.
08 · PAPER
How to use Paper Trading
Create through conversation
A paper draft needs an asset, side, entry, stop, target, Expected R, and either quantity or notional amount. Values must come from you or the current strategy. Velora asks for missing inputs rather than guessing.
You: Open a paper BTC long from the last plan: 0.01 BTC, entry 62000, stop 60800, target 64500, Expected R 0.32.
Velora: Creates a paper order draft showing the connection, risk, TP1 RR, hard-risk result, and expiry.
You: Confirm this paper order.
Result: Creates an Order Intent and Paper Trade without sending anything to the exchange.
Say "cancel this paper order" to cancel. You can view, mark prices, or close positions in natural language or through Paper Positions in the console.
Create through the console
Open Order Intents and enter connection, asset, side, order type, quantity, entry, stop, target, leverage, risk percentage, Expected R, and TP1 RR. The page calculates price risk before hard-risk validation.
09 · TEST
Testnet / Demo Trading
- Create a Binance Testnet or OKX Demo API key.
- Connect the matching environment with Trade scope and complete online verification.
- Create an Order Intent that passes hard-risk checks.
- Select Test Order, review the summary, and explicitly confirm the test submission.
- Use Orders and Activity to inspect submission, fills, cancellation, errors, alerts, and journal events.
Test and live environments are isolated. An environment mismatch usually means Demo/Testnet credentials were connected as Live, or live credentials were used for a test connection.
10 · LIVE
How live confirmation works
Live trading uses real funds
Confirm that the connection is Live, scope is Trade, status is verified, and the IP allowlist is active. Complete Paper and Testnet/Demo first.
Confirm in the console
- Open an Order Intent that passed hard-risk checks and select Live Confirmation.
- Review asset, side, quantity, type, entry, stop, target, risk, and connection.
- Enter the exact confirmation phrase requested by the dialog.
- After submission, immediately verify status in both the console and the exchange.
Confirm in natural language
- In Velora Chat, ask for a live confirmation ticket for the Order Intent. Creating the ticket does not place an order.
- The ticket includes a Confirmation ID, random challenge code, exact phrase, and expiry.
- Reply with the complete phrase within five minutes, for example
CONFIRM LIVE BTCUSDT 0.01 A1B2C3. - Generic replies such as "confirm" or "place it," a missing code, a typo, or an expired phrase will not execute.
- The phrase is single-use. If submission fails, inspect order and alert state before doing anything else.
11 · RISK
Risk settings and Kill Switch
Each exchange connection has an independent risk profile. Review the defaults against your account size and strategy before saving.
Stops, targets, and per-order confirmation are enabled by default. Orders are also rejected for disallowed assets, non-positive Expected R, invalid stop/target direction, excessive risk, or excessive leverage.
Immediate breaker
Select a connection and activate the Kill Switch to block new exchange orders. It does not cancel existing exchange orders or close positions. Inspect and manage those directly at the exchange.
12 · SECURITY
API and account security
- Create a dedicated API key for Velora.
- Prefer a sub-account or limited account balance to reduce exposure.
- Use minimum permissions and never enable withdrawals or transfers.
- Apply the server IP allowlist to every live key and review it periodically.
- Enable exchange account 2FA and monitor key, permission, and login notifications.
- If a Secret appears in chat, a screenshot, a log, or an unknown device, delete the key at the exchange immediately.
- After disabling a Velora connection, also delete any key that is no longer needed at the exchange.
13 · FAQ
Common questions
Account and use
Can I use Velora without signing in?
You can browse the public site and public entry points. Persistent memory, exchange connections, paper trading, and the trading console require an account.
Why did a follow-up not continue the prior task?
State the asset and timeframe again, and update any changed position or price information. A different asset, timeframe, or objective may begin a new task.
Is the analysis investment advice?
No. Velora provides information aggregation, research, and trading assistance. It does not guarantee forecast accuracy or returns.
Exchange connections
Why did verification fail?
Check the exchange and environment, read permission, complete Secret/Passphrase, server time, IP allowlist, and whether the key is active.
Why does OKX reject the Passphrase?
The Passphrase is chosen when the OKX API key is created and is not the login password. Delete and recreate the key if it is lost.
Can I connect a key with withdrawal permission?
No. Velora rejects keys that declare withdrawal, transfer, internal-transfer, or fund-movement permissions.
Will the API Secret be displayed again?
No. Velora displays only the key fingerprint. Exchanges generally show the Secret only once when the key is created.
Orders and risk
Why is Test Order or Live Confirmation unavailable?
The connection may be unverified, read-only, in the wrong environment, or the Order Intent may not be executable or may have failed hard-risk checks.
Why was a paper order rejected?
Check allowed assets, short and market-order settings, stop and target, leverage, per-trade and daily risk, Expected R, TP1 RR, and price direction.
Why did live confirmation expire?
A natural-language live confirmation ticket expires after five minutes. Generate a new one; an old challenge code cannot be reused.
Why are TP/SL orders missing at the exchange?
The executor currently submits entry orders only. TP/SL values are kept in the plan and audit record. You must place and verify protective orders at the exchange.
Does Kill Switch close positions or cancel orders?
No. It only blocks new exchange submissions. Existing orders and positions must be managed separately at the exchange.