Transpose

• Name: Transpose
• URL: https://www.transpose.io/
• Category: blockchain-data infrastructure company / decoded-schema and endpoint operator / SQL analytics provider
• Tags: ethereum-ecosystem
• Summary: Transpose belongs in companies/, not only projects/, because the useful question is not just where can someone query blockchain data with SQL? but which named operator chooses the realtime indexing coverage, decoded table model, Verified Endpoint catalog, Custom Endpoint workflow, API-key admission, and team-dashboard shell that downstream builders may start treating as their practical source of truth? The real leverage is not a neutral protocol primitive. It is a company-run data and access layer that decides what gets normalized, how it gets exposed, and which production workflow customers inherit.
• What it does:
  • Runs a realtime indexing and enrichment engine for blockchain data rather than exposing only raw node or subgraph output
  • Offers Verified Endpoints for common use cases so customers can consume prepackaged API outputs without writing their own SQL first
  • Offers Custom Endpoints for more tailored application-specific access patterns when the default catalog is not enough
  • Provides a SQL Analytics API so customers can query decoded datasets directly and combine prepared surfaces with bespoke analysis
  • Publishes chain and dataset coverage across settlement, asset, protocol, and pricing tables, with public examples spanning Ethereum, Polygon, Optimism, and Base
  • Uses API-keyed access and team accounts through a dashboard-style workflow, which makes the account and packaging boundary part of the product itself
• Key claims:
  • The docs describe Transpose as a complete Web3 data suite whose indexing engine processes and enriches raw blockchain data in realtime
  • The docs explicitly separate the product into Verified Endpoints, Custom Endpoints, and a SQL Analytics API, which is strong first-party evidence that the company is packaging a multi-surface data platform rather than one narrow analytics feature
  • The quickstart walks users from a prebuilt NFT-sales endpoint into direct SQL analysis, which is a useful clue that Transpose wants customers to treat its curated endpoint layer and its query layer as one combined workflow
  • The same quickstart shows API keys passed in X-API-KEY headers and ties access to team accounts, reinforcing that service admission and account packaging are part of the real operator boundary
  • The docs expose chain-by-chain table inventories across raw and decoded families, which means schema choice and dataset curation are among the company’s main sources of leverage rather than just implementation detail
  • The main site broadens the pitch toward transformed digital-asset data and ERP-style operational infrastructure, which supports reading Transpose as an operator-run data workflow company rather than only a developer toy
• Whitepaper: No classic Transpose company whitepaper is the important artifact here. The strongest primary materials are the docs homepage, the quickstart, the official site, and the existing source bundle in ../whitepapers/transpose-primary-sources-2026-04-27.md.
• Sources:
  • https://www.transpose.io/
  • https://docs.transpose.io/
  • https://docs.transpose.io/quickstart/
  • ../whitepapers/transpose-primary-sources-2026-04-27.md

Why this company note belongs in the corpus

• Transpose is easy to flatten into one more blockchain SQL product, but the practical dependency is a named company that decides which chains get indexed, how tables are normalized, which endpoint shapes become first-class, and how customers authenticate and operationalize the data.
• That makes the entity boundary more useful than a generic project note. The sticky question is who curates the schema and endpoint surface that downstream teams may start treating as operational data truth for analytics, product features, or internal reporting.
• The split between Verified Endpoints, Custom Endpoints, and direct SQL is the clearest signal. It means customers are not just buying raw access; they are inheriting a company-authored ladder of convenience, abstraction, and opinionated packaging.

Internal linkages

• Project-layer alias: transpose.
• Closest adjacent company-layer reads: dune, allium, goldsky, and bitquery.
• Protocol-coordination contrast where data publication is pushed toward a shared network rather than one hosted vendor shell: the-graph.
• Useful neighboring comparison where delivery goes direct to customer-controlled sinks instead of mostly endpoint-and-query packaging: indexing-co.

Protocol / company boundary

• There is not a very useful standalone Transpose protocol doing the main analytical work here.
• The meaningful surface is the company-run data platform: realtime enrichment, decoded-schema curation, prebuilt endpoint design, API-keyed access, custom endpoint packaging, and direct SQL query service.
• Even the most technical-seeming choices such as table naming, decoded-event coverage, or which workflows deserve a Verified Endpoint are company-authored packaging decisions, not neutral protocol baselines.
• That is why this note belongs in companies/: the important dependency is a named operator and service boundary, not an independent network or standard.

Control surface

• Practical leverage sits in which chains and datasets Transpose covers, how decoded schemas evolve, which endpoint shapes get promoted into the official catalog, and how much freshness or completeness users can assume.
• Additional leverage sits in API-key issuance, team-account workflow, rate limits, plan packaging, and the distinction between what is easy through a Verified Endpoint versus what is left to bespoke SQL or custom endpoint work.
• Because Transpose markets itself as transformed operational data infrastructure rather than only a charting site, its schema and access choices can quietly shape product analytics, internal reporting, and downstream automations.
• Read Transpose as a company-run blockchain data access and normalization layer first, not as neutral data plumbing.

Failure-prevention lens

• Ask whether a team is using Transpose for exploratory analytics or as production data infrastructure for dashboards, app features, compliance checks, accounting, or customer-visible reporting.

• Ask which assumptions are inherited from Transpose’s decoded schemas and endpoint definitions rather than reproduced independently from raw chain data.

• Ask what breaks if chain coverage, endpoint semantics, freshness, or API-access policy changes, especially when internal workflows have been built directly around Verified Endpoints.

• Ask whether the team has an escape hatch for critical reporting paths or whether the convenient endpoint catalog has effectively become its authoritative data model.

• Last reviewed: 2026-08-11 UTC