1. What Auto does
Auto is an optional execution mode for ODEI wallet software. Where it is available, you can establish a rule that permits ODEI’s delegated signing infrastructure to sign and submit eligible operations without asking you to approve or sign each operation again. The rule determines which proposals may proceed; it does not assess whether a trade is suitable or profitable for you.
These terms supplement the Terms of Service and Wallet & Connectors terms. They describe software and hosted execution services. The word “non-custodial” does not remove the delegated authority described here or determine the legal classification of every service.
2. Your rule and acceptance
Activation requires presentation of the applicable terms, rule and permission for your acceptance and authorization. Accepting service terms and signing a wallet permission are distinct steps. Publishing this notice does not establish that you accepted it, install a permission or retrospectively change an existing agreement.
Review the networks, assets, amounts, selected proposal sources, price conditions, duration and charges before authorizing the rule. The rule becomes active only after the required on-chain installation is confirmed and ODEI verifies the installed permission. A saved draft, connected AI application or account sign-in is insufficient. Keep the rule and operation records available for later review.
3. Who can sign
Your root wallet key remains under your control through the normal Manual key flow. Auto adds a separate session signing key controlled through ODEI’s hosted, hardware-backed signing infrastructure. ODEI can use that key within the installed permission; the connected application does not receive it or your root key.
This is real delegated signing authority, not merely a draft-storage service. ODEI’s signing infrastructure, access controls and software are therefore part of the system you rely on. The installed permission constrains that key; keeping assets at your wallet address does not mean ODEI has no authority to act on them.
4. Supported operations
The current Auto implementation supports eligible Uniswap v3 swaps on Base through the supported single-pool, exact-input route and reviewed pools. It can include the token approval needed for that swap. The review identifies the actual supported assets and route. Availability depends on your wallet, permissions, current service controls and jurisdiction; this notice is not a promise of access.
The permission binds swap proceeds to your own wallet. It does not give this Auto mode general authority for arbitrary transfers, bridges, lending, staking, unrelated contract calls or every Manual recipe. Additional networks or operations require their own supported permission and disclosure; they are not included merely because the wallet displays them.
5. How a proposal becomes an operation
A selected application or agent can submit a proposal. ODEI prepares and evaluates it against the active rule and applicable checks. A matching proposal may initiate the separate Auto process: ODEI records the applicable budget reservation, signs through its delegated signer and submits the operation. You may be offline when this happens.
A proposal can therefore have an automatic financial consequence even though the Connector itself cannot sign or broadcast. A failed check may leave the proposal for your review or pause Auto. Status distinguishes preparation, approval, submission and settlement; an approval or submission acknowledgement is not a confirmed trade.
6. Wallet limits and ODEI checks
The review separates restrictions encoded in the on-chain permission from additional controls enforced by ODEI. The installed permission constrains the signer, permitted route and assets, recipient, spending amounts, applicable daily and gas limits, price conditions and expiration. Read the actual permission rather than assuming every displayed control is enforced by the blockchain.
Selected proposal sources, weekly budgets, aggregate service limits and some counting or operating checks are enforced by ODEI’s servers. Network-specific limits are not automatically one shared cross-network allowance. Price checks and simulations reduce particular risks but do not guarantee market value, liquidity or a profitable result. A trade can satisfy every rule and still lose value.
7. Changes, reductions and expiration
Raising authority or renewing an expired permission requires the applicable new owner signature. A rule’s displayed duration and on-chain expiration matter independently of whether the app remains open. Expiration prevents new valid use of that permission; it does not undo transactions already submitted or their continuing protocol effects.
Lowering a limit can take effect immediately in ODEI’s server checks without a new signature. The previously signed, wider on-chain permission remains until it is replaced, expires or is revoked. A lower displayed server limit must not be mistaken for a completed on-chain reduction. Review the remaining permission if you need the blockchain restriction itself changed.
8. Pause, stop and revoke
Pause stops new approvals through ODEI once the pause request is successfully applied. It does not remove the session key’s on-chain permission. An offline or failed request is not a confirmed pause. Check the resulting state.
“Stop and revoke” first pauses Auto and prepares the owner-signed operation needed to remove its permission on each applicable network. A submitted removal request is not confirmed revocation: until confirmation, the installed permission may remain usable within its limits and expiration. If preparation, signing or confirmation is incomplete, follow the remaining steps; a partially completed stop is not complete revocation. An earlier installation may also still be pending and require reconciliation.
Already signed or submitted operations may still settle. Revoking Auto’s permission does not automatically revoke earlier token allowances or reverse protocol positions; review those separately. Disconnecting an application, signing out or locking your browser is not a substitute for pause or revocation.
9. Pending operations and records
Timeouts, provider failures and chain reorganizations can leave an operation uncertain. ODEI may continue observing and reconciling an existing operation after Auto is paused or revoked. This does not by itself authorize a new trade. Do not assume an absent confirmation means no funds moved, or repeat the same economic action through another interface without checking.
Review the rule’s history, approval explanation, transaction identifier and confirmed outcome. Reservations or pending records can affect remaining budgets while the result is unresolved. Cancellation and revocation cannot guarantee recall of an operation already in flight.
10. Charges and risk
Swaps, ancillary approvals, permission installation or removal, and failed attempts may incur network or protocol costs. Applicable ODEI charges must be disclosed under the purchase or service terms; network estimates do not represent all possible charges. See Billing, Cancellation & Refunds.
Auto adds risks from repeated execution, compromised proposal sources, delegated signing infrastructure and reliance on server controls. Choose limits you can tolerate and inspect activity. Read the Risk Disclosure; automation and restrictive permissions do not eliminate loss or replace appropriate professional advice.
11. Data, support and rights
ODEI processes rules, permissions, decisions, spending reservations, signed payloads and execution records to provide Auto. The Privacy Notice explains processing and your rights. Stopping Auto does not automatically erase records needed for pending operations, security, claims or legal obligations.
Report problems or complaints to ai@odei.ai, identifying the rule, operation, relevant dates and remedy requested. Never send private keys or recovery material. These terms do not waive ODEI’s duties, mandatory consumer protections or remedies. Blockchain irreversibility does not extinguish a valid contractual or statutory claim.