Naar inhoud
Developer portal

Start building with us.

TokonoMix provides the engineering and commercial infrastructure to build, operate, and deliver enterprise level AI solutions. Explore the full architecture, with production ready components clearly identified.

In plain terms

One integrated architecture built to work as a system

Two paragraphs and six words. If you read nothing else on this page, read this.

The gap

Organisations can buy individual AI models today, but not the engineering stack needed to build, operate, and scale reliable AI products. A model is a capability; a product is an architecture.

The answer

Modern AI should not be a monolithic platform. It should be built from independent layers with clear responsibilities, evolving separately while working together through open interfaces. TokonoMix provides this stack, along with the commercial infrastructure to operate and scale what you build.

Words this page uses
Unattended run
A long agent run that keeps going when a question comes up, parking it for a human instead of waiting.
Consensus
Several models answer the same prompt without seeing each other; a judge writes one verdict and names where they disagreed.
Gateway
The transport in front of the model providers: it carries the call, meters it and bills one account. It makes no decisions.
MCP
Model Context Protocol — the open standard that lets an AI assistant call external tools. Not ours; the components speak it.
DCP
Development Coordination Protocol — the vendor-neutral vocabulary for project state, published at devcopro.org.
Layer
A component with exactly one responsibility and an open interface, replaceable without touching the ones above it.
Two complementary stacks

From AI capabilities to commercial products

One stack builds the capability. The other turns it into a product you can sell. Each has a distinct role.

AI Engineering Stack

Open technologies for reliable AI systems. Independent by design.

creates AI
capabilities
turns them into
commercial products

Digital Commerce Stack

Commercial platforms built on those AI capabilities.

Architecture

How the layers stack

Transport carries messages, coordination gives them meaning, execution does the work, review checks it, commerce sells it, applications use it. Each layer owns one role.

Applications
GalleryZelixAISurfOnline
applications consume ↓
Digital Service Commerce Platform
beheer-v3 — subscriptions · billing · licensing · provisioning (not AI)
beheer-v3 commercialises
Where tokonomix.ai fits

The site you are on is the stack’s commercial API surface

Tokonomix is the gateway: one key and one base URL that reach every model in the catalogue, with Council’s multi-model review available as a model id on the same call. It carries and meters the traffic — it does not decide anything itself. ZelixAI buys its models here, including the EU-routed lane, and the components below are what the traffic is made of.

TransportOne OpenAI-compatible base URL in front of the whole catalogue.
ReviewSet the model to tokonomix-consensus and Council answers instead of one model.
MeteringUsage is billed per token to the account the key belongs to.
AI Engineering Stack

Open technologies for reliable AI

No component is dressed up. The badge on each card is its real maturity — that is how the finished parts stay believable.

ProductionActively used and supportedActive DevelopmentActively in developmentPublic SpecificationSpec public, implementations followResearchConcept / researchOpen SourcePublicly available

ANS

Production
Unattended Execution Engineowns execution

A long agent run stops at the first question it cannot answer, and sits there for hours. ANS keeps the run going and parks the question for you.

Run long AI workloads unattended without blocking on human questions.

Availability
Open Source
Repository
github.com/TokonoMix/agents-never-sleep
Docs
README · v1.9.0
Product
agentsneversleep.ai

TodayClone the repository and run it — open source, and the engine behind this site’s own unattended work.

Works independentlygithub.com/TokonoMix/agents-never-sleep

Council

Production
Multi-Model Review Engineowns review

One model can be confidently wrong and nothing in its answer says so. Council asks models from different families the same question separately, then shows where they disagree. That disagreement is the signal.

Independent multi-model review: fewer single-model errors, disagreement surfaced early. It does not guarantee correctness.

Availability
Open Source
Repository
npm: tokonomix-council-mcp
Docs
npm README + skill · MCP registry: ai.tokonomix/council

TodayAdd the MCP server to your agent, or call it over this site’s API with the model id tokonomix-consensus.

Works independentlywww.npmjs.com/package/tokonomix-council-mcp

DCP

Public Specification
Coordination Protocolowns coordination

Every agent describes project state in its own words, so nothing downstream can read it reliably. DCP fixes the vocabulary, not the tool — which is why it is a specification, not a library.

Development Coordination Protocol — a vendor-neutral language for project state, shared by AI agents and humans.

Availability
Public specification — live at devcopro.org
Repository
Not yet public
Docs
devcopro.org
Product
devcopro.org

TodayRead the specification at devcopro.org and build against it — implementations follow the spec, not the other way round.

Works independentlydevcopro.org

AgentsWeaver

Active Development
Distributed Collaboration Layerowns distribution

One machine runs out of capacity before the work does. AgentsWeaver spreads a job across a fleet of specialised agents, keeps them isolated, and settles what each one used.

Distributed collaboration for AI agents: workload distribution, isolation and settlement across a fleet.

Availability
Private Preview
Repository
Not public
Product
agentsweaver.ai

TodayNothing self-serve yet: access runs through a direct relationship while the private preview continues.

Works independentlyagentsweaver.ai

AgentixMesh

Active Development
Agent Infrastructure Layerowns transport

When agents message each other, delivery is the easy part. The hard part is knowing who really sent it, and treating the message as data rather than an order. AgentixMesh handles both.

Secure transport, trust, routing and discovery for distributed AI agents.

Availability
Open Source (repo)
Repository
github.com/TokonoMix/agentixmesh
Product
agentixmesh.ai

TodayThe repository is public; the hosted network is still in development.

Infrastructure layergithub.com/TokonoMix/agentixmesh
Digital Commerce Stack

Commercial platforms built on the stack

beheer-v3 is the commercial layer the applications run on — not an application, and not an AI component.

beheer-v3

Production
Digital Service Commerce Platformowns commerce

Building an AI feature and selling it are different problems. beheer-v3 handles the selling: who subscribed, what it costs, and what they get when they pay.

Subscriptions, billing, resellers, licensing and provisioning. Not AI — it sells AI and digital services.

Availability
Commercial
Repository
Not public

TodayA commercial platform behind the products below, not a self-serve component.

ZelixAI

Production
Enterprise AI Platformowns application

A customer-service AI that buys its models through the gateway and its billing from beheer-v3, instead of rebuilding either.

Enterprise AI for customer service, built on the stack — its models come through the Tokonomix gateway, including the EU-routed lane.

Availability
Commercial
Repository
Not public
Product
zelixai.ai

TodayLive at zelixai.ai — the sister product, and the reference implementation of the stack.

Integrates the Tokonomix gatewayzelixai.ai

SurfOnline

Active Development
Local Digital-Economy Platformowns application

A local marketplace that gets its AI and its billing from the same two stacks as everything else here.

A local digital economy, built on the stack.

Availability
Commercial
Repository
Not public
Product
product page — to confirm

TodayIn development; the product page is not confirmed yet.

How everything fits together

One request, through the whole ecosystem

The same path a real customer question takes. Each step is a component you can open above.

  1. RequestA customer asks a question
  2. ZelixAIthe enterprise AI application receives it
  3. ANSexecutes the work unattended
  4. Councilreviews the decisions
  5. DCPcommunicates project state
  6. AgentixMeshtransports the messages
  7. beheer-v3handles billing and provisioning
  8. Customerreceives the service

Applications like Gallery and ZelixAI consume these capabilities without hard dependencies — composability, not coupling.

Use it today

Five things you can paste right now

Everything on this list works today, with the account you already have. Nothing here is a waitlist.

Give Claude the council — no install

https://mcp.tokonomix.ai/mcp

Add it in claude.ai under Settings → Connectors as a custom connector. You log in with OAuth; no client id, no secret, no key in your config.

Full connector guide

Run the council next to your agent

npx tokonomix-council-mcp

The local transport, driven by an API key. It also carries what the remote one cannot: image input and the full council mode.

Package on npm

Call it from code you already wrote

https://tokonomix.ai/api/v1

An OpenAI-compatible base URL: change two lines in an existing client. Send model: "tokonomix-consensus" and several models answer instead of one.

Endpoints and agent setup

Read the catalogue as data

GET /api/v1/models

Every model the gateway reaches, with its prices and whether it can be routed inside the EU. Public JSON, no key needed.

Open the JSON

Run agents that do not stall

git clone https://github.com/TokonoMix/agents-never-sleep

The unattended-execution engine, open source. It parks the questions a run cannot answer alone instead of waiting on them.

ANS on GitHub
Roadmap

A controlled architectural evolution

Not a timeline — a direction. Each stage builds on the last, and no stage has a date it could miss.

  1. TodayProduction execution (ANS) and review (Council), open and in use.
  2. Open protocolsDCP is live as a public specification (devcopro.org); the agent transport follows.
  3. Distributed executionAgentsWeaver outsources, settles and isolates work across a fleet.
  4. Commerce platformsbeheer-v3 commercialises the capabilities for real products.
  5. Future ecosystemA composable, vendor-neutral platform others build on.
Ecosystem principles

The architecture rules we hold

These are constraints we accepted, not adjectives. Each one costs something somewhere else in the system.

Single Responsibility

Each layer owns exactly one job.

Vendor Neutrality

No lock-in to one model or provider.

Modular Architecture

Components compose, they don't entangle.

Swappable Components

Replace a layer without breaking its consumers.

Open Standards

Protocols over proprietary glue.

Independent Products

Each product stands on its own.

Independent Repositories

Separate repos, separate lifecycles.

API-first

Every capability is reachable programmatically.

AI as infrastructure, not the product

AI is a layer you build on, not the thing you sell.

Composable Architecture

Every component works standalone, but delivers more value combined with the rest of the ecosystem. This is the philosophy behind TokonoMix.

Architecture before implementation

The structure and responsibilities are designed first; the code fills in a shape that already makes sense.

Component overview

Every component, one table

The same facts as the cards, in the form you would put in a document.

Show the full table (9 components)
ComponentOwnsPurposeStatusAvailabilityRepository / Product
ANSExecutionUnattended executionProductionOpen Sourcegithub.com/TokonoMix/agents-never-sleep
CouncilReviewMulti-model review & consensusProductionOpen Sourcenpm: tokonomix-council-mcp
DCPCoordinationSemantic project coordinationPublic SpecificationPublic specification — live at devcopro.orgdevcopro.org
AgentsWeaverDistributionDistributed collaborationActive DevelopmentPrivate Previewagentsweaver.ai
AgentixMeshTransportTransport, trust, routingActive DevelopmentOpen Source (repo)github.com/TokonoMix/agentixmesh
beheer-v3CommerceDigital service commerceProductionCommercialNot public
ZelixAIApplicationEnterprise AI platformProductionCommercialzelixai.ai
GalleryApplicationCommerce media platformActive DevelopmentCommercialproduct page — to confirm
SurfOnlineApplicationLocal digital-economy platformActive DevelopmentCommercialproduct page — to confirm
Questions

What this page usually raises

Do I have to adopt all of it?
No, and that is the design. Every component works on its own — you can run ANS without Council, or call Council without ever touching the rest. Composing them adds value; nothing requires it.
Which parts are actually open source?
ANS and AgentixMesh have public repositories, Council is published on npm as tokonomix-council-mcp (its source lives in a private monorepo), and DCP is a public specification at devcopro.org. The commercial platforms — beheer-v3, ZelixAI, Gallery, SurfOnline — are not open source, and no page here claims otherwise.
How does tokonomix.ai relate to the TokonoMix ecosystem?
This site is the ecosystem’s commercial API surface: the gateway that carries calls to every model in the catalogue and meters them, with Council available on the same call as a model id. The ecosystem is the architecture behind it.
What does any of this cost?
The open components cost nothing to run — they run on your own infrastructure. Calls through the gateway are billed per token to the account your key belongs to, at the per-model prices on the pricing page. There is no surcharge for using the MCP connector.
Why does the page show components that are not finished?
Because hiding them would make the finished parts less believable. Every component carries its real readiness, and where a fact is not confirmed yet the page says so instead of guessing.
Does consensus mean the answer is correct?
No. Several independent models reduce single-model error and surface disagreement — that disagreement marks where one model alone would have sounded just as confident and been wrong. Models can still be uniformly wrong, and nothing here guarantees correctness.
Build on it

Public artefacts & APIs

TokonoMix — one architecture, built from independent components. Product URLs and maturity for Gallery and SurfOnline are marked to confirm rather than guessed.