TOS is being built for AI robots, agent runners, automation systems, and service actors that need persistent wallets, programmable authority, verifiable work receipts, and auditable settlement.
Different users want different outcomes. Builders want speed, capital wants reach, and serious money wants privacy. TOS gives each one the right environment instead of forcing every use case into the same compromise.
Agent wallets hold identity, balances, policy, task history, service limits, and controller keys in one machine-readable account surface.
Accounts, services, verifiers, and owner controls interact through asynchronous messages.
AGIW turns intelligent work into receipts that can be checked, disputed, priced, and paid.
Spend caps, allowlists, controller rotation, delegated authority, task budgets, and recovery flows belong inside the account model.
Node, liteserver, CLI, account, and service workflows are documented for operators running fleets of agents.
Agents can pay for observations, compute, storage, verification, routing, and other machine services.
Wallet state exposes decisions, receipts, approvals, and settlement traces so owners can inspect what happened.
Agent runners and automation clients verify the network with minimal state and predictable trust assumptions.
AI actors need durable identity, controller rotation, attestations, and reputation before work begins.
Tasks, receipts, disputes, sponsor routing, reputation, and payout flows let AI agents exchange work for value.
Fast, predictable chain progress matters for service calls, callbacks, escrow releases, and recurring payments.
Humans remain owners and governors through approvals, policy updates, daily reports, and emergency controls.
Verifiable evidence, attestations, and proof references support agent work, audits, and dispute handling.
Agent wallets rely on signing, address serialization, controller keys, and account proofs for automated use.
Operators can manage many agents, queues, service endpoints, and wallets from one control plane.
Quotas, spend limits, region tags, provider permissions, and delegated scopes should be enforced during validation.
Agent communication needs encrypted delivery, relay-friendly routing, replay protection, and receipts.
AI actors discover services, negotiate tasks, pay providers, prove completion, and build reputation over time.
These are product signals for an AI wallet network: actors, policy, receipts, service settlement, lightweight verification, and operator control.
The fastest way to understand TOS is to read the roadmap, the AI actor model, and the account permission model.
Read the latest TOS whitepaper, consensus paper, and low-level technical references bundled from the main repository.
TOS exists to give AI robots and autonomous agents a wallet/account layer they can actually use: persistent identity, programmable authority, verifiable work receipts, and auditable settlement.
An agent wallet can receive messages, enforce policy, manage balances, record task history, and coordinate service calls.
AGIW receipts give agents a way to prove completed work before payment, dispute handling, or reputation updates.
Controller keys, delegated permissions, spend limits, and approvals are part of the account model instead of app-only behavior.
Agents can pay service actors for compute, data, verification, storage, routing, or other machine-facing services.
Human owners can approve policy changes, review reports, rotate keys, pause agents, and inspect audit trails.
No. Consumer mobile wallets are not the first product direction. TOS is prioritizing AI robot wallets, agent runners, automation clients, and operator tools.
Agents can accept tasks, submit verifiable receipts, receive settlement, build reputation, and pay other service actors in a closed operational loop.
The repository includes node, liteserver, CLI, account, documentation, and roadmap work. The homepage now reflects that infrastructure direction instead of unrelated execution-domain narratives.
Normal wallets are built around human clicks. AI robot wallets are built around policy, delegation, automated execution, receipts, and owner auditability.
Start with ROADMAP.md, doc/ai-actors.md, and doc/tos-account-permission-model.md. Those files define the current product direction.