We're building the most comprehensive crypto data API we can, and it's still growing — there's always a coin, a field or an endpoint we haven't got to yet.
Please tell us about any data you think Crypto Data API should nail but doesn't. We're data nerds who love to geek out about market data, trading bots, AI agents, or how to make your trading stack work in general. Prefer a form? Send feedback.
20 volatility trading strategies for crypto, from the AlgoBrain wiki. Trade the size of moves, not their direction: long and short vol, DVOL, skew, dispersion, GEX and tail hedges. Each one lists the indicators it uses, the Crypto Data API endpoints that feed it and copy-paste prompts for an AI agent to build and backtest it. All of them are in the API: GET /api/v1/strategies?group=volatility-trading.
Complacency vol buying is a contrarian options strategy that purchases cheap volatility — typically OTM puts or ATM straddles — when three conditions simultaneously signal maximum complacency: sentiment is at an extreme greed reading, DVOL/IV is in a low percentile, and leveraged long positioning is building.
Why it works: Option market participants systematically underprice tail risk when sentiment is extremely bullish and realized vol has been suppressed for weeks — the greedy crowd extrapolates calm, funding confirms that leveraged longs are at maximum commitment, and DVOL sits at a low percentile; buying cheap vol/tails at this exact window purchases insurance at the moment when it is least demanded and most nec
Build the Complacency Vol Buying crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/combinations/complacency-vol-buying.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/derivatives/open-interest
- GET https://cryptodataapi.com/api/v1/hyperliquid/open-interest
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
3. Compute Crypto Fear & Greed Index, DVOL — Deribit Volatility Index, Implied Volatility, Realized Volatility, Open Interest on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Complacency Vol Buying strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/combinations/complacency-vol-buying.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
A crypto long-vol overlay buys convexity on BTC/ETH volatility — long OTM put "wings" and long straddles/strangles on deribit — used primarily as a tail-risk hedge to protect a crypto book against sharp declines and volatility spikes.
Why it works: The overlay pays the variance risk premium to vol sellers in exchange for convex crash protection; the behavioral angle is that in positive-funding regimes the crowd ignores downside protection, making OTM put wings temporarily cheap relative to their cascade payoff. Edge is not positive standalone expectancy but portfolio-level convexity and survivorship during liquidation cascades.
Build the Crypto Long-Vol Overlay (DVOL / Deribit) crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/vix-calls.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/derivatives/open-interest
- GET https://cryptodataapi.com/api/v1/hyperliquid/open-interest
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
3. Compute DVOL — Deribit Volatility Index, Funding Rate, Realized Volatility, Gamma, Implied Volatility on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Crypto Long-Vol Overlay (DVOL / Deribit) strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/vix-calls.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Crypto options dispersion is a correlation trade: sell the relatively rich implied volatility of the crypto "index" (a BTC/ETH major basket, or the dominant single name BTC used as the index proxy) and buy the relatively cheaper implied volatility of single-name constituents (ETH, and where liquid, SOL and a small set of large-cap alts).
Why it works: Index-level (BTC/ETH major-basket) implied vol prices in a higher forward correlation than crypto's single names subsequently realize outside of risk-off crashes; you sell the richly-priced index/major vol and buy cheaper single-name vol, getting paid the implied-minus-realized correlation gap plus the mean-reversion of crypto correlation away from its crisis-time extreme of ~1.
Via API/api/v1/strategies/crypto-options-dispersion
AI-agent prompts
Build it with an AI agent
Build the Crypto Options Dispersion crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/quantitative/crypto-options-dispersion.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
- GET https://cryptodataapi.com/api/v1/volatility/regime
- GET https://cryptodataapi.com/api/v1/volatility/index
- GET https://cryptodataapi.com/api/v1/hyperliquid/candles
- GET https://cryptodataapi.com/api/v1/market-data/klines
3. Compute Funding Rate, Delta, Implied Volatility, Realized Volatility on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Crypto Options Dispersion strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/quantitative/crypto-options-dispersion.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Crypto options volatility selling is the systematic sale of bitcoin and ethereum options on deribit when implied volatility — measured by Deribit's DVOL index — trades persistently above the realized volatility that subsequently delivers.
Why it works: Crypto spot holders, leveraged perp longs, and lottery-ticket call buyers persistently overpay for convexity; the vol seller underwrites that insurance and collects the spread between Deribit implied vol (DVOL) and subsequently realized vol — a variance risk premium that runs fatter than the S&P's because crypto's tail is genuinely fatter.
Via API/api/v1/strategies/crypto-options-volatility-selling
AI-agent prompts
Build it with an AI agent
Build the Crypto Options Volatility Selling crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/quantitative/crypto-options-volatility-selling.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/derivatives/open-interest
- GET https://cryptodataapi.com/api/v1/hyperliquid/open-interest
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
3. Compute Funding Rate, VIX (CBOE Volatility Index), Theta, Realized Volatility, Open Interest on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Crypto Options Volatility Selling strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/quantitative/crypto-options-volatility-selling.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Analytical: DVOL and the equity VIX share the empirical property of strong mean reversion — spikes that are event-driven (a single cascade) revert within days; spikes that represent regime breaks (LUNA/FTX) stay elevated for weeks. The analytical edge is identifying which type of spike has occurred in real time.
Why it works: DVOL is strongly mean-reverting; the counterparty to a post-spike short-vol position is the panic-buyer who bought crash protection at peak pricing and is now trapped paying rich theta; the short-vol desk collects the mean-reversion of the fear premium — with the caveat that regime breaks (not spikes) result in sustained elevated DVOL and a loss.
Build the Crypto Volatility Trading (DVOL) crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/quantitative/vix-trading.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/derivatives/open-interest
- GET https://cryptodataapi.com/api/v1/hyperliquid/open-interest
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
3. Compute Volatility Regime, DVOL — Deribit Volatility Index, Funding Rate, Gamma, Realized Volatility on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Crypto Volatility Trading (DVOL) strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/quantitative/vix-trading.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Event vol buying is a straddle or strangle strategy on BTC and ETH options (primarily on deribit) that enters long-vol positions specifically ahead of scheduled binary-outcome catalysts — protocol upgrades, ETF/regulatory decision dates, Bitcoin halvings, and major token unlocks — when implied volatility has not yet priced the upcoming event.
Why it works: Option market-makers and systematic vol sellers misprice scheduled crypto catalysts by treating upcoming protocol upgrades, regulatory decisions, halvings, and major unlocks as business-as-usual — implied vol does not step up until days to hours before the event; buying straddles when the event-date calendar is public knowledge but IV has not yet priced the catalyst captures the behavioural underr
Build the Event Vol Buying crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/combinations/event-vol-buying.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
- GET https://cryptodataapi.com/api/v1/volatility/regime
- GET https://cryptodataapi.com/api/v1/volatility/index
- GET https://cryptodataapi.com/api/v1/event/calendar
- GET https://cryptodataapi.com/api/v1/hyperliquid/candles
3. Compute Volatility, DVOL — Deribit Volatility Index, Implied Volatility on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Event Vol Buying strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/combinations/event-vol-buying.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Deribit market-makers hedge their net delta position continuously. That hedging is mechanical and non-discretionary — they have no choice. When net dealer gamma is positive (they are net long gamma), they sell into rallies and buy into dips to stay delta-neutral, creating a stabilising force.
Why it works: Deribit market-makers must delta-hedge their net option positions mechanically; above the gamma-flip level their hedging stabilises price (buy dips, sell rallies), below it they amplify moves (sell dips, buy rallies); knowing the aggregate net gamma position predicts whether the next daily move will be mean-reverting or trending.
Build the Gamma Exposure (GEX) Trading crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/combinations/gamma-exposure-trading.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/derivatives/open-interest
- GET https://cryptodataapi.com/api/v1/hyperliquid/open-interest
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
3. Compute Delta, Candlestick Patterns, Moving Averages, Open Interest on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Gamma Exposure (GEX) Trading strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/combinations/gamma-exposure-trading.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
GARCH volatility timing uses a Generalised Autoregressive Conditional Heteroskedasticity model to forecast the next-period realised volatility of BTC, ETH, or a basket of crypto perps, then scales exposure inversely to that forecast — cutting size before forecast vol rises and re-levering as it falls.
Why it works: Volatility is persistent and forecastable while next-period returns are not; a GARCH-scaled crypto book cuts exposure before the low-Sharpe high-vol regime that constant-notional retail leverage rides down into liquidation, harvesting the volatility-managed-portfolio premium and avoiding forced deleveraging.
Build the GARCH Volatility Timing (Crypto) crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/quantitative/garch-volatility.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/volatility/regime
- GET https://cryptodataapi.com/api/v1/volatility/index
- GET https://cryptodataapi.com/api/v1/sentiment/macro
- GET https://cryptodataapi.com/api/v1/hyperliquid/candles
3. Compute Realized Volatility, Liquidation, Funding Rate, Volatility Regime, Average True Range (ATR) on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the GARCH Volatility Timing (Crypto) strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/quantitative/garch-volatility.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Leverage-stress tail hedge is a standalone tail-hedge accumulation strategy that buys OTM puts or long-vol instruments (on deribit BTC/ETH options) specifically when a multi-factor leverage-stress composite is elevated — OI/market-cap above a threshold, funding rate stretched positive, and cascade-fuel metrics high — on the thesis that these measurable precondition metrics identify windows when cr
Why it works: Leveraged retail accumulates in perps and options when OI/market-cap is elevated, funding is stretched, and cascade fuel is high — creating the preconditions for a large drawdown crash before the vol surface has repriced; buying OTM puts or long-vol instruments specifically when these measurable stress metrics are elevated captures the window when the crash probability is above its unconditional r
Via API/api/v1/strategies/leverage-stress-tail-hedge
AI-agent prompts
Build it with an AI agent
Build the Leverage Stress Tail Hedge crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/combinations/leverage-stress-tail-hedge.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/derivatives/open-interest
- GET https://cryptodataapi.com/api/v1/hyperliquid/open-interest
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
3. Compute DVOL — Deribit Volatility Index, Open Interest, Funding Rate on 1d bars (pinned: interval=1d, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Leverage Stress Tail Hedge strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=1d (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/combinations/leverage-stress-tail-hedge.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
A long-vol overlay is a permanent, rolling allocation to long options (a Deribit BTC/ETH put ladder plus a DVOL-referenced convexity ladder) attached to a crypto short-vol core book to cap the left tail of the combined portfolio.
Why it works: Not a profit strategy in isolation; the 'edge' is portfolio-level: a small premium spend on Deribit BTC/ETH puts and DVOL convexity caps the left tail of a crypto short-vol core book, dramatically improving the geometric (compounded) return of the combined book.
Build the Long Volatility Overlay crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/long-vol-overlay.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
- GET https://cryptodataapi.com/api/v1/volatility/regime
- GET https://cryptodataapi.com/api/v1/volatility/index
3. Compute DVOL — Deribit Volatility Index, Vega, Delta, Gamma, Funding Rate on 1d bars (pinned: interval=1d, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Long Volatility Overlay strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=1d (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/long-vol-overlay.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Long volatility strategies are options structures that are net long premium: long gamma, long vega, short theta, with convex payoff in either direction (or specifically left-tail for protective/tail variants). They lose small amounts most days and earn outsized payoffs during vol expansions or crisis events.
Why it works: Long-vol books pay the crypto variance risk premium continuously and earn back convex payoff during shocks; the portfolio-level edge is path quality and crisis alpha rather than expected return, and crypto's fatter, more frequent crashes make the convex payoff larger when it arrives.
Via API/api/v1/strategies/long-volatility-strategies
AI-agent prompts
Build it with an AI agent
Build the Long Volatility Strategies crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/long-volatility-strategies.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
- GET https://cryptodataapi.com/api/v1/volatility/regime
- GET https://cryptodataapi.com/api/v1/volatility/index
3. Compute Gamma, Vega, Theta, DVOL — Deribit Volatility Index, Volatility Regime Classification on 1d bars (pinned: interval=1d, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Long Volatility Strategies strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=1d (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/long-volatility-strategies.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Post-panic vol selling enters a short-vol position (selling BTC/ETH options on deribit, typically strangles or OTM puts) after a panic-spike event — defined as a concurrent sentiment extreme (Fear & Greed ≤ 20), elevated IV percentile (DVOL ≥ 85th percentile of its trailing year), and a rapid realized-vol spike — but only once stabilization is confirmed: realized vol is rolling over from its spike
Why it works: Panic events spike IV far above the realized volatility that subsequently delivers after the cascade completes; by entering short-vol only after a sentiment extreme is confirmed AND stabilization signals (rolling realized vol turning over, no fresh cascade in N hours) are present, the seller captures the mean-reversion of the panic premium paid by terrorized spot holders and leveraged longs seekin
Build the Post-Panic Vol Selling crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/combinations/post-panic-vol-selling.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/market-intelligence/liquidations
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
- GET https://cryptodataapi.com/api/v1/volatility/regime
3. Compute Crypto Fear & Greed Index, DVOL — Deribit Volatility Index, Implied Volatility on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Post-Panic Vol Selling strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/combinations/post-panic-vol-selling.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Range trading buys near a well-defined support level and sells (or shorts) near a well-defined resistance level, betting that price will continue oscillating inside a horizontal channel rather than breaking out.
Why it works: Liquidity providers and dealers repeatedly buy near a defined floor and sell near a defined ceiling, fading retail momentum chasers; in a balanced (non-trending) regime price oscillates between these levels and the trader collects the round-trip.
Build the Range Trading crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/range-trading.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/volatility/regime
- GET https://cryptodataapi.com/api/v1/volatility/index
- GET https://cryptodataapi.com/api/v1/indicators/technical
- GET https://cryptodataapi.com/api/v1/hyperliquid/candles
- GET https://cryptodataapi.com/api/v1/market-data/klines
3. Compute Support and Resistance, Bollinger Bands, Skew, Relative Strength Index (RSI) on 15m bars (pinned: interval=15m, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Range Trading strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=15m (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/range-trading.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Short volatility strategies are options structures that are net short premium: short gamma, short vega, long theta, with concave payoff. They make money most days collecting theta and lose multiples of accumulated theta during vol shocks.
Why it works: Sellers of BTC/ETH options collect a persistent premium (the variance risk premium) for absorbing the crash convexity that leveraged perp longs, spot holders, and lottery-ticket call buyers are behaviorally and structurally compelled to lay off — a premium that runs fatter than the S&P's because crypto's tail is genuinely fatter.
Via API/api/v1/strategies/short-volatility-strategies
AI-agent prompts
Build it with an AI agent
Build the Short Volatility Strategies crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/short-volatility-strategies.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/derivatives/open-interest
- GET https://cryptodataapi.com/api/v1/hyperliquid/open-interest
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
3. Compute Gamma, Vega, Theta, DVOL — Deribit Volatility Index, Funding Rate on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Short Volatility Strategies strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/short-volatility-strategies.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Skew trading harvests the implied-volatility skew of crypto options — the difference in implied volatility between out-of-the-money puts and calls on the same expiry, almost always traded on Deribit (which clears ~85-90% of global BTC/ETH options volume).
Why it works: Tail-hedgers and FOMO call buyers overpay for the rich wing of the BTC/ETH surface (downside puts in stress, upside calls in euphoria); the skew trader sells that rich convexity delta-hedged and is paid the variance/skew risk premium for warehousing gamma and vega the crowd refuses to hold.
Build the Skew Trading (Crypto Options) crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/quantitative/skew-trading.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
- GET https://cryptodataapi.com/api/v1/volatility/regime
- GET https://cryptodataapi.com/api/v1/volatility/index
3. Compute Implied Volatility, Funding Rate, Realized Volatility, Cboe SKEW Index, Volatility Skew on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Skew Trading (Crypto Options) strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/quantitative/skew-trading.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Straddles and strangles are long-volatility option structures that profit from a large move in either direction. A long straddle buys a call option and a put option at the same strike and expiration; a long strangle buys an OTM call and an OTM put at different strikes — cheaper, but needing a bigger move to pay off.
Build the Straddle & Strangle crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/technical-analysis/straddle-strangle.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
- GET https://cryptodataapi.com/api/v1/volatility/regime
- GET https://cryptodataapi.com/api/v1/volatility/index
- GET https://cryptodataapi.com/api/v1/hyperliquid/candles
3. Compute Theta, Implied Volatility, Delta, Vega, Volatility Regime on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Straddle & Strangle strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/technical-analysis/straddle-strangle.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
A strangle is a two-leg options structure: an out-of-the-money call option and an out-of-the-money put option at different strikes but the same expiration.
Build the Strangle crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/technical-analysis/strangle.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
- GET https://cryptodataapi.com/api/v1/volatility/regime
- GET https://cryptodataapi.com/api/v1/volatility/index
- GET https://cryptodataapi.com/api/v1/hyperliquid/candles
3. Compute Delta, Vega, Gamma, DVOL — Deribit Volatility Index, Implied Volatility on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Strangle strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/technical-analysis/strangle.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Tail risk hedging is a portfolio-insurance discipline that buys deep out-of-the-money (OTM) BTC/ETH put options on deribit, plus long DVOL-linked volatility (straddles/strangles and variance structures), to provide asymmetric protection against crypto crashes.
Why it works: Vol sellers (Deribit strangle writers, on-chain option vaults) chronically underwrite the left tail of crypto's distribution; the tail hedger buys the underpriced wing and collects the convex payoff when the tail fires — the edge is portfolio-level survivorship and rebalancing capital, not standalone positive EV.
Build the Tail Risk Hedging crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/quantitative/tail-risk-hedging.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/derivatives/open-interest
- GET https://cryptodataapi.com/api/v1/hyperliquid/open-interest
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
3. Compute DVOL — Deribit Volatility Index, Funding Rate, Volatility Regime, Open Interest on 1d bars (pinned: interval=1d, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Tail Risk Hedging strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=1d (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/quantitative/tail-risk-hedging.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
A volatility swap is an over-the-counter (OTC) forward contract that pays the difference between the realized volatility of an underlying over the contract life and a fixed volatility strike (set at inception near prevailing implied volatility), multiplied by a vega notional.
Why it works: An OTC forward on realized volatility paying (realized vol − strike) × notional; on BTC/ETH the sellers harvest the crypto variance/volatility risk premium because the strike (anchored to DVOL implied vol) systematically exceeds subsequent realized vol, in exchange for bearing crypto's fat crash convexity.
Build the Volatility Swap crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/volatility-swap.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
- GET https://cryptodataapi.com/api/v1/volatility/regime
- GET https://cryptodataapi.com/api/v1/volatility/index
- GET https://cryptodataapi.com/api/v1/hyperliquid/candles
3. Compute Realized Volatility, Implied Volatility, DVOL — Deribit Volatility Index, Volatility on 1d bars (pinned: interval=1d, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Volatility Swap strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=1d (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/volatility-swap.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Volatility trading encompasses a family of strategies that seek to profit from changes in the level of market volatility rather than from the direction of the underlying asset's price.
Why it works: Crypto spot holders, leveraged perp longs, and lottery-ticket call buyers systematically overpay for convexity, so Deribit implied vol (DVOL) exceeds subsequently realized vol most of the time; disciplined sellers (and accurate vol forecasters) harvest that spread in exchange for bearing crypto's genuinely fatter tail.
Build the Volatility Trading crypto trading strategy using the CryptoDataAPI (X-API-Key header, base https://cryptodataapi.com).
1. Read the playbook first: GET https://cryptodataapi.com/api/v1/algobrain/page?path=wiki/strategies/volatility-trading.md
2. Pull the inputs:
- GET https://cryptodataapi.com/api/v1/derivatives/funding-rates
- GET https://cryptodataapi.com/api/v1/hyperliquid/funding-rates
- GET https://cryptodataapi.com/api/v1/derivatives/open-interest
- GET https://cryptodataapi.com/api/v1/hyperliquid/open-interest
- GET https://cryptodataapi.com/api/v1/market-intelligence/options
- GET https://cryptodataapi.com/api/v1/volatility/implied
3. Compute Implied Volatility, DVOL — Deribit Volatility Index, VIX (CBOE Volatility Index), Funding Rate, Realized Volatility on 4h bars (pinned: interval=4h, lookback=500 bars, universe=BTC,ETH,SOL unless the playbook says otherwise).
4. Emit entry/exit rules, position size (risk 1% of equity per trade) and a stop, as JSON: {"symbol","side","entry","stop","target","size_pct","reason"}.
5. State which regime the rules are valid in (GET /api/v1/regimes/current) and stand aside outside it. Research only — do not place orders.
Backtest it
Backtest the Volatility Trading strategy on CryptoDataAPI history before trusting it.
- Bars: GET https://cryptodataapi.com/api/v1/backtesting/klines?symbol=BTC&interval=4h (Pro)
- Funding: GET https://cryptodataapi.com/api/v1/backtesting/funding?symbol=BTC (Pro)
- Rules: from the playbook at /api/v1/algobrain/page?path=wiki/strategies/volatility-trading.md
Pinned: fees 4.5 bps taker per side, 2 bps slippage, funding applied every 8h, signals on bar close only (no lookahead), 70/30 in-sample/out-of-sample split. Report CAGR, Sharpe, max drawdown, trade count and out-of-sample vs in-sample decay.
Any key works, Free included — mint one in a single call. The list endpoint returns summaries; the per-slug endpoint adds the prompts, edge mechanism and data inputs. Full playbooks come from /api/v1/algobrain/page?path=… using each entry's wiki_path. Or use the MCP server.
What are volatility trading crypto trading strategies?
Trade the size of moves, not their direction: long and short vol, DVOL, skew, dispersion, GEX and tail hedges.
Which indicators do volatility trading strategies use?
Most often Funding Rate, DVOL — Deribit Volatility Index, Implied Volatility, Realized Volatility.
Can an AI agent build these strategies from an API?
Yes. GET /api/v1/strategies?group=volatility-trading lists them; GET /api/v1/strategies/{slug} returns the build and backtest prompts, and each prompt names the exact Crypto Data API endpoints to call. Any API key works, Free included.