Stock and crypto terminal

Monitor cited stock and crypto events in one terminal

Move from a delayed or realtime event feed into the exact evidence graph, known-at timeline, source policy, saved view, and delivery configuration without changing products.

Built for: Analysts who want to scan events, verify the underlying evidence, save a feed, and send alerts without building a front end first.

Scan one stock-and-crypto event feed

Filter by asset, entity, event class, source, time, and rights-visible display state.

Open the evidence behind a card

Review citations, clocks, entity links, source policy, corrections, and historical revisions in context.

Turn a saved view into an alert

Reuse the terminal filters for an account-scoped, HMAC-signed webhook subscription.

Live product proof · checked 23 July 2026 UTC

The terminal opens onto an inspectable event record.

The live demo returned a confirmed BTC exchange announcement with stable event and revision IDs, a known-at timestamp, source and document counts, availability, licensing state, and record-level latency. Those are the same qualifying fields the terminal is designed to keep beside the headline.

Confirmed
Status on the checked BTC event
1 source
Evidence source retained with the record
0 sec
Latency on this specific demo record
Verified response excerpt
{
  "event_id": "256dc527dbc2127721ce1a1a9d02ba83",
  "revision_id": "572f93fce1d0fb1c6374b0f79daefe58",
  "event_type": "exchange_announcement",
  "known_at_ms": 1784712887770,
  "document_count": 1,
  "status": "confirmed"
}
  • This is a dated live-response excerpt, not a mocked terminal card.
  • Plan delay and source eligibility remain explicit; this one record does not guarantee universal realtime delivery.
  • Use the keyless MCP demo to inspect the contract before creating an account.
Working surface

Open the event feed and evidence workspace.

Filter stock, crypto, macro, regulatory, and protocol events; inspect citations and corrections; save views; and configure signed alerts.

/dashboard/intelligence
Event feed → evidence drawer → asset timeline
Saved view → signed webhook
Coverage → source policy → known-at cutoff
Response model

The terminal surfaces that qualify every event.

feed state

Every card retains event identity, revision, source class, asset scope, and plan delay.

evidence drawer

Citations, document display state, entity links, clocks, and correction history stay one click from the event.

asset timeline

Resolved stock, crypto, protocol, venue, and macro events share one chronological research view.

coverage panel

Source freshness, universe, rights policy, latency, and missing states qualify every search result.

saved view

Reusable filters preserve asset class, event type, source, query, time window, and display-state choices.

delivery state

Webhook endpoint, signing status, retries, last delivery, and automatic suspension remain account-scoped.

Workflow

Scan, verify, reconstruct, and automate from one view.

01

Scan

Filter the event feed across stocks, crypto, macro, regulators, exchanges, and official protocol sources.

02

Inspect

Open a cluster to review primary evidence, source conflicts, resolved entities, and revision history.

03

Reconstruct

Apply a known-at cutoff and use the asset timeline to see only evidence eligible at that point.

04

Automate

Save the view or create a signed webhook using the same filters and source-rights controls.

Built for

Active research across stocks and crypto.
Evidence review before an event-driven decision.
Saved feeds and webhook alerts tied to stable event revisions.

Explicit boundaries

The terminal states its plan delay instead of implying realtime.
Restricted source bodies remain unavailable.
Market charts are included only where the source can be publicly served.

Frequently asked questions

Is the market intelligence terminal realtime?

Eligibility depends on the account plan and source. The terminal states the applied latency class—15 minutes, five minutes, one minute, or realtime eligibility—instead of silently presenting delayed events as live.

Can I inspect the evidence behind an event?

Yes. The evidence drawer exposes display-safe citations, canonical source URLs, publication and known-at clocks, entity relationships, source policy, and event revision history.

Can terminal filters drive alerts?

Yes. A saved filter can become an account-scoped webhook subscription. Deliveries are HTTPS-only, HMAC-SHA256 signed, idempotent, retried, and disabled after repeated failures.

Open the terminal and inspect a cited event.

Start with the feed, open the evidence drawer, check source coverage, and save the exact filter you want to monitor.