Historical information sets
Effective, published, retrieved, and known-at clocks stay distinct.
See what changed, when it became knowable, and which evidence supports it across companies, securities, tokens, protocols, exchanges, regulators, macro releases, and aggregate social activity.
Effective, published, retrieved, and known-at clocks stay distinct.
Events retain source documents, entities, revisions, and coverage state.
Serving checks the active source policy and withholds restricted text.
Search cited stock and crypto events, source evidence, entity timelines, coverage, and revisions through one point-in-time market intelligence platform.
GET /v3/intelligence/eventscurl 'https://api.datacedar.com/v3/intelligence/events?symbol=BTC&limit=20' \
-H 'X-API-Key: dc_...'event_id + versionStable event identity and an immutable revision number keep corrections inspectable.
effective_at + known_atSeparate when an event happened from when the evidence entered the usable information set.
entities[]Resolved companies, securities, tokens, protocols, venues, and macro series retain relationship confidence.
documents[]Display-safe citations retain source identity, canonical URL, publication time, rights version, and evidence role.
coverageA missing result is qualified as empty, partial, stale, restricted, or unavailable instead of being silently ambiguous.
latency_classThe response states the plan delay applied before the event could be served to the requesting account.
Filter the cross-market event spine by asset class, entity, event type, source, time, and display state.
Open one event revision and review its citations, entity links, clocks, and source-rights state.
Follow the stable event ID across corrections or inspect a related cluster when sources disagree.
Save the query, cursor, known-at cutoff, source-policy version, and coverage response with the research result.
A feed emphasizes the latest headline. DataCedar preserves stable event identity, source documents, entity relationships, revisions, effective time, known-at time, and coverage so a historical information set can be reconstructed.
Yes. The event graph covers rights-eligible company, SEC, macro, exchange, protocol, security, listing, and aggregate social-signal sources while keeping asset class and source scope explicit.
Yes. Use known-at filters and event revisions to exclude evidence that entered the system after the simulated cutoff. Coverage state still needs to be checked before treating an empty result as no event.
The source registry, coverage ledger, terminal, REST API, SSE stream, signed webhooks, and remote MCP server are live surfaces of the same rights-aware graph.