The economic operation layer for autonomous agents

The Open System for
the Agentic Internet.

TOS turns Internet actions into typed, authorized, metered, receipted, and settleable operations that independent agents and providers can safely execute across organizational boundaries.

Read the whitepaper Inspect the code
Transport-neutralBind HTTP, MCP, A2A, OpenAPI, or RLDP
Authority-boundIdentity, capability, budget, expiry
Resource-boundedQuotes, limits, metering, refunds
Outcome-accountableReceipts, evidence, disputes, settlement

One economic contract across the agent ecosystem

TOS is designed to wrap existing agent and Internet interfaces, not replace them. A client can discover through ARD, bind to MCP, A2A, OpenAPI, HTTPS, or RLDP, and carry the same capability, budget, metering, receipt, and settlement semantics across providers. The clients shown below illustrate the ecosystem TOS is designed to interoperate with; they do not imply integrations or endorsements.

  • Claude
  • Codex
  • Cursor
  • Devin
  • Gemini CLI
  • GenSpark
  • GitHub Copilot
  • Hermes Agent
  • LobsterAI
  • Manus
  • Marvis
  • OpenClaw
  • OpenFox
  • Pi Agent
  • Windsurf
  • WorkBuddy

What TOS must prove before it claims a network effect

Adoption is measured through unrelated repeat payers, conforming providers, portable receipts, organic settled value, and low-cost completion, not simulated dashboards, address counts, or reward-funded traffic.

P5 Organic settled value
P1 2+ Conforming providers
P4 OPEN Portable receipts
Quote-to-paid completionP2measure
Repeat payer retentionP3cohorts
OFFAIPoW before product-market fit
Unrelated payer domainsP5organic
Third-party integrationsP8open
P4
Receipt verification
OPENThird-party surfaces
  • Agent SDK
  • Provider SDK
  • Verifier
First-party reference appP0dogfood
Provider retentionP3no rewards
Settlement costP6

Measured as a share of completed operation value

These are public release gates, not live network metrics. Results remain unpublished until independently verifiable telemetry exists.

Open definitions. Competing providers. Portable receipts.

The first commercial wedge is paid model and tool invocation. Once independent providers conform to the same operation revision, agents can compare quotes, carry bounded authority, verify receipts, and switch providers without rebuilding the economic integration each time.

TOS Agentic operation layer
DefinitionsVersioned operations
ProvidersCompeting implementations
ReceiptsPortable outcomes
DemandRepeat agent buyers

Beachhead

Paid model and tool calls

Start with one measurable transaction: quote, authorize, invoke, receipt, and settle across unrelated providers.

Expansion

Broad, narrow, then broad again

After the compute profile works, communication, storage, events, commerce, and physical edge can reuse the same authority and receipt model.

Defensibility

Embedding and verified history compound

The moat is third-party SDK adoption, conformance, portable receipts, and measured reliability, not forced lock-in or token issuance.

The next Internet primitive

Web2 gave machines APIs.
TOS gives agents economic opcodes.

Typed actions. Bounded authority. Metered resources. Verifiable receipts. Settleable outcomes.

Read the whitepaper Inspect the code