Products
Data Access Portal API SQD Network Supported Chains
Development SDK SQD Cloud SQD 360
Solutions
By Use Case DeFi & Trading Analytics AI Agents Wallets & Payments Compliance
By Industry Stablecoins RWA All Customers
Developers
Get Started Documentation Subsquid Subsquid Labs Dev Chat
Resources
Learn Blog Changelog
Company About Ecosystem Brand Assets
Customers Pricing
Talk to us
All chains
Kusama

Kusama

Substrate Layer 0

Kusama is Polkadot's canary network, a pre-production environment for testing cutting-edge blockchain technology with real economic value.

Website Explorer
Quick Facts
Networks 1
Runtime Substrate
Real-time No
Data tables 0
Category Layer 0
Networks
1
Runtime
Substrate
Coverage
Archive
Start block
0 (genesis)
License
Open-source SDK

Networks

kusama
Substrate mainnet 0 tables

Kusama on SQD

Validated at ingestion

Kusama data is validated by SQD Network workers before it reaches the Portal. Validation is performed across the network rather than by a single ingestion node, so a faulty upstream source can't poison the dataset.

Decoded, schema-typed

Kusama data served as decoded, schema-typed tables, ready to query. Your indexer queries the data directly without writing SCALE parsers.

Full historical archive

SQD's Kusama archive covers historical state in one endpoint. Real-time on the roadmap.

Open-source SDK

Both the Squid SDK and the Pipes SDK are open-source. Connectors for Postgres, ClickHouse, MongoDB, SQLite and Parquet, plus a custom-target hook. Run your Kusama indexer on your own infrastructure or on SQD Cloud.

Build with Kusama data

Common production patterns teams build with SQD on Kusama.

DeFi & Trading

Index swaps, liquidations, and positions on Kusama in real time.

Analytics

Build dashboards and metrics from full Kusama historical state.

AI Agents

Give agents structured, decoded Kusama data with the MCP server.

Wallets & Payments

Power balance, transfer, and history views for Kusama wallets.

Compliance & KYT

Validated Kusama data for transaction monitoring and audits.

Stablecoins

Track every mint, burn, and transfer of Kusama stablecoins.

Real-World Assets

Auditable Kusama data for tokenized RWA issuance and transfers.

Stream Kusama data in two lines

Example below uses the public Kusama endpoint, no API key required for development. For full SDK reference, see the documentation.

1curl --compressed -X POST \
2 'https://portal.sqd.dev/datasets/kusama/stream' \
3 -H 'Content-Type: application/json' \
4 -d '{
5 "type": "substrate",
6 "fromBlock": 0,
7 "toBlock": 100,
8 "fields": {
9 "block": {"number":true,"timestamp":true},
10 "event": {"name":true,"args":true}
11 },
12 "events": [{}]
13 }'
kusama/stream
Substrate · blocks 0–100

Frequently asked questions

How does SQD compare to running a Kusama RPC node?
A Kusama RPC node serves raw bytes for recent state and rate-limits per request. SQD's Portal pre-indexes the full Kusama archive into decoded, schema-typed tables (blocks, transactions, logs) and serves them as a single streaming endpoint. You skip the multi-day node sync, archive storage, monitoring, and scale-out work, and pay only for the data you stream.
What does SQD cost for Kusama data?
The public Portal endpoint at portal.sqd.dev/datasets/kusama is free for development with no API key. Production workloads run on the SQD Portal with tiered pricing based on the network and request volume. See the pricing page for current tiers, or contact us for an enterprise quote.
How is SQD's Kusama data different from Subscan?
Block explorers are read-optimized for human browsing of single blocks or addresses. SQD is built for programmatic indexing: stream millions of Kusama blocks into your own database, run analytical queries across the full history, and back production applications with decoded data. Output is structured tables, not HTML pages, and there are no per-call rate limits geared toward UI traffic. If you wanted to build your own Kusama explorer, the SQD Portal is what you would back it with.
Can I self-host SQD's Kusama indexer?
Yes. Both the Squid SDK and the Pipes SDK are open-source. You can run a Kusama indexer on your own infrastructure pointing at the SQD Network or the Portal. SQD Cloud also offers managed hosting if you'd rather not operate it yourself.
Can I export Kusama data to a data warehouse or pipeline?
Yes. The Pipes SDK streams Kusama data from the Portal into Postgres, ClickHouse, MongoDB, SQLite, Parquet, or a custom target you implement. See the SDK docs for the connector reference.
Does SQD validate Kusama data?
Every Kusama block ingested into SQD is validated by the SQD Network workers (hash chain, parent reference, and where applicable finality) before it reaches the Portal. Validation is performed across the network, not by a single ingestion process, so a faulty upstream node can't poison the dataset.
Does SQD support real-time Kusama data?
Kusama historical data is available through the Portal archive. Real-time streaming for Kusama is on the roadmap, contact us to flag your use case for prioritization.

See other chains supported by SQD

Polkadot

Start building with Kusama

Access Kusama data through the SQD Portal, free tier available.

Try the Portal Read Docs