Trust / access boundaries
No key in the prompt. No trade in the toolset.
Treat every AI request as untrusted. The first release deliberately stops at market research while execution permissions remain outside the connection.
Boundary test / try to break it
See exactly what the AI can and cannot know.
Run the risk tool and watch it refuse to invent a safety score. Paste a bad address and watch validation stop it before any request.
Pick a test above or press Run live. The request goes out from your browser right now.
Public preview of the same data your AI receives through the authenticated connection. Observations, not advice.
Current controls
These are product boundaries, not an audit certificate or a guarantee against attacks.
An AI client requests access through account sign-in and a consent screen. No pasted wallet secret is an authentication method.
The connection exposes public market observations only. It cannot create transactions, sign or execute trades.
Connected external wallets keep their keys and sign themselves. Managed Dev, sniper and account wallet keys are AES-256-GCM encrypted at rest. The AI connection cannot access either kind of key.
Price and liquidity data are third-party observations, not guarantees. A sent transaction is never presented as a confirmed trade.
Any future trading access requires a separate reviewed authorization and risk policy. Read access today does not grant future trade access.