Apex Hunter
Adaptive Multi-Exchange SPOT Capital-Allocation Engine — Not a Grid Bot
Apex Hunter is not a fixed-coin bot and not a grid bot. It is an adaptive, deterministic, auditable capital-allocation engine. The customer supplies capital and operating constraints; Apex Hunter decides WHAT to trade, WHETHER to trade or wait, WHEN, WHERE, HOW MUCH, which execution METHOD to use, and WHY — all from real exchange data, never from fabricated or mocked state.
The strategy engine is completely exchange-neutral. Grid is one possible execution method among several. The same engine runs across Binance, OKX, Bybit, Bitget, and Coinbase without any exchange-specific trading logic leaking into the strategy layer. Exchange adapters translate native API contracts into normalized domain contracts; the strategy never sees exchange-specific DTOs.
Every material decision — exchange, instrument, allocation, method, market snapshot hash, qualification evidence, regime classification, opportunity calculation, risk result, strategy/config version, and reason codes — is recorded in an immutable audit ledger. The system must explain what it did, when, how much capital it committed, which exchange/asset/method it chose, why, what evidence supported it, and what the exchange actually executed.
Decision Pipeline
Every trade candidate passes through every stage. Any stage can reject and record why.
Strategy never submits orders. Risk never invents opportunities. Execution never invents prices or quantities. These are hard architectural boundaries. WAIT is a valid and frequent outcome — no daily profit target forces a trade.
How It Compares
| Typical Grid Bot | Apex Hunter |
|---|---|
| Fixed coin (BTC/ETH hardcoded) | Full exchange universe qualification on every cycle u2014 no hardcoded coins |
| Grid is the only strategy | PASSIVE_LIMIT, STAGED_LIMIT, AGGRESSIVE_LIMIT, or WAIT u2014 grid is one method |
| Averages down indefinitely (martingale) | ADVERSE u2192 RECOVERY requires renewed asset/liquidity/economics checks u2014 no auto-buy |
| Forces trades to hit daily targets | WAIT is a valid outcome u2014 no daily profit target forces execution |
| No audit trail | Immutable decision record: snapshot hash, reason codes, strategy version, decision ID |
| Exchange-specific logic in strategy | Exchange-neutral contracts u2014 strategy never sees exchange DTOs |
| Fabricates fills when exchange is slow | Fails closed u2014 no simulator fallback in production runtime |
| Blows up on one bad coin | Per-instrument concentration ceiling + aggregate deployed-capital ceiling |
| No economic edge check | Opportunity gate: expected move vs fees + spread + slippage + buffer |
| Treats submission as fill confirmation | Authoritative reconciliation u2014 submission u2260 fill, ambiguous states require lookup |
Problems Apex Hunter Solves
Your bot keeps buying a coin that is in a downtrend
The market regime engine classifies markets as TRENDING, RANGING, or TRANSITIONING using measurable slope-vs-ATR and efficiency metrics. Trend permission blocks buying into falling markets. Fails closed as UNSUITABLE for unhealthy or stale data u2014 never invents a regime.
Your bot trades even when there is no mathematical edge
The opportunity economics gate requires every trade to clear round-trip fees (10 bps/side), spread, slippage allowance, and a configured execution buffer. If the net edge is negative or marginal, the result is WAIT u2014 not a forced trade. No daily profit target overrides this.
Your bot blows up on one bad coin
Dynamic capital allocation caps per-instrument concentration and aggregate deployed capital. Protects configured quote/stablecoin reserve. Non-actionable opportunities receive zero allocation. The same engine scales from $20 to $5,000+ without hardcoded universal percentages.
You cannot tell why your bot made or skipped a trade
Every decision records: exchange, instrument, allocation, method, market snapshot hash, qualification evidence, regime, opportunity calculation, risk result, strategy version, and stage-tagged reason codes (e.g. OPPORTUNITY:NET_EDGE_TOO_SMALL). Every decision is traceable from signal to outcome.
Your bot treats a submission acknowledgement as a confirmed fill
Submission acknowledgement is never treated as fill confirmation. Ambiguous states require authoritative lookup and reconciliation. The execution probe requires private-stream subscription evidence before submission. Duplicate-order protection prevents double-entry.
Your bot is locked to one exchange and breaks when you switch
Exchange-neutral architecture: the strategy, risk, and analytics layers never see exchange-specific DTOs. Switching from OKX to Binance requires only a configuration change u2014 the strategy logic is identical. Each connector passes its own certification suite before being enabled.
Operating Modes
Every decision is recorded and evaluated u2014 no orders sent. Full audit trail active. Use to validate strategy behavior before committing capital.
Explicit operator start required via dashboard with typed confirmation. LIVE accounts also require APEX_LIVE_TRADING=enabled on the host environment.
Emergency stop engaged. Persists across restarts. No stream or reconciliation event can move the runtime out of BLOCKED while engaged. Does not cancel exchange orders.
Runs against exchange demo/testnet environments. Execution probe requires explicit operator confirmation. No live capital at risk.
Simple, Transparent Pricing
Subscription based on authorized trading capital. Your capital stays on your exchange.
$20u2013$1,000 authorized trading capital. 10-day free trial. Your capital stays on your exchange.
Get Started$1,001u2013$5,000 authorized trading capital. 10-day free trial. Automatic recurring billing.
Get StartedAbove $5,000 authorized trading capital. 10-day free trial. Tier based on authorized capital, not transient balance spikes.
Get StartedConnector Certification Status
Each connector must pass its own API-contract, authentication, market-data, order, reconciliation, rate-limit, and runtime validation before it is enabled for customers.
REST V5, WebSocket, HMAC signing, server-clock sync, public/private streams, heartbeat, batch orders (20-order ceiling), authoritative reconciliation
HMAC-SHA256 REST, exchange-clock sync, Spot symbol filters, myTrades by symbol, user-data WebSocket, execution-report normalization, Testnet probe
V5 Spot, HMAC-SHA256, Unified wallet, realtime/history order lookup, 20s heartbeat, Testnet lifecycle probe (submit u2192 stream u2192 lookup u2192 cancel)
UTA V3 Spot, REST signing, Demo Trading, authenticated private WebSocket, reconnect/deduplication, Demo lifecycle tooling
Advanced Trade, CDP JWT authentication, GTC limit execution, authenticated User WebSocket, account refresh, LIVE-only certification tooling
Algorithmic trading involves substantial risk of loss. Past performance does not guarantee future results. Apex Hunter is a technical system, not financial advice. Always validate with paper trading before live deployment.
Get Started
Ready to trade smarter with Apex Hunter?
Contact us to request early access or learn more about how Apex Hunter can work for your trading strategy.
