Skip to content

What Is Cortensor Today

Last updated: 2026-06-28

Cortensor is a decentralized AI execution and verification stack. It combines protocol contracts, node roles, router APIs, hosted product surfaces, and agent-facing workflows. The short map below helps route readers toward the right setup guide or product surface.

flowchart TB
  Contracts["Contracts<br/>Eliza modules"]
  Runtime["Node runtime<br/>router / miner / oracle / validator"]
  Router["Router APIs<br/>completion / delegate / validate / factcheck"]
  Products["Products<br/>Portal / Dashboard / Corgent / Bardiel"]
  Ecosystem["Ecosystem<br/>agents / apps / operators / partners"]

  Contracts --> Runtime
  Runtime --> Router
  Router --> Products
  Router --> Ecosystem
  Products --> Ecosystem

Stack Summary

Layer What it does Plain-language role
Contracts Coordinate identity, runtime configuration, node pools, sessions, queues, payments, privacy, stats, validation, and cognitive flows. Protocol coordination layer.
Node runtime Runs router, miner, oracle, validator, pool, quality, and tool roles through the packaged cortensord binary. Decentralized execution layer.
Router API REST route families for completions, delegate, validate, factcheck, x402, trial, A2A, MCP, privacy, and off-chain result handling. Developer and agent entrypoint.
Portal React web app plus FastAPI gateway for API keys, usage, billing surface, and hosted completions. Hosted developer product.
Dashboard Mining/operator dashboard for sessions, nodes, stats, heatmaps, pricing, admin, and private/dedicated session workflows. Operator and network visibility product.
Corgent Agentic trust and execution surface; router primitives map to delegate, validate, and factcheck. Agentic infrastructure surface.
Bardiel Dashboard, website, staking contracts/UI, and public positioning exist. Productized ecosystem agent built on Cortensor/Corgent patterns.
PyClaw Local-first agent runtime that can use Cortensor router surfaces. Agent runtime and client integration path.

Reader Paths

Reader Start with Then read
Developer evaluating API access Getting Started Web2 API Reference, Portal And API Gateway
Router or node operator Miner Node Setup Router Node Setup, Infra And Ops
Product reader Products Portal, Corgent/Bardiel, PyClaw, Dashboard pages
Ecosystem or community reader Use Cases Roadmap, Long-Term Vision
Protocol engineer Contracts And Modules Sessions And Task Queue, Private Inference

Boundaries

  • Production-live claims are limited to surfaces with active deployment details.
  • Bardiel staking and core Cortensor protocol staking are separate topics.
  • Historical roadmap dates are project history, not current setup instructions.
  • Corgent, Bardiel, PyClaw, Portal, and Router Node serve different audiences and stay distinct.

Readiness Checklist

Item Why it matters
Public router endpoint list Prevents examples from pointing to test or private infrastructure.
Canonical contract deployments Required before publishing Web3 setup tables or explorer links.
Portal and gateway production environment Required before hosted API, billing, and key-management docs are final.
Corgent/Bardiel availability Keeps agent-product claims aligned with what users can access.
Tokenomics and legal approval Prevents market-sensitive or policy content from drifting into product docs.