Quick Start
- Open elisiaagent.xyz/app.
- Connect an EVM wallet with MetaMask, Rabby, Trust or another injected wallet, or paste a public address for read-only analysis.
- Install the Chrome extension from the zip, open its popup and press
Pair device. - Approve the pairing link inside the app. The extension receives a device token; it never receives a seed phrase or private key.
- Open a supported terminal page. Elisia observes visible-tab interaction events and sends them to the AWARE engine.
Wallet Login
Wallet login uses a signed message flow. The backend creates a nonce, the wallet signs it, and the server opens a secure session after verifying the signature.
Extension Pairing
- Download elisia-agent-0.1.0-chrome.zip.
- Unzip it locally.
- Open
chrome://extensions, enable Developer mode and chooseLoad unpacked. - Select the unzipped extension folder.
- Open the Elisia popup and pair the device through the app.
The extension is scoped to supported trading sites and elisiaagent.xyz. It records structured UI events only while the tab is visible.
AWARE Score
AWARE is a 0-100 behavioral pressure score. It is not a buy or sell signal. It reads pace, repetition and reaction patterns so the trader can notice pressure before acting into it.
| Signal | Meaning | Weight |
|---|---|---|
| ACT | Activity load across recent actions. | 0.25 |
| WKF | Workflow repetition and looped behavior. | 0.15 |
| VEL | Action-to-execution velocity. | 0.15 |
| RTP | Roundtrip loops and re-entry patterns. | 0.15 |
| OUT | Loss response and size changes after adverse outcomes. | 0.15 |
| BAS | Drift away from the trader's own baseline. | 0.15 |
Wallet Analysis
Elisia can read public Robinhood Chain activity through configured providers and explorer data. The app shows summaries, realized behavior and current profile state. Exact results depend on provider availability and the address history.
AI Agent
The assistant answers questions about the trader's own activity and AWARE state. It can explain the drivers behind a score, summarize recent sessions and point out behavioral patterns. It should not be treated as financial advice.
API Overview
| Route | Purpose |
|---|---|
/api/health | Production health check. |
/api/v1/auth/* | Wallet nonce, verification and session management. |
/api/v1/me | Current authenticated account. |
/api/v1/pairing/* | Extension pairing request, approval, status and enrollment. |
/api/v1/analysis/* | Wallet analysis and provider-backed chain reads. |
/api/v1/assistant/* | AI assistant conversations and messages. |
Privacy and Safety
- No seed phrases, private keys or transaction signing.
- Device pairing requires explicit approval from an authenticated app session.
- Private API routes require a wallet session or device token.
- Extension observations are limited to supported host permissions.
- Assistant output is informational and not financial advice.
Production Status
Landing, app routes, API health, secure wallet login, extension pairing, device enrollment and AI assistant messaging have been smoke-tested on production.
Chrome Web Store publishing, live terminal-specific DOM adapters and optional provider keys should be verified before a public launch push.
Last updated: August 28, 2026