Cowrie Research

transpose-primary-sources-2026-04-27

3 min read

Transpose primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

What the official materials say

1) Docs introduction / current framing

  • URL: https://docs.transpose.io/
  • Key takeaways:
    • Transpose describes itself as a complete, powerful, and performant Web3 data suite.
    • The docs say its indexing engine processes and enriches raw blockchain data in realtime.
    • The same page separates the product into Verified Endpoints, Custom Endpoints, and a SQL Analytics API, which is a strong categorization clue that this is a multi-surface data platform rather than only a dashboard or only a query engine.

2) Dataset inventory / chain coverage

  • URL: https://docs.transpose.io/
  • Key takeaways:
    • The docs enumerate datasets chain by chain and split them into settlement, asset, protocol, and pricing layers.
    • Example tables shown publicly include accounts, blocks, logs, traces, token transfers, NFT sales, lending events, DEX swaps, bridge events, token prices, and liquidity OHLC series.
    • Public chain coverage shown in the docs includes Ethereum, Polygon, Optimism, and Base, with many decoded table families exposed directly in the navigation.

3) Quickstart / concrete workflow

  • URL: https://docs.transpose.io/quickstart/
  • Key takeaways:
    • The quickstart walks through a real use case: pulling CryptoPunks NFT sales from a Verified Endpoint and then using the SQL Analytics API to calculate daily floor-price style outputs.
    • This is an especially useful primary-source clue because it shows how Transpose expects developers to combine prebuilt endpoints with direct SQL access in production workflows.
    • The quickstart also reveals the basic auth model: API keys passed in X-API-KEY headers, with free-tier team accounts available via the app dashboard.

4) Official site / company-level framing

  • URL: https://www.transpose.io/
  • Key takeaways:
    • The official site frames the product around data transformation and ERP-style infrastructure for digital assets.
    • That broader business framing is narrower and more marketing-heavy than the docs, but it still supports the idea that Transpose is selling structured operational data infrastructure rather than only charts or research.
    • In practice, the docs are the clearer source of truth for the technical product surface.

Whitepaper / technical-doc status

  • No canonical Transpose whitepaper or litepaper was found in this pass.
  • The docs set is much more useful than a missing paper because it exposes the data model, API surfaces, and workflow style directly.
  • In practice, the docs home and quickstart are the strongest primary sources for this project snapshot.

Research notes

  • Best current category for the library: blockchain data infrastructure / indexing / analytics API / SQL query platform.
  • Key categorization insight: Transpose should be treated as a full data-access suite spanning realtime indexing, prebuilt endpoints, custom endpoint generation, and direct SQL analytics.
  • Another useful note for future scouting: docs-first data vendors with table-level chain inventories and multiple API/query surfaces often have much richer product scope than their public homepage suggests.

Graph View