Classify
Identify token, perpetual, or other product form before assigning an underlying equity mapping.
A stock-like ticker on a crypto venue may represent a token, perpetual derivative, or another synthetic product. DataCedar keeps the original product class, venue behavior, underlying mapping, and holder-rights boundary visible instead of merging it with the primary listed share.
Generated from the current public Binance Spot and USD-M catalogs. Classifications support discovery; product documents control legal interpretation.
Snapshot July 26, 2026 at 08:07 AM UTC
Tokenized stock data describes crypto-venue instruments that reference equities, ETFs, or other traditional assets. The data model must distinguish economic reference from legal ownership and preserve product documents, venue terms, trading hours, settlement, and mapping provenance.
Identify token, perpetual, or other product form before assigning an underlying equity mapping.
Retain venue symbol and attach a reviewed underlying identifier with source provenance.
Represent crypto-venue hours, reference methodology, settlement, FX, and underlying-market sessions separately.
Expose stated holder rights and limitations without implying ownership, dividends, voting, or redemption.
Product boundary: The generated July 26, 2026 ledger includes publicly served one-minute bStock bars and daily Web3/Ondo candles. These products are never described as legally equivalent to listed shares, and Web3 one-minute history is not offered.
curl "https://api.datacedar.com/v3/tokenized-assets?status=trading"{
"data": [{ "symbol": "AAOIBUSDT", "asset_class": "tokenized_equity_spot" }],
"coverage": {
"cataloged": true,
"price_history": "source_dependent",
"public_serving": true
}
}Examples document the public contract and may use illustrative values or redacted identifiers. Availability fields and rights filters are authoritative for the active environment.
Review venue and product documentation.
Assign legal and economic product type.
Version the underlying-reference relationship.
Compare sessions, prices, status, and public rights.
A product labeled with an equity ticker may not confer ownership, voting, dividends, custody, or redemption. Those rights come from product documentation, not a symbol string.
The API keeps product type prominent in every response.
A crypto venue may trade while the underlying exchange is closed. Prices can then reflect venue liquidity, funding, indicative references, FX, and expectations.
Cross-market analysis must align sessions and state which price can actually trade.
The dynamic Binance catalog provides the discovery surface, including inferred bStocks-style pairs and TradFi perpetuals.
DataCedar serves each instrument only within its reported history boundary: bStocks use Spot one-minute bars, Web3/Ondo uses daily candles, and TradFi perpetuals use the derivatives bar route.
The names may resemble one another, while legal rights, trading venue, hours, liquidity, settlement, and price formation can differ materially.
Not necessarily. The product may be a token or derivative referencing an equity without providing ordinary share ownership or rights.
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.
Understand and evaluate Binance historical archives, spot symbols, one-minute OHLCV, backfill reconciliation, and independent storage.
Model crypto perpetuals and futures with contract identity, mark and index prices, funding, open interest, liquidations, expiries, history, and gaps.
DataCedar stores raw source objects and normalized history independently, with coverage and rights enforced before serving.
Start free