PUBLIC · SERVER RENDERED · NO INSTALL

Give your AI one page.
Start choosing strategies.

Codex, Claude, OpenClaw, or another harness can read this page without a QuantElse CLI or Skill. It gets the current Catalog, preference cards, recommendation contract, and safe next steps.

AI HANDOFF
Read https://quantelse.trade/context?lang=en as the authoritative QuantElse public advisor context.
Use native single-select question cards in Codex Plan mode. Ask exactly one question at a time and provide only 2–3 mutually exclusive options per question. Follow native_card_flow, including its conditional market and objective questions. After collecting market, objective, risk, and runtime, call the public recommendation endpoint and cite the published strategy slug/version. Do not ask me to install a CLI or Skill. If native questions are unavailable, use the same flow as plain text and do not claim that cards were rendered.
Core content is server rendered. JavaScript is optional.
Codex · Plan mode questions

Use real chat-native
single-select cards.

Near the composer, switch the task mode from Default to Plan, then send the prompt again. Every question has two or three mutually exclusive options, and market selection is split into conditional questions.

  1. 01Switch the task mode beside the composer from Default to Plan.
  2. 02Send the provided prompt again in Plan mode.
  3. 03Codex may render native cards when the current client exposes Plan mode questions.

This page can request native cards but cannot force a chat client to render them. Rendering depends on the current Codex mode and available question tool; other clients should fall back to the same text flow.

Codex changelog ↗
DEFAULTPLAN
Read https://quantelse.trade/context?lang=en as the authoritative QuantElse public advisor context.
Use native single-select question cards in Codex Plan mode. Ask exactly one question at a time and provide only 2–3 mutually exclusive options per question. Follow native_card_flow, including its conditional market and objective questions. After collecting market, objective, risk, and runtime, call the public recommendation endpoint and cite the published strategy slug/version. Do not ask me to install a CLI or Skill. If native questions are unavailable, use the same flow as plain text and do not claim that cards were rendered.
Question map

At most three options per card.

Market

Which market family should we start with?

  • Crypto assets
  • Tokenized stocks
  • Explore markets
Cryptomarket_group = crypto

Which crypto market do you prefer?

  • BTC
  • Altcoins
Exploremarket_group = explore_markets

How should we explore across markets?

  • Cross-venue
  • Compare broadly
Goal

What kind of objective should we narrow down?

  • Risk and return
  • Spread monitoring
  • Compare first
Returnobjective_group = return_profile

Which risk-and-return profile fits your intent?

  • Stability first
  • Balanced growth
  • High volatility
Risk

How much strategy risk can you accept?

  • Low
  • Medium
  • High
Runtime

Where would you prefer the selected strategy to run?

  • Help me decide
  • Managed 24/7
  • My environment
For the harness

Conversation protocol

  1. Tell the user this is strategy discovery, not personalized financial advice.
  2. Ask one question at a time in this order: market, objective, risk, runtime.
  3. Use the option ids exactly; show cards when the harness supports them.
  4. Call the recommendation endpoint, then explain assumptions and caveats.
  5. Offer strategy detail, local runtime, or hosted information as the next step.
Non-negotiable rules
  • Never invent popularity, returns, users, or performance evidence.
  • A planned option with no strategy must return no exact match.
  • Paper is the default. Do not request API keys or place orders.
  • Do not require the professional CLI/Skill for this first-layer flow.
Live catalog JSON ↗
Preference cards

Ask less.
Understand enough.

These are coarse discovery preferences, not a suitability assessment. A planned market with no published strategy returns an honest empty result.

01Which market do you want to explore?
02What are you optimizing for?
03How much strategy risk can you accept?
04Where would you prefer it to run?

Select your preferences and request a recommendation.

Synced from Catalog

17 published strategy definitions.

This snapshot uses the same slug, version, risk, and evidence status as the website and API. Performance remains empty unless verified evidence is published.

BTC/USDT · lowv0.1.0

BTC Conservative Range Grid

Observe whether BTC repeatedly trades around a recent center, then make controlled counter-moves with limited exposure.

ETH/USDT · mediumv0.1.0

ETH Balanced Range Grid

Use a wider band to observe an ETH range while keeping paper trading as the default starting point.

BTC/USDT · lowv0.1.0

BTC Dual-EMA Trend

Use fast and slow averages plus price location to confirm direction and reduce the weight of isolated noise.

ETH/USDT · mediumv0.1.0

ETH Swing Trend

Observe ETH swings with a medium-horizon trend template; signals are less frequent but arrive later.

SOL/USDT · highv0.1.0

SOL Fast Trend Watch

Shorten the signal horizon to observe fast SOL trends; start with paper trading and limited exposure.

BTC/USDT · lowv0.1.0

BTC RSI Mean Reversion

Watch for reversion only when RSI reaches an extreme instead of trading repeatedly in neutral territory.

ETH/USDT · mediumv0.1.0

ETH RSI Reversion Watch

Use a smoother two-hour horizon to identify ETH extremes and avoid chasing neutral readings.

SOL/USDT · highv0.1.0

SOL Extreme-Move Reversion

Trigger only at more extreme thresholds to research reversion after high volatility, not to imply live readiness.

BTC/USDT · mediumv0.1.0

Major-Venue Spread Monitor

Compare net spreads across venues without assuming both legs can be filled safely.

ETH/USDT · highv0.1.0

Hyperliquid Spread Watch

Record quote differences between Hyperliquid and other venues while the execution and backtest model is built separately.

BTC/USDT · mediumv0.1.0

Same-venue Spot-Perpetual Funding Carry

Pair spot with an opposing perpetual leg and study carry after basis, fees, and margin. This is a parameter definition, not a runnable configuration.

ETH/USDT · highv0.1.0

Cross-venue Perpetual Funding Spread

Hold opposing perpetual positions on two venues and study the funding spread without assuming margin and leg risks are solved.

BTC/USDT · highv0.1.0

Cross-venue Spot-Perpetual Carry

Place spot and perpetual legs on different venues for more rate and depth choices, while adding transfer, venue, and leg risk.

BTC Options · highv0.1.0

Options Wheel

Start with a cash-secured put, hold the asset after assignment, then sell a covered call. The lifecycle matters more than one premium.

ETH Options · highv0.1.0

Sell Put DCA

Split a planned purchase budget into cash-secured put tranches. Premium is not risk-free income.

EVENT/USDC · highv0.1.0

Polymarket Late-resolution Strategy

Screen markets near cutoff or resolution while checking rules, evidence sources, dispute windows, and liquidity. No runnable config exists yet.

EVENT/USDC · highv0.1.0

Polymarket Compliant Liquidity Provision

Place controlled limit orders for genuine buying and selling intent with mandatory self-trade prevention. Wash trading and misleading volume are unsupported.

After discovery

Choose the next layer only when useful.

available

Run in my environment

No signup. Use your computer or your own cloud and start in simulation.

Open →
restricted

Explore hands-off hosting

Designed for continuous operation; public self-service is being prepared.

Open →
planned

Use AI for deeper control

More advanced AI-assisted management is planned and is not required here.

Coming later