Crypto news API

Crypto events beyond generic headlines

Track listings, delistings, protocol releases, incidents, security advisories, governance, tokenized assets, and TradFi-linked Binance instruments through a rights-aware event API.

Start free Open API reference

Historical information sets

Effective, published, retrieved, and known-at clocks stay distinct.

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.

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=BTC
curl 'https://api.datacedar.com/v3/intelligence/events?symbol=BTC&type=protocol_release' \
  -H 'X-API-Key: dc_...'
Response model

Fields that preserve the research trail.

event_type

Listings, delistings, releases, incidents, governance, security, and venue events use a stable taxonomy.

asset_class

Crypto 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_at

The source timestamp and DataCedar availability timestamp support point-in-time filtering.

revision + coverage

Corrections, removals, source gaps, and incomplete windows remain visible to the client.

Research workflow

From discovery to a reproducible result.

01

Filter

Select an asset, protocol, venue, event class, source class, and eligible historical cutoff.

02

Trace

Open the event and follow its primary exchange, repository, status, or foundation citation.

03

Classify

Keep the native venue instrument class instead of collapsing tokens, spot pairs, and derivatives into a ticker.

04

Deliver

Consume stable revisions through REST, SSE, signed webhooks, or the same rights-aware MCP tools.

Built for

Create listing and delisting alerts.
Build protocol and network-incident timelines.
Join crypto events to Binance spot, derivative, bStock, and tokenized-asset coverage.

Explicit boundaries

Binance is a venue source, not consolidated crypto pricing.
Official link metadata is served without copying unrestricted article bodies.
One-minute bars are the durable public market-history target; tick archives are not the moat.

Frequently asked questions

Which crypto sources are included?

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.

Is this a generic crypto news publisher feed?

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.

Can I build crypto alerts from the API?

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 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.

View coverageOpen terminal