Base agents
Agents submit EconomicIntent through Sovereign instead of receiving unchecked wallet authority.
Sovereign Wallet OS · Base-first
Constitutional wallets
for Base agents.
Sovereign Wallet OS is a Base-first framework that lets autonomous agents request x402 payments and other economic actions through policy-bound wallets instead of receiving raw wallet authority.
Built for Base agents, USDC service payments, merchant trust, data provenance, auditability, and governed trading workflows.
Typed EconomicIntent Decision Packets Mock x402 Provenance Paper Trading Live Trading Blocked
Base-native agentic commerce
Built for Base-native
agentic commerce.
Base gives agents wallets, x402 payments, stablecoin settlement, and onchain execution. Sovereign adds the missing governance layer: constitutions, budget controls, merchant trust, decision packets, provenance, and audit trails.
x402 lets an agent pay an API.
Sovereign decides whether the agent may pay.
Base payment lane
Akasha / Agent
↓
EconomicIntent → Sovereign Runtime
↓
Procurement Wallet + Constitution
↓
x402 Payment → Base Sepolia
↓
USDC Settlement
↓
DataArtifact → Provenance + Accounting
x402 payments
Procurement wallets govern paid API and data access through x402-style payment flows.
USDC on Base
Agent spend is modeled around USDC-denominated service payments on Base.
Builder attribution
Future Base transactions can carry Builder Codes for app, wallet, and agent attribution.
The problem
Agents can call tools. But under what
constitution may they spend?
Most agent systems focus on what an agent can do. Sovereign focuses on what an agent is allowed to do economically.
01
Raw wallet authority is too broad
A model-selected tool call should never become unchecked spending power.
02
Payments need policy
Economic actions should be evaluated against wallet-specific constitutions, budgets, counterparties, and risk constraints.
03
Actions need memory
Every purchase, artifact, and downstream decision should be traceable, auditable, and accounting-ready.
Wallet profiles
Three wallets. Three constitutions.
One runtime.
Each wallet profile carries its own authority surface, budget limits, permitted merchants, and risk tolerances.
Core framework
A runtime for governed economic intent.
Every economic action flows through a typed intent, a wallet constitution, and a scoped decision packet before execution touches anything real.
Wallet Profiles
Procurement, Trading, and Treasury wallets each carry their own authority surface and compiled constitution.
EconomicIntent
Agents submit typed requests instead of receiving direct signing access. No raw call surface.
Constitution Runtime
Active wallet policy evaluates budgets, merchants, risk, and execution context before any action.
Decision Packets
Approved actions receive scoped, expiring, replay-protected authorization. Nothing executes without one.
Merchant Trust
Routes are fingerprinted. Payee drift can deny or quarantine a merchant before any payment lands.
Provenance
Paid data artifacts are linked to the wallet, merchant, decision, and every downstream trade plan.
Accounting
Settled actions generate double-entry journal entries and exportable CSV records automatically.
Governed Trading
Paper execution is risk-checked and bounded. Live trading is denied or escalated by default.
Budget Engine
Reservations, commits, releases, and reversals keep spending bounded per wallet at runtime.
Execution model
From intent to execution,
every step is bounded.
The runtime evaluates typed intent before any economic action executes. No raw wallet access. No unchecked spending.
01
Submit Intent
Agent submits typed EconomicIntent
02
Load Constitution
Runtime loads wallet constitution
03
Policy Checks
Budget and merchant checks run
04
Issue Packet
DecisionPacket is created and signed
05
Execute
Adapter runs the approved action
06
Record
Audit, accounting, provenance persisted
Working flows
Current working use cases.
These flows are built, tested, and runnable in the developer demo today.
01
Paid Data Procurement
Agents buy approved data through a procurement wallet instead of making direct purchases.
✓ Working · mock x402 flow
02
Payee Drift Defense
If a merchant route changes unexpectedly, the runtime blocks or quarantines it before any payment.
✓ Working · route fingerprinting
03
Data Provenance
Each paid artifact is linked to the merchant, route, wallet, decision, and downstream usage.
✓ Working · artifact chain
04
Governed Paper Trading
Trading wallets approve bounded paper execution from risk-checked trade plans only.
✓ Working · paper broker
05
Blocked Live Trading
Live trading remains denied by default. Selecting a tool never automatically executes it.
✓ Verified · default denied
Build status
Built as a working
developer MVP.
All core flows are implemented, tested, and runnable. The demo proves the framework rather than just describing it.
Run the test suite
pnpm typecheck
pnpm test
pnpm test:integration
pnpm test:postgresSnapshot mode for local demos · Postgres for durable validation
First client
Akasha
Akasha is being integrated as the first agent client through the SDK-only path. She can request paid data, inspect provenance, create trade plans, run risk checks, and request paper execution.
She cannot directly sign transactions, trade live, alter wallet policy, or bypass constitutional controls.
Akasha ↓ paid data request ↓ Sovereign procurement wallet ↓ data artifact ↓ trade plan ↓ Sovereign trading wallet ↓ paper execution ↓ provenance + accounting
Live demo
Watch Akasha use Sovereign.
Akasha is the first live agent client. Watch her submit economic intent, receive a decision packet, execute a paper trade, and get blocked from live trading — all in real time.
Open Akasha Control Room → akasha_agent · live
✓ intent.created · mcp.paid_data_request
✓ budget.reserved · $12.00 of $500.00
✓ merchant.checked · fingerprint match
✓ decision.approved · dp_eth_001
✓ artifact.created · sha256:a3f2…
✓ paper.order.created · filled $2,847.30
✗ live.trading.denied · blocked by constitution
Developer
Run the framework
locally.
Seed the demo, request paid data, create a paper trade, inspect provenance, export accounting records, and verify blocked live execution.
Quick start
pnpm install
pnpm dev:api
pnpm demo:paid-data
pnpm demo:paper-trade
pnpm demo:provenanceAgents should have constitutions,
not raw wallets.
— SOVEREIGN WALLET OS CORE PRINCIPLE