Please is being released in deliberate stages. This page separates the current service from the intended production experience.
Available today
Not available in the public product today
- Operator, tenant, or agent accounts
- Durable policies, budgets, approvals, or audit history
- Connected or embedded wallets
- Live portfolio aggregation
- Transaction approval, signing, submission, or broadcasting
- Policy-authorized, autonomous, or recurring financial actions
- Custody of user funds
A demo approval screen does not approve a blockchain transaction. A simulation result does not mean that an action executed, confirmed, or will succeed later.
Intended control-plane experience
The intended product will give operators one place to manage agent identity, funding sources, policies, budgets, approvals, activity, receipts, exceptions, and emergency controls. Portfolio data remains supporting funding and exposure context.
Before any production payment, wallet, or transaction feature is released, please will publish updated documentation covering authentication, custody, signing, data handling, supported networks, fees, recovery, reconciliation, and incident controls.
Every transaction-capable release must preserve a clear boundary:
- The agent requests an outcome.
- Deterministic policy allows, asks, or denies the exact request.
- A permitted request reserves the applicable budget and authority.
- The planning engine creates and simulates a bounded plan.
- Material or exceptional actions receive independent approval.
- The control plane revalidates, submits through a protected signer, and records settlement, delivery, finality, or reconciliation separately.
How to read these docs
Pages that describe the current public service use terms such as preview, simulate, and read-only. Pages that describe the intended authenticated control plane are labeled planned or intended.
If the interface and documentation ever disagree, stop and contact support before taking action. 