Overview

Last updated: 2026-06-28

Cortensor's current stack spans setup paths, product surfaces, protocol references, router APIs, and operator workflows.

Read In Order

Page	Purpose
What Is Cortensor Today	Current stack map and status boundaries.
Architecture At A Glance	How clients, routers, sessions, miners, validators, and contracts fit together.

Core Message

Cortensor is not just an API wrapper around a model. It is a network for routing AI work, coordinating distributed execution, and validating outputs through redundancy, reputation, and proof-oriented task lifecycles. The core ideas are decentralized AI inference, open model access, blockchain coordination, scalable developer access, and agent-ready validation.

Three layers stay separate:

• the protocol and contracts that coordinate the network.
• the node runtime that performs routing, mining, oracle, validation, and support roles.
• the products and integrations that expose this network to developers, customers, and agent ecosystems.

Current Storyline

flowchart LR
  Narrative["Decentralized AI access"]
  Protocol["Protocol<br/>contracts and sessions"]
  Runtime["Runtime<br/>routers, miners, oracles, validators"]
  Products["Products<br/>Portal, dashboard, Corgent, Bardiel"]
  Ecosystem["Ecosystem<br/>builders, operators, partners"]

  Narrative --> Protocol
  Protocol --> Runtime
  Runtime --> Products
  Products --> Ecosystem
  Runtime --> Ecosystem

Main Areas

Area	What it covers
Protocol	Contracts, sessions, task queues, payments, validation, and network coordination.
Node runtime	Routers, miners, oracles, validators, pools, quality services, and operator tooling.
Products	Portal, API gateway, Router Node, Dashboard, Corgent, Bardiel, PyClaw, and agent apps.
Ecosystem	Token utility, staking, builders, partners, use cases, and community programs.