For Brokers

A structured risk-alert feed built for broker workflows.

Bring timestamped, symbol-level Jason Wheel risk observations into brokerage apps, research surfaces and risk-monitoring systems through a secure server-to-server feed.

Structured JSON Dated observations Partner-specific access
Risk Alert Feed Server to server
01
ObserveGlobal symbol risk conditions are evaluated by scheduled backend scans.
02
PublishEach qualifying observation is stored with structured details and a timestamp.
03
IntegrateYour backend polls incrementally and presents the data within your own experience.
All-symbol scopeIndependent of any individual user's Watchlist
No customer contextNo user, subscription, device or read-state fields
Research destinationsPublic Technical Snapshot and Research links
Reliable pollingIncremental IDs, cursors and idempotent consumption
Current coverage

Risk observations with the context needed to investigate.

Alert types are structured for machine consumption while retaining a concise message suitable for a user-facing timeline.

vol_risk

Volatility risk

Identifies elevated ATR conditions and supplies the observed ATR, ATR percentage and volatility environment.

Example Technical Snapshot
structure_risk

Structure risk

Highlights price outside its normal Bollinger range with price, boundary and percentage-position measurements.

Example Technical Snapshot
earnings_risk

Earnings-window risk

Adds a calendar-day countdown and, when available, current IV, IV percentile, 20-day realized volatility and the IV/RV ratio.

Example Research report
Integration model

Designed for a controlled backend handoff.

Each partner receives an independent ID and secret. Credentials remain in the partner's backend, never in a mobile app, browser bundle or URL.

GET/v1/partners/risk-alerts/feed
Security boundary

The public website never requests the live feed. Partner credentials are exchanged separately during onboarding.

1

Request access

Confirm the intended product surface, operating region, polling model and support contacts.

2

Receive independent credentials

Jason Wheel provisions a partner-specific ID and secret for server-side storage.

3

Complete an initial synchronization

Choose new-record-only activation or a full historical import, then persist the latest committed ID.

4

Poll incrementally

Read records after the committed ID, paginate with the cursor when required and process each ID idempotently.

Representative payload

Stable identifiers, structured evidence and public next steps.

Sanitized exampleNo live credentials or customer data
{
  "id": 324,
  "symbol": "AVGO",
  "security_type": "STK",
  "alert_type": "earnings_risk",
  "severity": "high",
  "details": {
    "earnings_date": "2026-09-08",
    "days_until_earnings": 6,
    "current_iv_percent": 41.25,
    "iv_percentile": 73,
    "realized_volatility_20d_annualized_percent": 27.18,
    "iv_to_realized_volatility_ratio": 1.518
  },
  "links": {
    "primary": {
      "rel": "research",
      "href": "https://www.jasonwheel.com/research/AVGO/"
    }
  },
  "occurred_at_iso": "2026-09-02T14:35:00+00:00"
}
Independent partner keys

One partner cannot authenticate with another partner's assigned secret.

Immutable observations

Stored messages and details preserve what was observed when the alert occurred.

Backward-compatible fields

Optional evidence can expand without invalidating earlier historical records.

Public research links

Each item can direct users to the latest Technical Snapshot and Research pages.

Important boundary

Market-risk information, not an order instruction.

Risk Alert Feed records are generalized, non-personalized market observations. They do not determine suitability, position size, contract selection or whether a customer should transact.

Partner with Jason Wheel

Discuss a brokerage integration.

Tell us about your intended customer experience, technical environment and market coverage. Detailed integration documentation is provided during partner onboarding.