Data Coverage Scope

Acceso focuses on the data categories most production systems end up rebuilding: chain primitives, market data, and derived analytics.

Coverage is exposed as normalized resources and derived views. This keeps client code stable as upstream vendors change.

Coverage areas (high level)

Solana primitives

• Accounts, transactions, and program activity as app-ready primitives.

• Wallet and token views built on consistent typing and naming.

DeFi analytics

• Pricing, trades, and liquidity views across venues.

• Derived analytics like OHLCV and aggregates (when supported).

Prediction markets

• Market metadata and lifecycle (active, resolved).

• Trade and pricing dynamics (when supported).

Acceso normalizes data into consistent schemas across sources. That reduces client branching and vendor-specific parsing.

Normalization rules (why it matters)

• Consistent field naming.

• Consistent typing.

• Consistent “shape” for similar resources across venues.

Normalization is a contract. It is what lets you add new venues without rewriting downstream code.

Where to see what is supported today

For the current supported set (and what "supported" guarantees): Supported Networks & Protocols.

Example (illustrative, not a strict schema)

{
  "resource": "trade",
  "venue": "dex-or-market",
  "timestamp": "2025-01-01T00:00:00Z",
  "base_asset": "…",
  "quote_asset": "…",
  "side": "buy|sell",
  "price": "…",
  "size": "…",
  "tx": {
    "signature": "…",
    "slot": 0
  }
}