Catalog
Snapshot active and inactive instruments, precision, filters, and native status instead of rebuilding history from today's list.
DataCedar combines verified public archive files with ongoing live capture, stores raw objects in R2, normalizes its own tables, and records the exact coverage boundary. Binance remains the named source venue, not a runtime serving dependency or a claim of consolidated crypto coverage.
Generated from canonical normalized observations and immutable object manifests on the DataCedar OVH validation deployment.
Snapshot July 26, 2026 at 08:07 AM UTC
Binance historical data is venue-specific instrument and market history exposed through Binance archives and APIs. Reproducible use requires catalog snapshots, archive checksums, UTC rules, row reconciliation, live handoff checks, and stream-specific usage rights.
Snapshot active and inactive instruments, precision, filters, and native status instead of rebuilding history from today's list.
Hash every archive object, validate its rows, and keep file and retrieval manifests in owned R2 storage.
Map archive and live messages into stable DataCedar tables without losing native identifiers or timestamps.
Test archive-to-live boundaries, duplicates, reconnects, and expected continuous intervals.
Product boundary: Counts are a build snapshot generated July 26, 2026. DataCedar intentionally stores research-grade minute bars rather than the full Binance tick, depth, derivatives, or options surface.
curl "https://api.datacedar.com/v3/crypto/BTCUSDT/bars?timeframe=1Min" \
-H "X-API-Key: $DATACEDAR_API_KEY"{
"venue": "binance",
"market": "spot",
"active_spot_symbols": 1369,
"stored_candles": 30794211,
"public_serving": true,
"history": "deepening_by_instrument"
}Examples document the public contract and may use illustrative values or redacted identifiers. Availability fields and rights filters are authoritative for the active environment.
Snapshot exchange metadata and product status.
Download and checksum elapsed archive files.
Capture live messages with event and receive time.
Compare boundaries, gaps, and canonical counts.
Public archive files reduce request volume for elapsed data and provide deterministic file-level inputs. Checksums and row counts should be verified before normalization.
The raw file belongs in an immutable manifest so a table can be rebuilt later.
REST is useful for bounded catalog and reconciliation calls. WebSocket streams reduce live polling but add reconnect, ordering, and sequence responsibilities.
The normalized schema should not change depending on which acquisition path produced the row.
Binance exposes multiple spot and derivatives interfaces, order books, funding, open interest, liquidations, options, indexes, and product-specific catalogs.
DataCedar's implemented production capture is narrower, and the page keeps that distinction explicit.
The source remains Binance, while storage, normalization, coverage evidence, and the downstream contract can belong to DataCedar.
No. The catalog is broad, but the validated historical corpus currently covers 1376 spot pairs and selected live streams. Full spot depth, derivatives, options, and other surfaces remain gaps.
Evaluate one-minute crypto OHLCV, symbols, and coverage through a venue-explicit, independently stored, rights-aware data model.
Build historical cryptocurrency datasets with venue identity, UTC intervals, delisted instruments, source lineage, continuous-market gap checks, and frozen cutoffs.
Model crypto perpetuals and futures with contract identity, mark and index prices, funding, open interest, liquidations, expiries, history, and gaps.
Research tokenized and equity-linked crypto products with explicit instrument type, venue, underlying mapping, trading status, reference methodology, and rights.
DataCedar stores raw source objects and normalized history independently, with coverage and rights enforced before serving.
Start free