The transaction layer for the machine economy

Intelligence is becoming infrastructure. TOS makes it transactable.

TOS Network is building the open coordination and settlement network for autonomous agents, owner-operated AI services, and site-bound physical intelligence.

Providers keep their hardware, models, data, and operating control. Open ARD discovery makes their services legible to agents. TOS then standardizes authorization, live admission, evidence, and payment across organizational boundaries.

Read the whitepaper Inspect the code
  • Implemented TOS Core
  • Designed Service architecture
  • Planned Edge terminal products
OpenARD-compatible, not a walled cloud
Owner-operatedSupply without platform custody
Policy-boundAuthority before execution
VerifiableReceipts, evidence, settlement

A structural market transition

AI has compute. It has models. It still lacks a neutral economic operating system.

The next AI market is not one application or one cloud. It is a fragmented universe of agents, models, sensors, machines, data, and human expertise. TOS is designed to turn that fragmentation into an open service economy.

01

Demand shift

From users clicking to agents transacting

Autonomous software needs persistent identity, delegated authority, explicit budgets, task state, and machine-verifiable receipts.

02

Supply shift

From centralized clouds to owner-operated intelligence

AI services are spreading across workstations, edge servers, factories, vehicles, robots, cameras, stores, and homes.

03

Value shift

From renting hardware to buying outcomes

The durable market unit is a completed, policy-compliant service action—not an hour of unidentified GPU capacity.

What TOS coordinates

A common transaction grammar for independently owned intelligence.

A client asks for a capability under explicit price, latency, privacy, region, and evidence constraints. A provider decides whether to admit it. TOS binds the request to authority, proof, and settlement.

  1. 01 Discover

    Search ARD catalogs and federated registries for a compatible service.

  2. 02 Authorize

    Bind a quote to permissions, budget, and limits.

  3. 03 Execute

    Run an approved service under local admission policy.

  4. 04 Evidence

    Return signed results, metering, and evidence references.

  5. 05 Settle

    Release, refund, or dispute according to agreed policy.

SO

Service outcomes

Consumers buy a defined capability and result. TOS does not expose raw accelerators, public shells, or arbitrary execution.

OC

Owner control

Providers retain custody of hardware, data, models, availability, pricing, and operational policy.

BA

Bounded authority

Controller keys, spending limits, quotes, deadlines, and revocation constrain what autonomous software may do.

ER

Evidence and receipts

Signed records connect service actions to accounting and settlement without putting private payloads on-chain.

Open discovery, native transaction

ARD lets agents find the world. TOS turns discovery into accountable execution.

TOS is designed for compatibility with the open Agentic Resource Discovery specification and to run an independently deployable ARD Registry. Providers publish once; agents can discover across plural registries; TOS completes the economic and operational loop.

Open ecosystem layer

Agentic Resource Discovery

ARD-compatible
Publish AI catalog /.well-known/ai-catalog.json
Federate ARD Registry POST /search
Discover Agents + apps MCP · A2A · OpenAPI
Discovery handoff Verify before value moves
TOS transaction layer

From a resource claim to a settled service

TOS-native
  1. 01VerifyPublisher, TOS identity, endpoint, and policy
  2. 02Quote + admitCurrent price, capacity, revision, and limits
  3. 03Execute + evidenceBounded local work and signed receipts
  4. 04SettlePayment, refund, or dispute under explicit rules
01

Distribution without lock-in

One open discovery surface can expose TOS services to the wider agentic ecosystem instead of trapping supply in a proprietary marketplace.

02

Plural registries by design

Public, private, regional, and industry-specific registries can compete and federate. No single TOS index is mandatory.

03

A hard trust boundary

ARD discovers; it does not authorize, reserve hardware, move funds, update a fleet, or control a physical device. TOS verifies every consequential handoff.

Read the open ARD specification

One network, two frontiers

Digital AI services and physical edge intelligence.

Coordination, settlement, and trust sit between independently owned supply and global demand.

Swipe to explore the full network map → TOS Network connecting AI services and physical edge intelligence through identity, authorization, execution, receipts, and settlement

The Physical AI wedge

The most valuable edge node is not the biggest. It is the one in the right place.

A terminal beside a camera, robot, vehicle, or production line can execute where remote clouds face latency, bandwidth, privacy, connectivity, or safety constraints.

TOS treats these devices as site-bound service terminals—not miniature GPU clouds. Local real-time work and independent safety controls always outrank external network tasks.

Read the Physical AI architecture
01

Disconnected by design

Approved local workloads continue offline with bounded authority and idempotent reconciliation after reconnect.

02

Real-time work comes first

Safety interlocks, control deadlines, and local perception pre-empt external services and background jobs.

03

Updates fail safely

Signed artifacts, compatibility gates, staged rollout rings, health checks, and known-good rollback protect fleets.

04

Execution stays isolated

No public shell, raw actuator, Docker socket, or unrestricted host access. Every queue and resource has a bound.

Why the network can compound

Each completed service makes the next transaction easier to route and trust.

TOS is designed around cumulative interoperability rather than rewards for idle hardware. More compatible services improve choice. More demand improves provider utilization. More signed receipts create better operational evidence. Shared conformance lowers integration cost across devices, models, sites, and industries.

TOS Open service economy
SupplyOwner-operated services
DemandAgents and applications
EvidenceReceipts and outcomes
StandardsLower integration cost

Capital structure

Asset-light at the application layer

Providers fund and operate the hardware. TOS coordinates market access, commitments, and settlement.

Expansion logic

One base protocol, many verticals

AI opens the network; storage, commerce, tools, and human services can reuse the same trust rails.

Defensibility

Integration depth compounds

Identity, policy, evidence, conformance, and operational history travel across endpoints and hardware generations.

Execution credibility

Built on working infrastructure, with every product boundary made explicit.

The blockchain and networking foundation exists in open source today. The service protocol and terminal product layers are intentionally separated and explicitly identified as the next delivery surface.

Implemented foundation TOS Core
  • Native TVM actor execution and asynchronous value-bearing messages
  • Masterchain, shardchains, validator engine, and full-node stack
  • ADNL, DHT, RLDP, QUIC, TOS Sites, and DNS resolution
  • Wallet, cryptography, JSON-RPC, indexing, and operator tooling
  • Agent Account, Service Actor, Task Escrow, and Dispute foundations
  • Capability Registry and Proof Attestation foundations
Verify in the repository
Planned product layer TOS Network
  • Canonical service descriptors, sessions, quotes, and receipts
  • ARD catalogs, independently deployable Registry, and bounded federation
  • Public .tos registration with verified ARD gateway bindings
  • Edge Core, terminal installers, and runtime adapters
  • Managed AI terminal and Physical AI terminal distributions
  • Home and site relays, low-latency settlement, and stronger evidence
  • Cross-implementation conformance and extended resource-soak testing
Review the implementation plan
Demand
People
Applications
Autonomous agents
Service plane
ARD Registry
Authentication + quotes
Receipts + evidence
Owner-operated supply
Managed AI terminals
Physical AI terminals
Other service profiles
TOS Core
Identity + authority
Escrow + settlement
Network + transport

Validator-led distribution

A bounded genesis. Transparent block creation. No insider allocation.

Nearly all native TOS is designed to be created for produced blocks and distributed through recurring validator elections. The policy targets approximately five billion TOS of gross creation over approximately seven years; neither figure is a hard consensus guarantee.

Gross creation target ≈ 5B TOS

Policy target, not a guaranteed hard cap.

Provisional genesis 101,000 TOS

100,000 bootstrap + two 500-TOS system reserves.

Target duration ≈ 7 years

Actual timing follows finalized block production.

Insider allocation 0 TOS

No team, investor, foundation, ecosystem, or treasury allocation.

How native TOS is created

Blocks fund the elected validator set.

Produced block ConfigParam 14 Elector bonus pool Effective-stake share

No finalized block means no native creation. Outages create no reward debt, catch-up multiplier, or later backfill. Transaction and service fees transfer existing TOS and continue after block creation is stopped.

How genesis is constrained

The bootstrap wallet is temporary.

Four original validators begin with equal consensus weight. Each controlling wallet may receive 20,000 TOS of stake principal plus no more than 100 TOS of measured bootstrap costs. After two overlapping elected sets succeed, the remaining main-wallet balance must be burned and its spendable balance reduced to zero.

How concentration is constrained

Open elections replace administrative allocation.

Equal bootstrap funding, an initial effective-stake factor of one, submitted-stake limits, recurring elections, operator-control disclosures, and public concentration metrics are designed to reduce single-entry dominance. The four-validator set is only a startup minimum; the public participation target is 64 independent operators and the long-term target is at least 75 eligible validators.

How creation ends

Governance tapers and then sets rewards to zero.

Finalized gross creation must be published continuously. A public taper review begins before the projected total reaches 4.95 billion TOS, and governance is expected to set masterchain and basechain creation values to zero near the five-billion policy target. Configuration authority means the target is transparent policy, not an immutable cap.

Distribution controls reduce concentration risk; they cannot guarantee dispersed ownership.

Early rewards necessarily go to the validators then elected, and stake-proportional rewards may compound existing holdings. TOS provides no equity, debt, dividend, redemption, fixed yield, liquidity, or price support. Market value can fall, and participation remains subject to technical, custody, governance, concentration, and regulatory risk.

Read full token economics

Focused delivery

A sequence designed to prove the transaction loop before scaling the market.

No phase introduces bare GPU rental, arbitrary consumer execution, or blockchain control of physical safety systems.

  1. Phase 0

    Base protocol and Edge Core

    ARD compatibility, catalog publishing, Registry search and federation, identity, authentication, quotes, receipts, SDKs, and conformance.

    Next foundation
  2. Phase 1

    Managed inference terminal

    Tier 1 Linux/NVIDIA reference, approved models, bounded scheduling, streaming, metering, receipts, and restart recovery.

    First vertical
  3. Phase 2

    Site-bound Physical AI terminal

    Jetson/ARM reference, offline operation, safe updates, real-time priority, actuator isolation, and fleet management.

    Edge expansion
  4. Phase 3+

    Additional profiles and network services

    Storage, commerce, tools, human services, relays, channels, multi-region routing, replication, and stronger attestation.

    Protocol leverage

Underwrite the work, not the adjectives

Every material claim should lead to code, architecture, or a clearly marked plan.

TOS does not ask serious investors to confuse vision with deployment. Start with the source, inspect the current foundation, then evaluate whether the service and terminal roadmap can turn it into a category-defining network.

01
WhitepaperPositioning, architecture, status, and roadmap
↗ 02
Implementation planRepository boundaries, missing work, and release gates
↗ 03
ARD specificationThe open catalog, Registry, and federation baseline adopted by TOS
↗ 04
Source repositoryConsensus, networking, contracts, tests, and history
↗
05
Disclosure boundary Institutional materials covering legal entity, team, financing, customers, commercial metrics, and independent security audits are not published on this website. The technical materials above do not substitute for those disclosures.

Investment questions

What matters before the narrative becomes consensus.

Is TOS another decentralized GPU marketplace?

No. TOS is designed around policy-bound service outcomes. The provider exposes an approved capability, not a raw accelerator, public shell, or arbitrary execution environment.

Why does Physical AI strengthen the thesis?

Physical AI creates services whose value comes from location, local data, privacy, and real-time execution. Those advantages cannot always be replicated by moving the workload to a remote centralized cloud.

What does ARD compatibility add?

ARD gives TOS services an open publication and search surface through standard catalogs and federated registries. TOS begins where discovery ends: it verifies the TOS binding, obtains a live quote and admission decision, executes under local policy, returns evidence, and settles value.

What exists today?

TOS Core exists in open source: actor execution, consensus, sharding, networking, wallets, query foundations, and service-oriented contracts. The interoperable service protocol, discovery product, and edge terminals remain planned product work.

Where can network effects emerge?

Compatible supply improves discovery and composition; demand improves utilization; signed receipts improve operational evidence; shared standards reduce the cost of adding the next model, device, site, or service profile.

How is native TOS issued and distributed?

The policy targets approximately five billion TOS of gross creation over approximately seven years. Genesis is provisionally limited to 101,000 TOS for validator bootstrap and system-contract reserves; nearly all remaining TOS is created for finalized blocks and distributed through the Elector to active validators. Outages are not backfilled, and governance must taper and stop creation near the published target.

Does the website project token value or protocol revenue?

No. Service transaction volume, validator fees, protocol revenue, and token value accrual are distinct. The project publishes architecture and delivery objectives, not investment-return promises.

The opportunity

The cloud organized computing.
TOS is built to organize independent intelligence.

Open ARD discovery. Bounded authority. Verifiable service actions. Native settlement.

Read the whitepaper Explore TOS Core