trading-signals

TraderSpy's AI signals are automated reads of the market: a named preset fires when several technical conditions line up on one crypto futures pair, a validator scores the alignment, and the published signal carries an entry, a take-profit ladder, a stop and — later — what actually happened. The signals feed at https://traderspy.app/signals publishes every one with its resolved outcome. Your job is to fetch, translate and contextualise them; the decision stays with the user.

Tools

Three argument behaviours that are easy to get wrong:

• importance is inclusive downward. high returns high only, medium returns high AND medium, low returns everything. To show "medium and above" pass medium, not low.
• coin is a prefix match on the pair name. BTC matches BTCUSDT and also BTCDOMUSDT; check the coin field of each row before presenting "BTC signals".
• limit is what gets rendered. In hosts that draw signal cards, every fetched row becomes a card. If the user asks for "the last 5", pass limit: 5 — do not fetch 20 and show 5.

What a signal row contains

strategyName (the preset, e.g. "OBV Divergence Buy (4H)") · action buy / sell · timeframe 1h / 4h / 1d · price at trigger · targets[] as {label, type, pct} where pct is measured from price · triggeredConditions[] in plain language · importance · signalStrength weak / moderate / strong / very_strong · resolutionStatus · createdAt.

Convert target percentages to prices before showing them — users think in prices:

• buy: TP = price × (1 + pct/100), SL = price × (1 − pct/100)
• sell: TP = price × (1 − pct/100), SL = price × (1 + pct/100)
• reward-to-risk at TP1 = TP1 pct ÷ SL pct (a 0.7 R:R is normal for this system, whose first target sits close to entry; read it together with the hit rate from get_signal_stats, and do not call a sub-1 R:R "bad" on its own).