Kusama
Kusama is the permissionless, unaudited canary network of the Polkadot ecosystem, running the same Polkadot SDK (Substrate/FRAME) runtime as Polkadot but with faster governance, lower barriers to entry, and real economic conditions — it is where runtime upgrades, parachain/coretime mechanics, and governance changes ship first before reaching Polkadot. Its developer surface is a chain interface rather than a hosted SaaS API: a public Substrate JSON-RPC 2.0 endpoint at kusama-rpc.polkadot.io exposing 130 live methods (chain, state, author, system, payment, plus the newer chainHead/archive/transaction v1 families) over HTTP and WebSocket, and a REST projection of the same chain state via Substrate API Sidecar at kusama-public-sidecar.parity-chains.parity.io, documented by a 119-operation OpenAPI 3.0 specification. Access is unauthenticated and public-read; write access happens by submitting SCALE-encoded, key-signed extrinsics. The native token is KSM (12 decimals, SS58 prefix 2).
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Kusama the way a machine reads it — 48 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Kusama scores 47.5/100 (developing), with a separate agent-readiness read of 29/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Kusama's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/kusama/"
title="Kusama on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/kusama.svg"
alt="Kusama Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/kusama/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/kusama/"
title="Kusama on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/kusama/card.svg"
alt="Kusama Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Kusama
Each block below is one kind of artifact we hold for Kusama. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 21
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Kusama JSON-RPC API
The public Substrate JSON-RPC 2.0 interface to the Kusama relay chain. Probed live on 2026-07-19: 130 methods are advertised by rpc_methods, spanning chain (blocks/headers), sta...
Kusama accounts API
The accounts API from Kusama — 11 operation(s) for accounts.
Kusama ahm API
Asset Hub Migration information
Kusama blocks API
The blocks API from Kusama — 8 operation(s) for blocks.
Kusama contracts API
The contracts API from Kusama — 1 operation(s) for contracts.
Kusama coretime API
The coretime API from Kusama — 6 operation(s) for coretime.
Kusama node API
node connected to sidecar
Kusama pallets API
pallets employed in the runtime
Kusama paras API
The paras API from Kusama — 9 operation(s) for paras.
Kusama rc accounts API
The rc accounts API from Kusama — 5 operation(s) for rc accounts.
Kusama rc API
relay chain specific endpoints for asset hub
Kusama rc blocks API
The rc blocks API from Kusama — 8 operation(s) for rc blocks.
Kusama rc node API
The rc node API from Kusama — 3 operation(s) for rc node.
Kusama rc pallets API
The rc pallets API from Kusama — 13 operation(s) for rc pallets.
Kusama rc runtime API
The rc runtime API from Kusama — 5 operation(s) for rc runtime.
Kusama rc staking API
The rc staking API from Kusama — 4 operation(s) for rc staking.
Kusama rc transaction API
The rc transaction API from Kusama — 5 operation(s) for rc transaction.
Kusama runtime API
The runtime API from Kusama — 5 operation(s) for runtime.
Kusama staking API
The staking API from Kusama — 4 operation(s) for staking.
Kusama trace API
The trace API from Kusama — 4 operation(s) for trace.
Kusama transaction API
The transaction API from Kusama — 6 operation(s) for transaction.
Scroll within the panel for all 21 ·
Open Collections 21
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONSubstrate API Sidecar accounts API
OPEN COLLECTIONSubstrate API Sidecar accounts ahm API
OPEN COLLECTIONSubstrate API Sidecar accounts blocks API
OPEN COLLECTIONSubstrate API Sidecar accounts contracts API
OPEN COLLECTIONSubstrate API Sidecar accounts coretime API
OPEN COLLECTIONSubstrate API Sidecar accounts node API
OPEN COLLECTIONSubstrate API Sidecar accounts pallets API
OPEN COLLECTIONSubstrate API Sidecar accounts paras API
OPEN COLLECTIONSubstrate API Sidecar accounts rc accounts API
OPEN COLLECTIONSubstrate API Sidecar accounts rc API
OPEN COLLECTIONSubstrate API Sidecar accounts rc blocks API
OPEN COLLECTIONSubstrate API Sidecar accounts rc node API
OPEN COLLECTIONSubstrate API Sidecar accounts rc pallets API
OPEN COLLECTIONSubstrate API Sidecar accounts rc runtime API
OPEN COLLECTIONSubstrate API Sidecar accounts rc staking API
OPEN COLLECTIONSubstrate API Sidecar accounts rc transaction API
OPEN COLLECTIONSubstrate API Sidecar accounts runtime API
OPEN COLLECTIONSubstrate API Sidecar accounts staking API
OPEN COLLECTIONSubstrate API Sidecar accounts trace API
OPEN COLLECTIONSubstrate API Sidecar accounts transaction API
OPEN COLLECTIONScroll within the panel for all 21 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Kusama JSON-RPC Subscription API
The event/streaming surface of the Kusama relay chain, served over WebSocket at wss://kusama-rpc.polkadot.io. Kusama publishes no webhooks — there is no vendor to register a cal...
ASYNCAPIExamples 2
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Kusama Jsonrpc Examples
EXAMPLEKusama Rpc Methods
EXAMPLESecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Kusama — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/kusama · machine-readable index on apis.io
This is an independent, third-party profile of Kusama, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.