DocsRadar

Natural-language scanner

Type a scan in plain English. What the translator understands, where it falls back, and how to phrase requests it'll handle well.

6 min read

At the top of Radar there’s a single text input labeled Describe a scan. Type something like “sell 30-delta puts on tech with 30+ days,” hit enter, and Tradient’s NL translator turns the sentence into a fully-populated filter object and runs it. This page covers what the translator can and can’t do, and how to phrase requests so they parse cleanly.

What it’s for

The natural-language input is the fastest path from “I want a specific scan that doesn’t exist in the library” to a running scan. It’s not magic — under the hood it’s a deterministic translator that recognizes a finite vocabulary of strategies, parameters, and ticker scopes. But within that vocabulary it’s very fast.

What the translator understands

Strategies

Any of the following keywords map to a specific strategy:

  • Cash-secured puts:“sell puts,” “CSPs,” “cash secured puts,” “naked puts.”
  • Covered calls:“sell calls against stock,” “covered calls,” “CCs.”
  • Iron condors:“iron condor,” “condor,” “IC,” “short range.”
  • Vertical spreads:“bull put spread,” “bear call spread,” “bull call spread,” “bear put spread,” “debit spread,” “credit spread.”
  • Long straddles:“straddle,” “buy a straddle.”
  • Short strangles:“short strangle,” “sell strangle.”

Parameters

Numbers attached to recognized parameter words become filters:

  • DTE:“30 days,” “30+ DTE,” “between 30 and 45 days,” “weekly” (≤ 7 DTE), “monthly” (≥ 25 DTE).
  • Delta:“30 delta,” “0.20 delta,” “low delta,” “ATM” (≈ 0.50), “OTM” (< 0.50).
  • IV rank:“IV rank above 50,” “low IV rank,” “high IV.”
  • POP:“at least 70% probability,” “high POP.”
  • Annualized return:“at least 20% annualized,” “high yield.”
  • Volume / liquidity:“liquid,” “at least 500 contracts.”
  • Earnings:“before earnings,” “avoid earnings,” “earnings this week.”

Ticker scopes

  • Tickers by name:“on AAPL,” “on TSLA NVDA AMD.”
  • Sectors:“on tech,” “on financials,” “on energy.” (Maps to a curated tag list, not a live sector classifier.)
  • Watchlists:“from my watchlist,” “from my income watchlist.”
  • Universe:“from the liquid universe” (default), “from the SP500,” “from the QQQ.”

Examples that work

sell 30-delta puts on tech with 30+ days
iron condors expiring in 30-50 days on names with IV rank above 50
covered calls on AAPL MSFT GOOGL with at least 20% annualized
high POP credit spreads from my income watchlist
cheap straddles on stocks reporting earnings this week
weekly cash-secured puts with 70% POP on liquid names

Where the translator falls back

If a request is ambiguous, the translator picks a sensible default and tells you what it inferred via a chip in the result bar. If the strategy isn’t recognized at all, the request is rejected with an explanation of which keywords weren’t found. If a number can’t be attached to a parameter (“buy 50 puts” — does 50 mean strike, delta, contracts?) the translator drops the number and you get a warning.

The result chips after a NL scan are editable — if the translator inferred something you didn’t mean, just edit the chip and the scan reruns.

Tip
Think of the translator as a power user’s shortcut, not as a chatbot. The faster way to phrase a request is to use terms a real options trader would use — strategy name, delta number, DTE window, IV rank. Conversational phrasing (“find me something good for next week”) works too but produces less specific scans.

What it doesn’t do

The translator is not an LLM and doesn’t make judgment calls about strategy choice. It will not interpret “trade the dip on TSLA” as anything specific — pick a strategy first, then describe its parameters. For strategy guidance, see How to choose a strategy.

Where to go next