One account · every client
Your shared workspace.
Teams, watchlists, developer access and data tools stay attached to your GEX Levels account across the website and Terminal.
Your account at a glance
One desk, across your tools.
Create a team, share a watchlist and choose whether your discussion is public, team-only or personal. The same discussions are readable in the Terminal. The security centre and AI execution remain unavailable while being prepared.
Your account data is requested on demand. The page does not poll in the background.
Not available · currently being set up
AI credits
This feature is visible for transparency but cannot be used or purchased yet. When released, requests will use customer-funded prepaid credits only.
Shared on site and Terminal
Teams & watchlists
One conversation · website and Terminal
Community desk
Choose who can read a post before publishing. Public means signed-in members; team means active teammates; private means only you. Team visibility does not make team messages public.
Posts load when you open this section or press Refresh. There is no background polling.
Open this section to load messages.
Not available · currently in development
Security centre
This Workspace section is fully gated while its controls and account-session views are being completed. No security data is loaded here.
Scoped and revocable
Developer API
Raw values are shown once. The database keeps only a one-way hash. Revoke a token you no longer use.
Source-backed
Data lineage
| Data path | Domain | Priority | Mode | Lineage |
|---|
The primary options path is preferred. A separate continuity path can take over when the primary source is unavailable. Timestamps and source health remain attached to every served payload.
Low cost by design
Sync & reliability
- Conditional ETag refreshes avoid redownloading unchanged account data.
- Versioned watchlists reject conflicting edits instead of overwriting them.
- A per-account snapshot is kept only in this browser tab for offline, read-only fallback.
- Only explicit user refreshes or detected change cursors trigger account sync.