Tenzro Network · Preview
Settlement for AI work.
An open settlement and coordination layer for AI work, underneath the operators, model providers and agent platforms that already serve it. Each call is routed, authorised, settled and returned with a receipt anyone can check.
- Signed by hardware
- Every answer a registered machine serves from a catalogued model carries a receipt signed under that machine's hardware key.
- Billed by what was sent
- A call is billed from the provider's signed receipt, capped by what was actually sent and received.
- Revoked everywhere at once
- Revoke an agent and nothing signed for it after the revocation is paid, on any operator's channel.
- Open source
- The node, the SDKs and the protocol are open source under Apache 2.0.
Demand
Agents now pay for work.
Software that acts on someone’s behalf now calls models, buys data and hires other software, often many times a second.
Invoices and card payments were built for people buying from companies. They do not say which agent spent, under whose authority, or what the money bought.
- Participants
- Humans
- Agents
- Machines
- Services
- Rails
- Settlement
- Consensus
- Hardware
- TPM 2.0
- Secure Enclave
- Passkeys
- TEEs
- GPUs
Operators and demand
Operators have the machines. Tenzro brings the work.
Data centres, GPU clouds and independent operators already run the hardware AI needs. Tenzro sends them agent and app demand through one API, routes each call by price, latency and reputation, and pays per call at the operator's own rate card, without a contract between every buyer and every operator.
- Routed
To the provider that fits
Calls go to the provider that fits by price, latency and reputation, and move on within seconds if one fails. - Settled
Paid per call
Each call is paid against a receipt the serving machine signs, with billing capped by what was actually sent and received. When a job spans several operators, each is paid its share. - Recorded
One record per payment
Every payment is one record that binds the request, the quote and the price. Refunds and revenue splits settle on the same record.
Accountability
Every agent answers to someone.
An agent on Tenzro holds no key of its own. It acts under terms granted by the person or company responsible for it, and every payment it makes is recorded against those terms.
Terms, not keys
An agent's authority is its terms: what it may pay, in which assets, up to which per-payment and daily limits, granted by a person's passkey or a machine's hardware key.Channels for frequent calls
High-frequency work runs over payment channels backed by escrow, and counts against the same limits.Revocation that holds
Revoke an agent and nothing signed for it after the revocation is paid, on any operator's channel.Evidence you can hand over
An agent's payments export as an evidence pack that anyone you give it to can verify offline.
Providers
Every class of machine has work to do.
One codebase builds a release for each class of hardware, and each machine takes only the roles it can serve. Each role it takes is bonded from the same account.
- Edge
Small and embedded devices
Single-board computers, Jetson-class modules, mini PCs, NAS boxes and gateways. They hold identity, make payments, run agents and storage, and pass inference on to GPU providers. - Provider
CPU servers and workstations
Every role a CPU can serve, including the models that fit it. - Provider
From one GPU to a data centre
Inference, compute rental and confidential computing, with models too large for one machine served in pipeline shards across your own machines, and mixture-of-experts models across holders on the network. - Validator
Servers with a TPM
Order transactions and certify checkpoints with keys held in the hardware, against a bonded stake.
Who builds on Tenzro
One network for everyone who buys AI work.
Developers, researchers, organisations and autonomous software use the same endpoint, the same payment rails and the same receipts.
Developers building AI applications
Leading open-source models behind OpenAI-compatible APIs, priced by an open market instead of one provider's rate card.Learn moreAgents and machines
Hardware-rooted identities, spending limits and metered payments, so software can buy inference and compute on its own.Learn morePrivate and sensitive workloads
Run inference and data processing inside attested hardware, with evidence you can check yourself.Learn moreRegulated industries
Choose where models, data and compute live, and see who served every request, under which policy, certified by whom.Learn moreModel builders and researchers
Rent capacity, and train across distributed clusters with applications built on the network.Learn moreEvery industry that buys AI
One endpoint for inference and compute from independent providers, without a contract with each of them.Learn more
Under the hood
Built to be trusted by machines.
The network is in preview, and governance decides the steps to testnet and mainnet. Everything below ships from the start.
- 01Tenzro DAG Consensus (TDC)Our post-quantum consensus protocol. Every validator proposes in parallel each round, so no single leader limits the network.
- 02Keys that live in hardwareEvery key is rooted in a TPM, a Secure Enclave or a passkey. No private key is ever stored in the clear, and there are no seed phrases.
- 03Trust and provenanceCertification and ratings for models and operators, issued by anyone. You choose which issuers you trust and check the rest yourself.
- 04The Machine EconomyA compute price index signed by validators from what their routers observe, SLA-attested rentals and metered, per-use settlement, paid in TNZO or stablecoins.
- 05Inference for any modelPrefix and state reuse for every architecture class, behind OpenAI-compatible APIs for chat, responses, embeddings and audio, with image and video generation on the same node's API.
- 06Closed by defaultOpen, owner and admin methods are separate. Anything that moves money or changes state needs a signature from the account that pays.
Open source
Open source under Apache 2.0.
The protocol and network primitives are open source under Apache 2.0, and the Tenzro Foundation stewards the protocol and its repositories. Partners help operators of every background get started.
Get involved
Join Tenzro Network.
Anyone can operate, build on or use the network. It is permissionless and open source. Tell us how you want to take part and we will help you get started.
- OperatorRun a nodePut an edge device, a GPU, a homelab or a data centre on the network and get paid for the work it serves.Apply
- DeveloperBuild on the networkOpen models, OpenAI-compatible APIs, identity and payments in one stack, priced by an open market.Apply
- ResearcherTrain and experimentRent compute for experiments, and run training across distributed clusters with applications built on the network.Apply
- PartnerPartner with TenzroIntegration, technical support and go-to-market partners who bring operators and builders onto the network.Apply