Omni AI News

A decision-ready market event stream, without rebuilding raw-news infrastructure.

Raw feeds leave terminal teams with source adapters, repeated headlines, inconsistent payloads, and ambiguous instruments. Omni AI News turns 50+ active market-news sources into a compact stream of clustered events with sentiment, impact, symbol mapping, AI summaries, and versioned analysis lineage.

At a glance

Coverage
50+ active sources 56 distinct feeds were observed in the 30 days ending 15 July 2026; the private inventory is not published.
Signal quality
Clustered events Exact and vector dedupe reduce repeated headlines before AI analysis and presentation.
Action path
News → chart Resolved instruments open beside chart, order, risk, and portfolio context.

Why It Matters

What traders and researchers should take away

  • Repeated headlines waste attention; event clustering makes one developing story easier to follow.
  • Tradable symbol mapping is more useful than a generic topic tag when a trader needs to inspect price and exposure.
  • The same event can power the public feed, terminal modal, Price:News chart, alerts, and share links.

How it works

What the product uses behind the scenes

  • The ingest layer stores source messages before the analysis layer performs filtering, dedupe, clustering, and structured enrichment.
  • The terminal API adapts news events into history and live websocket contracts used by the web and PWA surfaces.
  • The paid public API uses an allow-listed news_event.v1 contract, includes model/schema/prompt lineage, and removes raw source messages and model payloads.
  • REST uses product-scoped API keys and tiered limits; WebSocket clients exchange that key for a single-use ticket that expires after 60 seconds.
  • Display-oriented symbol resolution connects event entities to Hyperliquid and IBKR instruments without exposing private feed configuration.

Notes

Things to know

  • AI summaries are decision support, not a guarantee of market direction or completeness.
  • Confidence and impact describe the event analysis, not expected investment returns.
  • Public documentation omits private feed inventory, prompts, production thresholds, credentials, and host topology.

From noisy messages to one market event

Layered filtering and clustering reduce repetition before a story reaches the trader.

  • Store source messages and normalize the incoming contract.
  • Apply noise filtering, exact dedupe, embedding similarity, and event-cluster updates.
  • Generate structured summaries only when the event adds useful context.

Why integrate Omni instead of raw news

One public-safe contract replaces source-by-source ingestion and moves terminal teams closer to a useful customer experience.

  • Avoid maintaining individual parsers, reconnect logic, and inconsistent payload shapes.
  • Reduce repeated alerts by following one clustered event as a story develops.
  • Route events into charts, watchlists, portfolios, risk views, alerts, and automation using normalized fields.

Tradable routing and Price:News

An event becomes useful when it opens beside the affected market and current account state.

  • Map entities to canonical Hyperliquid or IBKR instruments.
  • Carry confidence, impact, event tags, and concise reasoning into the visible card.
  • Deep-link the event into chart, news modal, risk, and execution context.

Standalone REST and WebSocket API

Paid clients receive versioned, public-safe events without internal prompts or raw source payloads.

  • Use x-api-key for REST history and to create a short-lived WebSocket ticket.
  • Pro supports 500 items/request, seven-day lookback, and 60 REST requests/minute.
  • Enterprise supports 2,000 items/request, 30-day lookback, and 600 REST requests/minute.

References

Implementation references

  • AI news pipeline

    omni-terminal/docs/AI_NEWS_PIPELINE.md

    Documents the public-safe ingest, dedupe, clustering, API, and terminal flow.

  • News display contract

    omni-terminal/docs/NEWS_DISPLAY.md

    Documents symbol resolution, display behavior, and terminal news surfaces.

  • Public API specification

    omni-terminal/static/openapi.yaml

    Defines the versioned AI news REST, WebSocket ticket, and event contracts.