Skip to main content

Vision

ClyptQ’s Data Marketplace brings third-party data directly into the operator framework. Instead of writing custom data pipelines, builders access vendor data as standard FIELD inputs — the same way they access OHLCV data today. Data is either provided by ClyptQ (pre-licensed and included in the platform) or purchased by builders through vendor licensing agreements brokered by ClyptQ.

Licensing Model

ClyptQ-Provided Data

Data that ClyptQ licenses in bulk and provides to all users:

Vendor-Licensed Data

Data accessed through ClyptQ’s licensing partnerships with vendors:
How it works:
  1. ClyptQ negotiates redistribution licenses with data vendors
  2. Builders subscribe to datasets through the ClyptQ marketplace
  3. Data is delivered as standard FIELD inputs — no custom integration
  4. Billing is either per-use (API calls) or monthly subscription
  5. Vendors receive revenue share based on usage
Pricing tiers:

Vendor Integration Requirements

For a vendor to be listed on the ClyptQ marketplace:
  1. API availability — REST or WebSocket API with documented endpoints
  2. Historical data — Minimum 1 year of backfillable history for backtesting
  3. Licensing terms — Redistribution rights for ClyptQ platform usage
  4. Data format — Convertible to TaggedArray (numeric values with symbol alignment)
  5. Update frequency — Defined update schedule (real-time, hourly, daily)

Data Categories

News & Sentiment

Real-time and historical news with structured metadata for event-driven strategies. FIELD integration:

Fundamental Data

Financial statements, ratios, and corporate actions for equity strategies. FIELD integration:

Crypto On-Chain Data

Blockchain-native analytics for crypto strategies. FIELD integration:

Alternative Data

Non-traditional data sources for alpha generation. FIELD integration:

Macro & Economic Data

Macroeconomic indicators for regime detection and macro-overlay strategies. FIELD integration:

Platform Integration

Data as FIELD

All marketplace data follows the same FIELD protocol:
Examples:
  • FIELD:glassnode:onchain:exchange_inflow
  • FIELD:benzinga:news:sentiment
  • FIELD:simfin:fundamentals:pe_ratio
  • FIELD:fred:macro:fed_funds_rate

Observation Specs

Each data category gets its own ObservationSpec:

Backtest Compatibility

Marketplace data supports backtesting through historical backfill:
  • Daily resolution data (fundamentals, macro): Full historical coverage
  • Hourly resolution data (on-chain, news sentiment): 1-3 years historical
  • Real-time data (news events, social): Paper/live mode only (ephemeral)
Data that cannot be reliably backfilled is marked ephemeral and follows the same pattern as semantic operators.

Revenue Model

Timeline