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. Public sockets use per-plan concurrent connection caps, bounded client messages, and crash-safe expiring leases.
- Customer API keys are named, shown only once, stored as one-way hashes, immediately revocable, and newly issued News API keys require the news_api:read scope.
- 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 allows 2 concurrent news sockets; Enterprise allows 10. Send a JSON ping at least every 60 seconds; inactive sockets close after 120 seconds.
- Public client messages are capped at 4 KiB, and each ticket is consumed by its first upgrade attempt.
- Pin news_event.v1 when needed; each immutable analysis id carries a stable logical event_id plus correction, backfill, or reanalysis metadata.
- 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.
Five-minute integration path
Start with a server-side key, process cursor history idempotently, then add ticketed live delivery.
- Create a named news_api:read key and keep the one-time value in a server-side secret manager.
- Request news_event.v1 history from api.omniterminal.app and commit next_before_timestamp only after processing a page.
- Request a fresh single-use ticket for every WebSocket connection or reconnect; never put the long-lived key in the URL.
- Send application-level JSON pings, honor X-RateLimit-Reset on 429 responses, and use capped jittered backoff for transient failures.
- De-duplicate immutable revisions by id and group corrections, backfills, or reanalysis by event_id.
References
Implementation references
News API five-minute quickstart
omni-terminal/docs/NEWS_API_QUICKSTART.mdProvides copy/paste REST, pagination, WebSocket, retry, ticket-renewal, and error-handling examples.
News API lifecycle policy
omni-terminal/docs/NEWS_API_LIFECYCLE.mdDefines dated and object versions, change classes, deprecation notice, revisions, model migrations, and backfills.
News API changelog
omni-terminal/docs/NEWS_API_CHANGELOG.mdLists public contract and behavior changes, affected surfaces, compatibility, and required client action.
AI news pipeline
omni-terminal/docs/AI_NEWS_PIPELINE.mdDocuments the public-safe ingest, dedupe, clustering, API, and terminal flow.
News display contract
omni-terminal/docs/NEWS_DISPLAY.mdDocuments symbol resolution, display behavior, and terminal news surfaces.
Public API specification
omni-terminal/static/openapi.yamlDefines the versioned AI news REST, WebSocket ticket, and event contracts.