A founding reference ecosystem for an open Agentic Internet

The Open System for
the Agentic Internet.

TOS develops public protocol proposals, reference implementations, and infrastructure for humans and Agents to express revocable Intents, form exact Agreements, act with bounded authority, prove outcomes, and choose a settlement path. TOS is one open part of the Agentic Internet, not its owner or mandatory marketplace.

Read the Constitution Inspect the protocol FreeCity
Public proposalSpecifications, versions, vectors, licensing gates
Authority-boundedPurpose, capability, budget, expiry, revocation
Settlement-pluralDirect, authenticated, escrow, external, refuse
Outcome-accountableStable identity, evidence, Receipts, recourse

Shared semantics. Independent implementations.

TOS is designed to complement existing agent and Internet interfaces, not replace them. Any party should be able to implement compatible Intent, Agreement, authority, evidence, and settlement semantics in its own repository and runtime, subject to the published profile and conformance gates. Using OpenFox, a TOS SDK, or a TOS-operated service must never be a condition of protocol compatibility. The clients below illustrate possible interoperability only; they do not imply completed 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.

Public specifications. Competing implementations. Portable evidence.

The first external acceptance target is machine-checkable software work. Once independent buyers, providers, verifiers, and implementations share the same Agreement and evidence semantics, Agents can compare offers, carry bounded authority, verify outcomes, and change providers without making one Gateway or marketplace the source of truth.

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

Beachhead

Machine-checkable software work

Start with one independently verifiable lifecycle: Intent, offer, Agreement, bounded execution, evidence, Receipt, and settlement across unrelated roles.

Expansion

Generic core, narrow profiles

Intent content can describe new industries without changing the core protocol. Add a profile only when authority, ordering, privacy, admission, or side effects genuinely differ.

Defensibility

Conformance and verified history compound

Durable value comes from independent implementation, portable evidence, repeat demand, and measured reliability, not forced lock-in, one mandatory marketplace, or token issuance.

Constitutional direction

Local judgment. Minimum authority. Verifiable commitments.

TOS proposes a polycentric design for the Agentic Internet: decisions stay with the lowest competent and accountable layer; consensus is reserved for facts that need one authoritative history; participants retain meaningful choice and exit; and experiments never promote themselves into greater power.

Agentic Internet ConstitutionFounding proposal · published, reviewed internally, not yet ratified
↗
Normative service specificationSchemas, authority rules, invariants, profiles, vectors, and acceptance gates
↗
OpenFox reference AgentLocal interpretation and bounded execution; model output is never protocol authority
↗
Proposal is not adoption The Constitution becomes governing only through an explicit ratification record naming the authority, exact commit, date, and adoption scope. Its publication does not bind independent projects.

One open part of a larger Internet

Agents discover locally.
Protocols make commitments portable.

Revocable Intents. Exact Agreements. Bounded authority. Verifiable evidence. Plural settlement.

Read the Constitution Inspect the protocol Enter FreeCity