Introduction to API Trading
API connection basics
The user does not manage the execution logic. The only active parameter is the global risk multiplier.
Understanding risks is the foundation of responsible participation.
Cryptocurrency trading involves extreme risk. Significant losses, up to total loss of funds, are possible. Past performance does not guarantee future returns.
Algorithms can experience extended drawdowns during structural market shifts.
Funds remain on the exchange. You assume the risk of exchange insolvency or hacking.
API limits, latency, or server downtime can result in unexecuted orders and losses.
We operate purely as an execution layer. You maintain absolute custody and control over your capital.
Application and compatibility check. Strict capital limits from $1,000 to $10,000 per trading node to ensure execution capacity.
Creating a sub-account on your exchange. Read and Trade permissions only. Withdrawals are technically disabled.
Select your Risk Multiplier (x1 to x3) in the dashboard. The server-side algorithm autonomously handles the rest.
40% Technology Fee strictly on positive High-Water Mark profit. First month: Weekly invoices. Then: Monthly (1st to 5th).
Built as a high-performance execution infrastructure. We do not disclose strategy logic, but we provide full transparency on system architecture and risk controls.
Frontend (Next.js) is physically isolated from Backend (Python) and the core Execution Engine (Rust) to ensure maximum security.
Server-side order execution written in Rust. Operates autonomously without client influence on micro-timing or routing.
Independent module controlling exposure limits, drawdown thresholds, and emergency position liquidation (Kill Switch).
Real-time telemetry, audit logging, and automated alerts for infrastructure state and exchange API latency.
Our infrastructure mitigates counterparty risks by enforcing zero-trust API management.
Your API keys are strictly bound to our isolated execution servers. They are completely useless if accessed from outside our infrastructure.
We require the use of exchange sub-accounts. This physically isolates the trading module from your main holdings.
Permissions are locked to Read and Trade. The engine cannot and will not execute transfer or withdrawal requests.
Complete transparency regarding the vulnerabilities of algorithmic execution.
Losses are an inevitable part of systematic trading. Even profitable systems experience periods of drawdowns.
Cryptocurrency markets are highly volatile. Prices can change sharply due to structural shifts.
Funds are held on the exchange. You assume the risk of exchange insolvency or technical failure.
USDT and other stablecoins may temporarily or permanently lose their peg to the fiat currency.
Evaluating infrastructure efficiency through the lens of risk management. We focus on capital protection and drawdown control.
Maximum floating network drawdown
Ratio of return to accepted risk
Ratio of gross profit to gross loss
Percentage of profitable closing cycles
Average time capital is exposed in trades
Strict volume limit per single instrument
The presented metrics are model-based and derived from historical algorithm testing data. Past performance does not guarantee future returns. Cryptocurrency markets exhibit extreme volatility, and actual results may vary significantly, up to a partial or complete loss of funds.
Monitor algorithmic execution strictly in read-only mode. You retain ultimate control by setting the global Risk Multiplier, while the engine handles dynamic position sizing and daily margin recalculation.
Educational materials focused on systemic risk and execution architecture. We build infrastructure for those who understand the market.
Understanding drawdowns, exposure limits, and position sizing mathematics.
How systematic execution differs from manual trading. Infrastructure vs emotions.
Best practices for securing exchange API keys, IP whitelisting, and sub-accounts.
Order books, slippage, liquidity, and latency implications in crypto markets.
Structured knowledge base
API connection basics
Systematic risk approach
Understanding drawdowns
Sharpe ratio and other metrics
Adapting to volatility changes
Secure API configuration guide
All funds remain strictly on your personal exchange account. Aurexis does not accept deposits and does not hold client assets.
No. The API keys must be generated with Read and Trade permissions only. Our system automatically rejects any keys with Withdrawal enabled.
Absolutely not. Cryptocurrencies are highly volatile. Algorithmic execution is subject to drawdowns, and complete loss of capital is possible.
We charge a 40% Technology Fee strictly on realized positive performance (High-Water Mark). Invoices are generated automatically. First month: weekly. Following months: on the 1st of each month.
Yes. You have full control. You can use the "Kill Switch" in your dashboard or simply delete the API key on your exchange.
These limits are enforced for strict capacity and risk management per trading system, ensuring optimal execution without excessive slippage.
Strict definitions of our operational perimeter and regulatory status.
Aurexis operates exclusively as a technology and software provider. We provide execution infrastructure, not financial services.
We do not hold, receive, or transfer client funds. All assets remain securely in your personal exchange account at all times.
Nothing on this platform constitutes financial, investment, or legal advice. You are solely responsible for your risk settings.
The operator is not liable for exchange failures, API latency, network downtime, or trading losses incurred while using the software.
Platform connection process
Fill out the application form. No open registration.
Platform requirements assessment.
API setup and activation within 3-5 business days.
Expected connection time: 3-5 business days