Agents
Hand a mandate to an agent.
Watch every joule and every dollar.
Provision a sub-account for an AI agent under your account. Give it a bounded, revocable mandate — a spend cap, a period, a category, the rails it may use. The agent transacts; ComplianceOS screens; Veritas books the tax; Insights meters the energy. Every action is on the same ledger as the assets behind it, and you see the agent's energy bill next to its commerce.
Agent sub-accounts
Provision a sub-account for an agent. The agent never touches your full balance — it works inside the sub-account you gave it. Create it, suspend it, or close it from the app, the same way you'd freeze a card.
Mandates
A signed authority with edges: a spend cap, a period, a category or merchant scope, the rails it may use, an expiry. One mandate model that's compatible at the edges with the agent-payment protocols the industry is converging on — without locking you to any of them.
Agent identity (KYA)
A verifiable credential, issued by ComplianceOS, that proves this agent acts for your account within these mandates. And because the credential is a smart byte , it works anywhere on the substrate — not just here.
The kill switch
Revoke a mandate and the agent is cut off the moment the revocation commits. Every agent action is on the same tamper-evident audit log as everything else in the account — you see what the agent did, with the joules it spent next to the dollars.
The mandate, the credential, and the spend so far are one record. Revoke it and the next action fails — there's no second system to call.
Identity is a credential, not a config flag
ComplianceOS issues a verifiable credential that says: this key acts for this account, within these mandates. It carries the check that produced it.
The credential is a smart byte
Content-addressed, portable, neutral — the agent's passport works anywhere on the substrate, so the agent isn't captive to one venue or one protocol.
Every action on the same audit log
The agent's purchases, transfers, and receipts land on the same tamper-evident ledger as the rest of the account — nothing the agent does is off to the side.
Joules next to dollars
Insights meters the energy the agent's decision consumed; it sits on the same receipt as what the agent spent. One line for the commerce, one for the compute.
Multi-rail agent payments
A single mandate can route this purchase over a card, that one over the stablecoin settlement rail , another over ACH — all on one statement, one audit log. Protocol-agnostic at the edges; substrate-native at the core.
Agent receiving / merchant
Agents that do work and need to get paid. Accept agent payments, proceeds land in the account, Veritas income-classifies them. The full agent-economy loop — agents spending and agents earning — on one rail.
Powered by the platform
ComplianceOS underwrites and screens · TradingOS executes and surveils · LegalOS resolves jurisdiction for cross-border agent payments · Veritas books the tax · Insights meters the energy. Five pillars on one record.
Runs on EOC
The agent's compute runs on EOC , the energy-optimized substrate, so the joules on the statement are honest by construction — the agent's energy bill and its commerce, denominated the same way.
The agent's energy bill and its commerce, on one statement.
Agent commerce isn't only agents spending — it's agents earning, agents settling, agents getting metered. When the agent runs on an energy-honest compute substrate, transacts through a regulated multi-rail account, and every action is a content-addressed receipt carrying both its joules and its dollars, the human behind the agent sees the whole picture: what the agent bought, what it earned, what it cost to think. And because the receipt rides on a neutral substrate, the agent isn't captive — it can transact with anyone who speaks the same format. That's the closed loop: a model on EOC, an account on Settlement, a receipt that's a smart byte.