Settings

Access, notifications and connected accounts.

Account

Email—
Role—
Last sign-in—

Google sign-in

not configured

Google refuses bare IP addresses as redirect URIs, so this needs a real domain first. Once you have one:

  1. Point an A record at this server's public IP
  2. Set SITE_ADDRESS in .env, restart Caddy (TLS is automatic)
  3. In Google Cloud Console → Credentials → OAuth client (Web)
  4. Authorised redirect URI: https://YOUR-DOMAIN/api/auth/google/callback
  5. Put the client id/secret and TAOSCOPE_PUBLIC_URL in .env, set TAOSCOPE_COOKIE_SECURE=true, restart the backend

Telegram

no bot token

Long-polling, so it needs no domain and no open port. About five minutes:

  1. In Telegram open @BotFather and send /newbot. Pick a name, then a username ending in bot. It replies with a token.
  2. Put it in .env as TAOSCOPE_TELEGRAM_BOT_TOKEN, then docker compose up -d backend
  3. Check curl -s localhost/api/status | grep telegram — it should say online @yourbot
  4. Come back here, click Generate code, and send /link CODE to your bot

Ask the bot

no API key

Lets you ask the bot questions in plain English — it answers from live chain data using read-only tools, never guesses a number.

  1. Put an OpenRouter key in .env as TAOSCOPE_OPENROUTER_API_KEY (or an Anthropic key as TAOSCOPE_ANTHROPIC_API_KEY)
  2. docker compose up -d backend

Roughly $0.03–0.04 per question. Capped at 100 answers per chat per day; spend shows here once it is running.

Wallet

verification coming

You can register an address and get a signing challenge now. Signature verification and any on-chain action land with the trading release — the key will live in a separate signing service, never in this web app.

Active sessions

No other live sessions.