Superior-Trade Intelligence
Use Unified API market intelligence to rank current setups and inspect one canonical symbol. Read the returned evidence; never treat a score as advice.
Files in this skill
| File | What it covers |
|---|---|
references/api.md |
Unified scan/setup parameters and contract-shaped examples. |
references/workflow.md |
Scan → setup → backtest → deploy workflows. |
references/buckets.md |
Optional strategy lenses for interpreting evidence; these are not Unified response categories. |
references/glossary.md |
How to explain common evidence fields without assuming they are always present. |
Route selection
- List/ranking question →
GET /context/scan. Usebucket=allfor an open-ended scan, oralts/hip3when the user narrows the universe. Usecategory=allunless they explicitly requestmomentum,mean_reversion,breakout, orvolume.top_ndefaults to 10 and must not exceed 50. - Single-symbol question → first resolve a canonical symbol with
GET /context/markets, then callGET /context/setup/{symbol}with the URL-encoded canonical value.
Presenting results
- State
computed_atwhen the response includes it. - Present the returned
symbol,category, andscorewithout renaming them to an older bucket taxonomy. - Cite the exact
evidencevalues returned for each conclusion. - Treat setup fields such as regime, levels, volatility, and funding as optional unless they appear in the response.
- Before recommending capital, apply an appropriate strategy lens, run a backtest, and explain the principal risk.
Never manufacture an empty or unavailable scan from training data. Scores are deterministic market computations, not guarantees or a signal service.