Crypto news API

Cited crypto listings, releases, incidents, and governance

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.

Trigger listing and delisting alerts

Filter venue announcements by asset, instrument class, event type, and historical cutoff.

Build protocol incident timelines

Connect releases, status changes, governance, and security events to their official citations.

Keep tokens and instruments distinct

Preserve the relationship between tokens, spot pairs, derivatives, tokenized assets, venues, and underlying references.

Live product proof · checked 23 July 2026 UTC

Six official crypto sources, measured in the open.

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.

933
Records in the checked coverage snapshot
6 / 6
Sources reporting complete in that snapshot
BTC · ETH · SOL
Assets represented by official sources
Verified response excerpt
{
  "symbol": "BTC",
  "event_type": "exchange_announcement",
  "status": "confirmed",
  "availability": "realtime",
  "latency_seconds": 0,
  "license_state": "official_project_metadata",
  "source_count": 1
}
  • Counts are a dated snapshot and will change as source history grows.
  • Every checked crypto source reported rights_state: derived_metadata_only.
  • Realtime and zero latency describe this demo record, not a blanket promise for every source or plan.
Working surface

Filter official crypto events by asset and type.

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

Crypto event fields built for alerts and timelines.

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.

Workflow

From an official announcement to a revision-safe alert.

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.

Test a crypto event query on the free tier.

Inspect source coverage and a real response before you connect REST, SSE, a signed webhook, or MCP to your workflow.