Settings
Your account, alerts and access
One identity across the bot and the Terminal. Manage how alerts reach you and what unlocks at your tier.
Telegram
Connect Telegram to link your Terminal
Telegram is the alert and command layer. Terminal is the research surface. Linking syncs alerts, watchlists and access state.
- Receive Smart Money alerts straight in Telegram.
- One account links bot, Terminal and access state.
- No custody, no private keys, no seed phrases.
Account
Sign in to link your Terminal session
Telegram login links your Terminal session to your bot account.
- Telegram login links your Terminal session to your bot account.
- Wallet access checks land separately.
- Smart Money never holds your funds, signs transactions, or executes trades.
Current access
Free · Not connected
Your live access state across Telegram and wallet sources.
- Telegram
- Not linked
- Wallet
- Not connected
- Tier
- Free
Telegram login links your Terminal session to your bot account.
Wallet connect proves ownership for access checks. Smart Money never stores private keys or seed phrases.
Entitlement evaluation is not wired. Live checks land in a later workstream.
Account links
Linked sources
Telegram is wired up. Wallet linking and $SMART balance proofs land in later workstreams.
Telegram
Linked at /login. Sessions are stored in a signed HTTP-only cookie. Bot alerts route to this same identity.
Wallet
Wallet linking is non-custodial. Live connect lands in a later workstream — no adapter is loaded in this build.
$SMART balance
Will be read from your linked wallet on Solana once balance proofs are wired. Holder thresholds determine your tier.
Notifications
Notification preferences
UI-only toggles. Notification preferences are not yet wired.
Telegram alerts
Smart Action Cards and signal alerts routed via @SmartMoneyTerminalBot.
Terminal alerts
Inline Terminal notifications when alerts trigger while you're signed in.
Email alerts
Reserved for future delivery. Email routing is not yet wired.
Bot API status
Where Terminal data will come from
The Bot is the future intelligence engine. The Terminal is the research UI. Every contract endpoint below is mock-backed today.
Mode
Disabled
Base URL
not set
API key
not set
Contracted endpoints
- GETToken scanscan.tokenComposite token snapshot — scores, evidence and sources.
- GETWallet profileprofile.walletWallet performance + risk profile across windows.
- GETSmart wallet leaderboardleaderboard.smart_walletsCurated smart-wallet leaderboard with rank deltas.
- GETCluster feedfeed.clustersObserved wallet clusters acting on the same subject.
- GETRisk reportreport.riskDetailed risk evidence bundle for a single subject.
- GETAlert listalerts.listAlerts queued or recently delivered for the current user.
- GETWatchlist statewatchlist.stateCurrent watchlist with bot indexing-coverage flags.
- GETProvider statusstatus.providersLive status of every upstream provider the engine consumes.
- GETScore registryregistry.scoresVersioned score registry the bot is currently emitting.
- GETEvidence bundlebundle.evidenceAggregated evidence for a subject across all risk types.
BOT_API_KEY is read server-side only. The client never sees it.
Provider policies
What we may use, and how
Conservative draft stance for every external data source. Not a legal review.
Show all 11 policies
dexscreener
DexScreener
Allowed use
- · Public token metadata read (price, liquidity, volume, FDV)
- · Pair-level snapshots for cached display
Prohibited
- · Resale of bulk pair feeds
- · Public mirror of DexScreener-hosted screenshots or charts
Cache stance: limited
Rate limits: Public endpoints throttle aggressively. Cache reads and back-off on 429.
Compliance: DexScreener terms require review before commercial Terminal launch. Cached values are surfaced with attribution.
Last reviewed · 2026-05-07
helius
Helius
Allowed use
- · Solana RPC + enhanced transaction parsing
- · Account state lookups for wallet enrichment
Prohibited
- · Bulk archival mirror of Helius-enriched payloads
- · Sharing raw API key with downstream consumers
Cache stance: permitted
Rate limits: Plan-bound RPM and credit budget. Reuse a single intelligence object across users to amortise cost.
Compliance: API key must remain server-side. Confirm commercial tier covers Terminal load before launch.
Last reviewed · 2026-05-07
alchemy
Alchemy
Allowed use
- · EVM RPC for Ethereum/Base/Arbitrum/Polygon enrichment
- · Token metadata + transaction receipts for wallet inspector
Prohibited
- · Public mirror of raw RPC responses
- · Sharing API key client-side
Cache stance: permitted
Rate limits: CU-budgeted. Treat compute units like a paid resource — coalesce reads.
Compliance: Confirm commercial Growth/Scale plan covers projected Terminal traffic.
Last reviewed · 2026-05-07
birdeye
Birdeye
Allowed use
- · Solana token holder distribution + holder count
- · Per-mint top holder snapshots for the holders panel
Prohibited
- · Public mirror of Birdeye-hosted holder feeds
- · Sharing API key client-side
Cache stance: limited
Rate limits: Per-key RPM budget. Cache per-mint holder responses; tighten limit when degraded.
Compliance: API key must remain server-side. Confirm commercial tier covers Terminal load before launch.
Last reviewed · 2026-05-07
jupiter
Jupiter
Allowed use
- · Solana token list + metadata read
- · Reference quotes for display (never executed)
Prohibited
- · Order placement or execution from the Terminal
- · Custodial routing
Cache stance: permitted
Rate limits: Public endpoints throttle. Cache token list reads.
Compliance: Quotes are reference only. Terminal never signs or executes — confirms non-custodial rule.
Last reviewed · 2026-05-07
geckoterminal
GeckoTerminal
Allowed use
- · Cross-chain pool metadata as a sanity-check fallback
- · Volume/liquidity snapshots for cached display
Prohibited
- · Bulk export of GeckoTerminal pool feeds
Cache stance: limited
Rate limits: Public API has tight rate limits. Use as fallback, not primary.
Compliance: CoinGecko/GeckoTerminal terms must be reviewed before commercial use.
Last reviewed · 2026-05-07
solscan
Solscan
Allowed use
- · Account + token metadata read for the inspector
- · Per-tx context lookups
Prohibited
- · Bulk mirroring of Solscan datasets
Cache stance: limited
Rate limits: Public endpoints throttle. Solscan Pro may be required at scale.
Compliance: Solscan terms reserve commercial use. Confirm Pro plan terms before launch.
Last reviewed · 2026-05-07
etherscan
Etherscan family
Allowed use
- · Address + tx context for inspector
- · Contract verification source via key
Prohibited
- · Mirror of Etherscan-hosted data without attribution
Cache stance: limited
Rate limits: Per-key RPS budget. Family includes Etherscan/Basescan/Arbiscan/PolygonScan.
Compliance: Terms-of-service explicitly call out caching and attribution. Review per-network terms before commercial use.
Last reviewed · 2026-05-07
website_meta
Project website metadata
Allowed use
- · Read of public OG/meta tags from the project's own domain
- · Display of project-published links for context
Prohibited
- · Scraping behind logins or paywalls
- · Re-publishing entire site content
Cache stance: encouraged
Rate limits: One read per refresh cycle per project. Always cache aggressively.
Compliance: Robots.txt / TOS of the target site take precedence. Do not bypass auth walls.
Last reviewed · 2026-05-07
social_meta
Public social metadata
Allowed use
- · Public account existence checks via official APIs only
- · Cached display of project-published social links
Prohibited
- · Ingesting follower lists for resale
- · Bypassing platform rate limits or login walls
Cache stance: limited
Rate limits: Each platform has its own paid tier. Defer to official APIs only.
Compliance: Each platform's developer terms apply individually. Confirm commercial tier of every social API consumed.
Last reviewed · 2026-05-07
ai_summary
AI summarisation
Allowed use
- · Summarising cached evidence into a one-line rationale
- · Synthesising signal+wallet context for the inspector
Prohibited
- · Producing trade or allocation recommendations
- · Generating verdicts unsupported by deterministic evidence
- · Hallucinating addresses, transaction hashes or balances
Cache stance: encouraged
Rate limits: Per-tier daily quota. Cache outputs aggressively to amortise cost across users.
Compliance: AI must summarise deterministic evidence only. Disclose AI involvement to the user.
Last reviewed · 2026-05-07
Safety
Research and analytics only.
Research and analytics only. Smart Money never holds your funds, signs transactions, or executes trades. Users always sign in their own wallet.
Research and analytics only. Smart Money never holds your funds, signs transactions, or executes trades. Users always sign in their own wallet.