1. Hosted scope
This service-level notice applies to ODEI-operated hosted control and public surfaces, including my.odei.ai, network.odei.ai, api.odei.ai and app.odei.ai, documentation delivery, account access and hosted launch, session, resume and intake-status functions. It also includes the ODEI-operated components of Auto: rule management, permission-state checks, execution processing, the server signing service, submission and status reporting. A separate written commercial agreement may define a narrower or different service commitment.
The hosted availability target does not cover your local runtime, device, browser state, independently operated wallet software, model providers or connected external systems. ODEI-operated wallet interfaces and Auto components remain within the hosted scope described above. Hosted availability does not guarantee that a transaction is accepted, included, finalized, filled, bridged or settled, or that a third-party service delivers a result.
2. Availability target
Our public target for hosted availability is 99.5% monthly uptime, excluding scheduled maintenance, force majeure and the exclusions below. This is a service target, not an unconditional uptime guarantee or a representation of measured historical performance.
This target is not a per-operation completion rate or an additional Auto execution guarantee. Availability of the website does not establish availability of every signing, submission or external network dependency. Auto has no separately promised execution latency, fill rate, price or investment return under this public notice.
3. Incidents and maintenance
Incident intake is asynchronous and prioritized by severity. We prioritize issues that materially affect hosted access, availability or integrity. Planned maintenance, emergency security work and rollbacks may be necessary to protect the service. This public notice does not promise a fixed support response or restoration time.
Auto execution may be paused during an incident or when a required check cannot be completed. A paused or unavailable service must not be treated as evidence that the wallet's on-chain permission has been revoked. If you want to remove that authority, complete the applicable revocation and check its network confirmation. Already-sent operations may still execute while ODEI is unavailable; observations and status updates can arrive later.
4. Performance and data freshness
Response time, graph freshness, quotes, market views and blockchain observations can vary by route, dependency and load. A displayed pending, submitted or observed status is not a promise of final execution. Independent networks and protocols determine their own inclusion, finality and settlement conditions.
An Auto rule can decline a proposal, wait for required information or stop when a permission, price check, budget, simulation or network condition does not allow execution. A rule match is not a promise that the operation will succeed. The service may need to reconcile uncertain or reorganized network outcomes before reporting a final result. Review operation history before deciding whether to submit another operation.
5. Exclusions
- Failures in local software, local files, browsers, devices or user connectivity.
- Outages or restrictions affecting model providers, blockchain networks, protocols, RPC providers, indexers, explorers, wallet software or upstream APIs.
- User misconfiguration, revoked credentials, incompatible extensions or abusive traffic.
- Scheduled maintenance, emergency security mitigations, legal restrictions or force majeure.
These exclusions define the availability target. They do not exclude liability or statutory remedies that applicable law does not permit ODEI to exclude.
6. Credits and commercial commitments
Public and free usage tiers do not include automatic service credits. A credit schedule, guaranteed response time or custom uptime commitment requires a written commercial agreement. This does not limit a refund, conformity remedy or other right that applies by law.
7. Contact
The operator is identified in the Terms of Service. Report service-impacting issues or ask about a commercial commitment at ai@odei.ai. Include the affected service, time and a description of the issue, without passwords or recovery material.
For an Auto incident, include the affected network, rule or operation reference and the status shown, where available. Do not send your owner private key, recovery phrase, wallet password or signing-service credentials. The Auto notice, Availability notice and Billing notice explain execution authority, access conditions and applicable charges.