Trigger listing and delisting alerts
Filter venue announcements by asset, instrument class, event type, and historical cutoff.
Track listings, delistings, protocol releases, incidents, security advisories, governance, tokenized assets, and TradFi-linked Binance instruments through a rights-aware event API.
Built for: Crypto researchers and alert builders tracking official exchange, protocol, network, governance, and security events.
Filter venue announcements by asset, instrument class, event type, and historical cutoff.
Connect releases, status changes, governance, and security events to their official citations.
Preserve the relationship between tokens, spot pairs, derivatives, tokenized assets, venues, and underlying references.
The live crypto coverage response reported 933 stored records across Bitcoin Core, Ethereum Foundation, Go Ethereum, Kraken, Agave, and Solana status history. All six sources reported complete for the checked snapshot, with rights state attached to every source.
{
"symbol": "BTC",
"event_type": "exchange_announcement",
"status": "confirmed",
"availability": "realtime",
"latency_seconds": 0,
"license_state": "official_project_metadata",
"source_count": 1
}Query Binance announcement history and official Bitcoin, Ethereum, and Solana project events with token entities, citations, revisions, and point-in-time filters.
GET /v3/intelligence/events?symbol=BTCcurl 'https://api.datacedar.com/v3/intelligence/events?symbol=BTC&type=protocol_release' \
-H 'X-API-Key: dc_...'event_typeListings, delistings, releases, incidents, governance, security, and venue events use a stable taxonomy.
asset_classCrypto spot, perpetuals, tokenized assets, and TradFi-linked contracts stay separate.
entities[]Tokens, protocols, networks, venues, products, and referenced underlyings retain explicit relationship types.
documents[]Exchange announcements and official project sources remain directly citable.
published_at + known_atThe source timestamp and DataCedar availability timestamp support point-in-time filtering.
revision + coverageCorrections, removals, source gaps, and incomplete windows remain visible to the client.
Select an asset, protocol, venue, event class, source class, and eligible historical cutoff.
Open the event and follow its primary exchange, repository, status, or foundation citation.
Keep the native venue instrument class instead of collapsing tokens, spot pairs, and derivatives into a ticker.
Consume stable revisions through REST, SSE, signed webhooks, or the same rights-aware MCP tools.
The live source set includes Binance announcement metadata plus official Bitcoin Core, Ethereum, Solana, and related project or status sources. The coverage endpoint reports the enabled source and freshness state.
No. The product focuses on structured, citable events and official or display-safe source metadata. It does not claim comprehensive publisher coverage or republish unrestricted article bodies.
Yes. Event filters can drive resumable SSE or account-scoped HMAC-signed webhooks. Stable event IDs, revisions, source policy, and idempotency keys support safe downstream processing.
Inspect source coverage and a real response before you connect REST, SSE, a signed webhook, or MCP to your workflow.