Kadena
Kadena was a layer-1 Proof-of-Work blockchain platform built around Chainweb, a braided, parallelized Nakamoto-consensus protocol that scales Bitcoin-style security across many chains for high transaction throughput, together with Pact, its human-readable, Turing-incomplete smart-contract language. Kadena exposed two primary public APIs: the Chainweb Node API (P2P and service endpoints for cuts, blocks, headers, payloads, the mempool, mining, and node info) and the Pact REST API (local, send, poll, listen, spv) for submitting and querying smart-contract transactions on mainnet and testnet. The developer surface includes the kadena.js TypeScript client libraries, the pactjs CLI for type generation, and extensive docs at docs.kadena.io. Kadena Eco supported an ecosystem of dApps, the Marmalade NFT standard, and tooling. NOTE: Kadena the company announced it would cease operations on 2025-10-21; Kadena Mainnet stopped producing blocks on 2025-11-15 and the kadena-io GitHub organization was archived on 2025-12-23. A community edition (kda-community) forked from mainnet on 2025-11-08 and continues the open-source protocol. This profile documents the public API surface as published.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Kadena the way a machine reads it — 19 machine-readable artifacts across 16 APIs, 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 — Kadena scores 37.2/100 (thin), with a separate agent-readiness read of 51/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Kadena
Each block below is one kind of artifact we hold for Kadena. 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 16
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.
Kadena block API
These endpoints return whole blocks, headers and payloads, from the chain database. Generally, blocks are returned in ascending order and include orphaned blocks. For only query...
Kadena blockhash API
These endpoints return block hashes from the chain database. Generally, block hashes are returned in ascending order and include hashes from orphaned blocks. For only querying b...
Kadena config API
The config API from Kadena — 1 operation(s) for config.
Kadena cut API
A cut represents a distributed state of a chainweb. It references one block header for each chain, such that those blocks are pairwise concurrent. Two blocks from two different ...
Kadena endpoint-listen API
The endpoint-listen API from Kadena — 1 operation(s) for endpoint-listen.
Kadena endpoint-local API
The endpoint-local API from Kadena — 1 operation(s) for endpoint-local.
Kadena endpoint-poll API
The endpoint-poll API from Kadena — 1 operation(s) for endpoint-poll.
Kadena endpoint-private API
The endpoint-private API from Kadena — 1 operation(s) for endpoint-private.
Kadena endpoint-send API
The endpoint-send API from Kadena — 1 operation(s) for endpoint-send.
Kadena endpoint-spv API
The endpoint-spv API from Kadena — 1 operation(s) for endpoint-spv.
Kadena header API
These endpoints return block headers from the chain database. Similar to the block endpoints, block headers are generally returned in ascending order and include headers of orph...
Kadena mempool API
Mempool P2P endpoints for communication between mempools. Endusers are not supposed to use these endpoints directly. Instead, the respective Pact endpoints should be used for su...
Kadena mining API
The Mining API of Chainweb node is disabled by default. It can be enabled and configured in the configuration file. The mining API consists of the following endpoints that are d...
Kadena misc API
The misc API from Kadena — 7 operation(s) for misc.
Kadena payload API
Raw literal Block Payloads in the form in which they are stored on the chain. By default only the payload data is returned which is sufficient for validating the blockchain Merk...
Kadena peer API
The P2P communication between chainweb-nodes is sharded into several independent P2P network. The `cut` network is exchanging consensus state. There is also one mempool P2P netw...
Scroll within the panel for all 16 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
kadena-mcp.yml
MCP SERVERSecurity Posture 1
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Kadena — 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 3
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 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/kadena · machine-readable index on apis.io