Market data and providers
Know the source. Know the time. Know what is missing.
A scanner is only as current and complete as its approved inputs. TraderBase keeps source timing, licensing, account access, and unavailable data inside the product model.
Data principles
Normalize without inventing
Quotes, trades, aggregates, reference values, news, filings, earnings, and halt information can have different coverage and timestamps. Missing input stays missing.
Carry time and delay
Scanner events retain provider market time and visible recency. Delayed, stale, reconnecting, offline, and unavailable states take precedence over a generic live label.
Approve every surface
A source appearing in code or documentation does not prove production rights. Each provider, field, user class, geography, tier, cache, alert, and AI use requires approval.
Data categories
Different inputs answer different questions.
- Market activity
- Trades, quotes, aggregates, session highs and lows, volume, VWAP, spread, and market status.
- Reference data
- Exchange, market cap, shares outstanding, reported float, corporate actions, and other company fields.
- Catalyst context
- Available news, SEC filings, earnings, offerings, and related timestamps or source attribution.
- Derived scanner state
- Deterministic rankings, conditions, events, cooldowns, recency, and deduplication produced by TraderBase services.
Questions
Market-data FAQ
Is every TraderBase market-data field always available?
No. Coverage varies by provider product, license, exchange session, symbol, field, deployment configuration, and account entitlement. TraderBase keeps unavailable fields distinct rather than inventing values.
Is TraderBase data always real time?
No. Free market data is delayed by 15 minutes. Paid access can be real time only when the configured feed is approved, licensed, entitled, enabled, connected, and current for that surface.
Does TraderBase expose provider credentials to the browser or Agent?
No. Provider credentials and canonical market publication remain server-side. TradeBase Agent receives bounded normalized TraderBase output, not upstream credentials or publishing authority.