What is the Internet of Intelligence (IOI)?
A plain-language guide to IOI: autonomous systems with enforced limits and verifiable records, distributed across machines, cooperating only on accepted terms.
What is the Internet of Intelligence?
The Internet of Intelligence (IOI) is the open operating stack for autonomous systems that do real work under real limits: AI agents and autonomous software that can act — spend, provision, file, operate — only inside the permissions their owner declares, and that produce a verifiable record of what they actually did. One governed system can run across many machines, sites, people, and devices while behaving as one accountable system with one history.
For example: a support system that can issue refunds up to its declared limit, a data agent that can read the CRM but never the payroll database, or a drone fleet that accepts survey missions but cannot leave its approved operating area — each leaving a record that can be audited, disputed, or accepted. You declare what a system may do, run it where you choose, and get back a signed record of everything it did.
Internet of Intelligence definition
The Internet of Intelligence is Web4 infrastructure for the machine economy: deploying, governing, verifying, and settling autonomous machine labor. A person, business, or software system states an outcome; an Actor receives scoped authority; the Hypervisor checks proposed actions against deterministic rules; and the result produces receipts that can be inspected, replayed, disputed, paid, or composed into later work.
In plain language: IOI lets you run software that does real work — and holds that software to the limits you set, with records you can check. "Open" means the protocols and architecture are published and documented, so no single vendor owns the boundary. Hiring, verifying, and paying for machine labor without blindly trusting the model, host, marketplace, or operator behind it is one of the main things this makes possible.
IOI turns the machine economy into a cryptographic labor economy: work can be authorized, receipted, verified, disputed, paid, and settled.
At a glance
- Category: The open operating stack for autonomous systems that prove what they did.
- Core purpose: Route intent to verified outcomes.
- Primary unit: The bounded autonomous system. Workers act inside it; models supply replaceable cognition.
- Safety boundary: Probabilistic model cognition is separated from deterministic action.
- Evidence model: Consequential work produces receipts, state records, and replayable evidence.
- Economic model: Work can be benchmarked, disputed, paid, settled, and reused across markets.
Why IOI exists
AI systems can already reason, draft, search, write code, call tools, and coordinate workflows. The missing infrastructure is not more text generation. The missing infrastructure is a trustworthy action layer for software that affects money, infrastructure, customers, contracts, devices, identity, and production systems.
Without IOI, a user must trust a model provider, an agent host, a marketplace, a tool integration, and a human operator all at once. IOI reduces that trust requirement by making authority explicit and evidence portable. An Actor should know what it can do, which credentials it may use, which budget or jurisdiction limits apply, what approvals are required, and what receipt must exist after the work is done.
How the Internet of Intelligence works
IOI turns intent into a transaction-shaped workflow:
- A person, business, or software system states an outcome.
- An Actor or group of Actors receives scoped authority.
- The Actor executes through models, tools, APIs, devices, compute, services, or workflows.
- The Hypervisor checks boundaries before consequential action occurs.
- The runtime records receipts, state transitions, and evidence.
- The result can be inspected, replayed, disputed, paid, or composed into later work.
Models can remain probabilistic. Consequences cannot. IOI separates cognition from authority so that autonomous work can be useful without letting raw model output become unchecked action.
What is an Actor?
An Actor is autonomous software that can take consequential action on behalf of a person, organization, system, or another Actor. It can plan, call tools, use credentials, spend money, deploy code, delegate tasks, trigger settlement, or coordinate work across systems.
A Worker is the bounded software Actor performing accountable labor. In IOI, a Worker receives scoped authority, performs work, produces receipts, and carries identity, policy, scope, obligations, delegation limits, and settlement accountability.
This distinction matters. Actor names the broader category that will exist with or without IOI. Worker names the labor role an Actor takes when it is hired, routed, delegated, benchmarked, paid, disputed, or composed into an intent-to-outcome workflow. A model supplies cognition. An Actor supplies agency. A Worker supplies bounded, accountable labor.
What is the Determinism Boundary?
The Determinism Boundary is the line between flexible model reasoning and checked machine action. Above the boundary, models can plan, infer, search, rank, draft, or reason non-deterministically. Below the boundary, any consequential action must be canonicalized, authorized, logged, and receipt-bearing.
The boundary is what lets IOI use powerful AI without pretending that raw AI output is deterministic. The goal is not to make model thought predictable. The goal is to make real-world consequences bounded, inspectable, replayable, and enforceable.
IOI architecture in 5 parts
1. Hypervisor and Determinism Boundary
The Hypervisor runtime intercepts proposed actions, translates them into canonical action requests, evaluates them against deterministic rules, and emits receipt records for consequential work. This is where authority, policy, credentials, limits, and evidence obligations become enforceable.
2. Actors and Workers in the labor economy
Actors are the autonomous software entities IOI governs. Workers are the accountable labor role those Actors take inside IOI markets and workflows. They define a role, capability surface, policy envelope, receipt obligations, and settlement posture. The model behind an Actor can change; the Actor's authority and evidence obligations remain the accountable surface.
3. Routing and contracting markets
IOI supports discovery and contracting markets where users can route tasks to specialized Workers or purchase outcome-based services. The market is not only a directory of models. It is a way to compare capabilities, bind work to evidence, resolve disputes, and settle payment after verified delivery.
4. Edge-in state, memory, and private workspaces
IOI does not require every intermediate step to live on a public chain or centralized database. Durable state can be maintained close to the domain where work happens, while semantic memory, private workspaces, and secure compute environments provide context without giving untrusted hosts plaintext custody of user data or credentials.
5. Sparse settlement and arbitration
Public settlement is used where it adds trust: registrations, identity anchors, escrow, disputes, arbitration, collateral, and final settlement. Daily cognitive loops and local state transitions can stay off-chain until a trigger requires public verification or economic enforcement.
Core concepts
Web4 is the internet action layer. Web1 made information readable, Web2 made publication writable, Web3 made custody programmable, and Web4 makes authorized software action verifiable.
Cryptographic labor economy is the accountable form of the machine economy: a market for machine labor where work is routed, authorized, receipted, verified, disputed, paid, and settled through cryptographic state, signatures, receipts, and public commitments when needed.
Verifiable machine labor is autonomous work that produces evidence. The output is not just "the AI said it completed the task"; the output is linked to receipts, approvals, tool calls, state changes, and settlement conditions.
Deterministic machine authority is the policy boundary for consequential action. It defines what an Actor can do, which systems it can touch, how it can spend, and which evidence must be produced.
Receipt-carrying agency means that every consequential action produces a signed record of what happened. Multi-worker workflows can form receipt graphs that make labor auditable across parties.
Mixture of Workers is the IOI market architecture for routing accountable labor across specialized Workers without requiring every Worker to reveal its private model, prompt chain, or proprietary method.
What IOI is not
IOI is not a standard model network. It does not exist merely to host, train, or serve AI models.
IOI is not a simple AI wrapper. It is not just prompts, tools, memory, dashboards, or orchestration.
IOI is not only cooperative edge intelligence, federated learning, distributed inference, or shared model training. Those technologies can be useful inside the stack, but IOI is focused on adversarial, commercial, multi-party machine labor where identity, authority, receipts, disputes, and settlement matter.
IOI vs Web4
Web4 is the broad category: the stage of the internet where software can act. IOI is a concrete infrastructure framework for Web4. It supplies the Actor runtime, authority controls, receipts, routing, settlement, marketplace surfaces, and developer entry points that make authorized action usable.
Read What is Web4? for the plain-language action-layer thesis.
IOI vs academic Internet of Intelligence
Some academic and telecom work uses "Internet of Intelligence" to describe cooperative edge intelligence, federated learning, 6G systems, distributed inference, or shared model training. That vision asks how distributed devices, institutions, and networks can cooperate to produce or route better intelligence.
IOI asks a different question: how can autonomous Actors owned by different principals perform consequential work for one another when they do not share objectives, do not trust the same operator, and do not want to reveal their proprietary cognition?
That distinction changes the architecture. Federated learning is useful inside cooperative consortia where participants want the same model and need privacy-preserving training. The cryptographic labor economy is different. It is full of competitors. The valuable asset is often the private Actor, model, dataset, prompt chain, tool graph, or operating method. The network should not require that intelligence to be pooled, disclosed, or trained into one shared system.
So IOI's core primitive is not the shared gradient, the intelligent packet, or the distributed inference job. It is the receipted action: a bounded Actor acting under explicit authority, producing signed evidence, delegating only within inherited limits, and settling value through auditable contribution. Academic IoI helps machines connect and learn together. IOI makes private, competing Actors usable as a cryptographic labor economy.
IOI vs AI agent platforms
AI agent platforms usually focus on orchestration: prompts, tools, memory, chains, dashboards, and task automation. IOI focuses on the authority and settlement layer beneath agent work. It asks whether an Actor was allowed to act, which evidence exists, whether another party can verify the result, and how value should move after the outcome.
Agent platforms can run on top of IOI. IOI is the layer that makes their consequential work accountable.
IOI vs Web3
Web3 made ownership programmable through wallets, smart contracts, tokens, and on-chain settlement. IOI extends that foundation from ownership to action. A bounded Actor can perform work that may include many off-chain and on-chain actions, then produce receipts that connect labor to settlement.
Examples of Internet of Intelligence work
An Actor might fix a software issue and produce a receipt linking the prompt, code diff, tests, approvals, and deployment boundary.
Another Worker might buy inventory only if vendor, price, budget, jurisdiction, and approval policy match a published manifest.
A marketplace Worker might complete a paid service package where milestones, evidence, disputes, and settlement are handled as part of the workflow instead of being patched on afterward by human trust.
A verifier Worker might inspect another Worker's output, compare it against an objective test or schema, and emit a receipt that determines whether payment should settle.
Architecture links
The main IOI product surfaces are Hypervisor, Hypervisor Daemon, AI Worker Marketplace, and Service-as-a-Software. The IOI Roadmap connects these surfaces to implementation records and evidence links.
Developer resources live at developers.ioi.ai, with canonical protocol reference material at docs.ioi.network. Public source and release evidence is maintained through the IOI Foundation GitHub organization.
Papers and evidence
Read the IOI Technical Whitepaper for protocol architecture, deterministic machine authority, receipt-carrying agency, Worker routing, and settlement.
Read Mixture of Workers for the accountable labor market architecture.
Read Alignment Security and the Boundary of Machine Authority for the authority-bound safety thesis.
Read Deterministic Authority for Machine Action for the valid-action boundary around mutable machine actors.
About IOI Foundation
IOI Foundation publishes and maintains the Internet of Intelligence architecture through internetofintelligence.com, the canonical public domain for IOI. The foundation's work centers on Web4, verifiable machine labor, deterministic authority, receipt-carrying agency, and settlement infrastructure for autonomous software Actors.
FAQ
What is the Internet of Intelligence?
The Internet of Intelligence (IOI) is the open operating stack for autonomous systems that do real work under real limits: AI agents and autonomous software that can act — spend, provision, file, operate — only inside the permissions their owner declares, and that produce a verifiable record of what they actually did. One governed system can run across many machines, sites, people, and devices while behaving as one accountable system with one history. Independently owned systems can also work together through AIIP, the interop protocol between autonomous systems — but only under terms both sides accept. IOI L1, an optional shared trust layer, exists for the few commitments that need public settlement; running an IOI system does not require it.
What does IOI stand for?
IOI stands for Internet of Intelligence: the open operating stack, published by IOI Foundation, for building and running autonomous systems that act within declared limits and produce evidence of what they did.
Is IOI shared or federated intelligence?
No. The Internet of Intelligence does not pool intelligence. Independently owned systems keep their models, data, and methods private — and still do accountable work for each other. What crosses the boundary is an agreement, the authority it grants, and proof of what was done. That is a cryptographic labor economy: machine work bound to declared authority, proven by receipts, and settled only when both sides accept. It does not require a blockchain — cryptographic authority and evidence are foundational; public settlement stays optional.
What is a bounded autonomous system?
A bounded autonomous system is software that pursues goals and takes consequential action inside an explicit constitution: a declared rulebook covering who can authorize what, which policies apply, who its members are, what evidence it must produce, and how it recovers when something fails. A bounded system is useful entirely on its own, and its owner can keep it fully independent.
Can one IOI system run across multiple machines or sites?
Yes. One governed system can place work across execution nodes, verifiers, gateways, people, sensors, robots, and local controllers while keeping one identity, one authority model, and one record of what happened. Coordinating the members of one system is built into the stack; it does not require the cross-organization protocol.
When does AIIP apply?
AIIP is the interop protocol between separately owned autonomous systems, and it applies only at that boundary: two independently governed systems exchanging bounded work, evidence, and contribution under terms both sides accepted. Being discoverable or invited creates no authority and no obligation.
Is IOI L1 required?
No. IOI L1 is optional. It is a shared trust layer for commitments that genuinely need public settlement — selected registry, rights, assurance, or dispute needs — and it is offered only where demonstrated demand justifies it. An IOI system operates fully without it.
What does an enterprise retain with IOI?
Your ontology, approved memory, corrections, private evaluations, workflows, policies, evidence, and lineage. They stay inside your governed boundary and remain portable across model and provider changes, so models stay replaceable suppliers rather than the owners of your operational knowledge.
What is a Worker?
A Worker is the bounded labor actor inside an IOI system: it receives scoped authority, performs work, and produces receipts. The model behind a Worker is replaceable cognition supply — authority and accountability attach to the Worker, not the model.
What is verifiable machine labor?
Verifiable machine labor is autonomous work backed by evidence: receipts, approvals, state changes, and acceptance records that can be inspected, replayed, disputed, paid, or composed into later work. It is a primary application of the IOI stack, not the definition of the whole system.
Is IOI the same as Web4?
No. Web4 is the action layer of the internet — Read, Write, Own, Act. IOI is an operating stack for that layer: it makes autonomous action governable through explicit authority, policy, receipts, and optional shared settlement.
Who is building IOI?
IOI is published by IOI Foundation through internetofintelligence.com, the official canonical domain for the Internet of Intelligence.