Breakout Radar

Overview

**Historical endpoint: `/api/influencers`.** The board now lives at `/api/radar`, the path that names what it returns; the old one answers identically while clients migrate and carries `Deprecation`, `Sunset` (2027-03-19) and a `Link` to its successor. `/api/influencers` keeps `view=accounts` and `view=traders` for good — those really are about influencers. Hybrid pre-breakout radar whose social evidence comes from the influencers you choose. `leaderboard` and `candidates` hold the same variable core set (0–30), never padded. Every row must clear all filters: favourable regime, verified market cap of at least $300M, earnings clear, 0–8% from the pivot and a mature pattern measured on closed daily candles. Posts keep the original wording in `text` and add English in `textEn`; `translation` reports whether that coverage is complete or partial. `executionPlan` adds the pivot, stop, mechanical 1R/2R/3R levels and position size from the risk budget and position cap you pass. Cached for about 3 hours, rebuilt on demand.

Use it toSee only pre-breakout setups that clear every filter, and choose which influencers provide the social evidence.

Codes and field names stay stable so integrations do not break; `labels` holds their human-readable English labels. That now includes the section codes: `labels.section` reads `setup-explicado`, `mencionado` and `descartado`, and `labels.sections` reads the keys of the `sections`/`returnedSections` counters, which are plurals of those codes rather than the codes themselves. The three sections are a two-tier board: `setup-explicado` is a social mention that passes the full structural contract and carries an explained setup; `mencionado` keeps a social mention visible when it only fails quality gates (the chart is not verified, the mention is); `descartado` is reserved for hard reasons — already broke its pivot, outside the forming window, unknown or imminent earnings, or market cap below the floor. A client can therefore tell a verified setup from a raw mention without losing either. The counters keep their keys on purpose — publishing English duplicates beside them would double any client that sums the object, so they are translated rather than aliased. `risk_budget_usd` defaults to 1000 and `max_position_usd` is optional; sizing uses whole shares and exposes utilization and which constraint limits the size. `executionSummary` totals assume every returned candidate triggers: they are a scenario, not a recommended portfolio. `plannableByFreshness` separates plans computable with current, stale or unknown data. `executionPlan` is a deterministic sizing template, not a recommendation or a prediction. `dataFreshness` separates `priceAsOf`/`quoteAgeSeconds` from the age of the technical cache: stale means a quote older than seven days or a technical cache older than two hours. If the board is stale and its rebuild fails, `sourceStatus` gives the cause, `sourceNeedsAttention` is true when retrying cannot help (for example an inactive X subscription), `ageDays` gives the age in whole days and `sourceDetail` explains it; the rebuild stops at the first batch on an inactive subscription. With personal accounts, `personalization.sourceStatus` appears when their refresh failed for an account-wide X cause; X is then not queried for 10 minutes and the previous overlay is served if it exists. **What the pattern quality grade means.** `patternQualityScore` starts at 42 and adds six measured components, each capped so no single one can carry a chart: proximity to the pivot (up to 16, `16 − distToPivot × 1.5`), base maturity (up to 12, `(baseAgeSessions − 10) × 0.6`), volume dryness (up to 12, `12 × (1.15 − volContraction)`), base compactness (up to 12, `12 − range20Pct × 0.45`), how many times the pivot was tested (up to 12, `pivotTouches × 3`) and a structure quorum (2 points for each of six signals: range contracting, rising lows, dry volume, a strong pivot cluster, price in the upper half of the base and a compact recent range). The total is clamped to 0–100. `grade` reads that score: **A at 80 or above** (textbook), **B from 65 to 79** (solid), **C below 65**. The score only ever RANKS a valid setup: `patternQualityPass` is a separate hard contract, and a chart that trips any of its checks — already broke, immature base, illiquid, extended, choppy, untested resistance, a recent spike or gap — is rejected whatever it scored, with the failed checks listed in `patternQualityReasons`. A high score cannot rescue a chart the contract rejects, and every rejection says which check failed. `screenFunnel` reports how the technical lane reached its candidate count — charts scanned, with data, with a setup, selected — and names the gates that rejected the rest, so a zero can be read as a weak tape or as a broken gate.

Coverage

Call it

Send your ra_live_… key in the x-api-key header. Pick your language:

curl "https://raspberrytrades.com/api/radar?setup=breakout&risk_budget_usd=500&max_position_usd=10000" \
  -H "x-api-key: ra_live_your_key_here"