Historical information sets
Effective, published, retrieved, and known-at clocks stay distinct.
Market events API
One revisioned event graph for stocks and crypto
DataCedar turns source documents into a durable event spine so applications can search what happened now and reproduce what was available then.
Cited event graph
Events retain source documents, entities, revisions, and coverage state.
Rights-aware output
Serving checks the active source policy and withholds restricted text.
Working endpoint
Query the product, not a promise.
Build against stable event IDs, evidence citations, resolved entities, effective and known-at times, corrections, clusters, coverage, SSE, webhooks, and MCP.
GET /v3/intelligence/events/{event_id}curl 'https://api.datacedar.com/v3/intelligence/events/{event_id}' \
-H 'Authorization: Bearer dc_...'Response model
Fields that preserve the research trail.
event_id + revisionThe identity survives correction while every material version remains separately addressable.
effective_atWhen the underlying market or company event took effect, independent of discovery time.
published_at + known_atWhen the evidence was published and when it became eligible in DataCedar stay distinct.
entities[] + confidenceResolved assets and organizations retain relationship type, match evidence, and review confidence.
evidence[]Primary and supporting documents identify their source, rights version, and role in the event.
cluster_id + correction_stateRelated reports, conflicts, replacements, and tombstones can be reconciled without deleting history.
Research workflow
From discovery to a reproducible result.
Acquire
Rights-approved connectors preserve raw source objects, retrieval time, checksums, and source identifiers.
Normalize
Deterministic rules map documents into an event taxonomy and resolve entities with reviewable confidence.
Revise
New evidence creates an event revision or related cluster record rather than overwriting historical truth.
Distribute
REST, SSE, webhooks, and MCP apply the same plan latency, rights, history, and account filters.
Built for
Event-driven research and backtest annotations.
Cited agent retrieval through REST or MCP.
Resumable SSE feeds and HMAC-signed webhook delivery.
Explicit boundaries
Generated fields retain their evidence set and cutoff.
Low-confidence matches enter review rather than silently becoming facts.
Rights revocation is checked at serving and delivery time.
Frequently asked questions
What counts as a market event?
The taxonomy includes company, SEC, earnings, macro, regulatory, exchange, listing, protocol, governance, incident, security, and correction events. Each class retains its own entities, clocks, evidence, and coverage state.
How are corrections represented?
The stable event ID links immutable revisions. Clients can inspect the current revision, retrieve a historical cutoff, and process correction or tombstone delivery without losing the earlier record.
Do REST, webhooks, and MCP return different rights states?
No. They compose the same serving rules. Account plan, history window, latency class, source rights, removal state, and display policy are enforced before each delivery channel returns the event.
Inspect the coverage before you build the workflow.
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.