DOCUMENTATION / 01

GLIDE / THE GUIDE

From your first address
to your next Callout.

Understand orders, tune your settings and see what's available in the private alpha.

Getting started

Glide runs in a private Telegram chat. The current alpha only permits its owner to trade with the connected wallet. Public access is not enabled.

  1. Send /settings or /start.
  2. Choose your amount, currency and Callout mode.
  3. Review slippage, priority and confirmation.
  4. Enable the modes, then send a CA: a Solana token address.

New modes are disabled initially to preserve the existing bot workflow. Purchase confirmation is on by default.

/cancel cancels your current input. Stop pauses new purchases and copying; it cannot cancel a transaction already submitted.

Normal, Fast and Turbo

ModeMessageFlow
NormalYour own textSend an address, then reply with your message
FastA short AI messageSend an address
Turbo๐Ÿš€Send an address; no generation

With confirmation enabled, review the order and tap to buy. With it disabled, your text in Normal mode or the address in Fast and Turbo starts the operation.

Fast requires a Gemini API key. Missing credentials or failed generation stop the order before a purchase. The model receives the token address and generates a neutral message; it does not research the project or evaluate returns.

Turbo skips text entry and generation. It still waits for purchase confirmation on-chain and Pump publishing eligibility. It does not change slippage or priority.

Buy settings

Amount and currency

SOL sets the swap budget in SOL. USDC sets a USDC budget for a supported direct pair. USD pays a dollar-denominated budget in SOL using a checked exchange rate. Automatic USDC-to-SOL routing is not available.

Each new configured order buys the selected amount, even if you already hold the token. An order saves a snapshot of its settings; later menu changes do not alter it.

Slippage

The permitted decrease in tokens received from the quote. A quote of 1,000 tokens at 5% slippage permits a minimum of 950. Slippage does not increase your swap budget. The bot does not automatically raise it after a failure.

Priority

An extra transaction fee expressed in SOL. Glide converts it to a compute-unit price. Rounding may make the actual amount slightly smaller. Base network fees and account creation are separate. A higher priority fee does not guarantee execution. Protected relays and separate tips are not integrated yet.

Glide fees

Planned public pricing is 0.5% on top of the successful purchase budget. A 150 USDC purchase adds 0.75 USDC: 150.75 USDC total, plus network costs in SOL.

The fee is not active in the current alpha until the treasury is configured. Its status appears in the settings and confirmation card.

  • The purchase and service fee transfer share one atomic transaction.
  • If the transaction fails, the service fee transfer also rolls back. A network fee may still be charged.
  • SOL purchases pay the service fee in SOL; USDC purchases pay it in USDC.
  • Fees round down to the currency's smallest unit, with no hidden minimum.
  • Trading protocol fees are reflected in the quote and are not Glide revenue.

Pump publishing is a separate action. If the purchase succeeds but publishing is delayed, resuming does not require another purchase or service fee.

Wallets and Pump access

These are separate connections: a wallet authorizes trades, while a Pump session authorizes publishing from a profile.

Three public onboarding options are planned: create a dedicated trading wallet, import through a secure form, or connect an external wallet. Public onboarding is not available yet.

A created or imported wallet can allow trades without an external signature for each order, but the service then has authority over its funds. An external wallet requires transaction approval unless the user explicitly grants separate automation permissions.

Do not send a seed phrase, private key or Pump cookie through Telegram. Wallet onboarding and backups need a separate secure interface.

A new trading wallet does not automatically link to an existing Pump profile. Before buying, the bot checks the active account's wallet and Callout availability.

Copying Callouts

The alpha follows one profile, which can be replaced from the copying menu. Existing history is skipped when connecting; new Callouts arrive with approval and skip buttons.

Each approved signal triggers a new $1 purchase paid in SOL and copies the author's text. Media is not copied. Tokens on other networks appear without a buy button. Main-menu purchase settings do not change this copy amount.

Repeated taps on one signal do not create a second purchase. If your own Callout already exists, another publication is not created.

/copies shows pending signals. /copy_off pauses copying. /copy_on enables it. Multiple profiles and per-profile budgets are planned.

Account statistics

Send a Pump profile address or link from the statistics menu. The bot shows the number of Callouts in the retrieved page, unique tokens and the date range. It indicates when earlier pages exist.

This is a limited sample, not lifetime performance. Returns, median outcomes, post-publication highs and drawdowns need historical price data and are not available yet. Missing data is not reported as zero.

A signal's performance is not the author's actual PnL: publishing does not prove their entry price, position size or exit time.

Errors and recovery

An operation moves through created โ†’ prepared โ†’ submitted โ†’ purchase confirmed โ†’ publishing โ†’ complete. The transaction signature is saved before submission.

  • Failure before submission: the purchase was not sent. Check your settings or balance.
  • Unknown confirmation: avoid creating another purchase. Use the exact /resume command supplied by the bot.
  • Purchased but not published: the bot rechecks the position and publishing state.
  • Lost publishing response: the profile is checked first to avoid a duplicate.
  • Expired Pump session: renew the connection before continuing.

Shutting down the computer stops the local bot. This documentation and landing page run on Vercel; continuous public bot hosting is not deployed yet.

Data and access

The private alpha stores settings and its operation journal locally. Settings are separated by Telegram ID, but multi-user trading is not enabled: only the owner may use the current wallet.

Public launch requires isolated wallets and Pump sessions, ownership checks for every order, managed secret storage, account recovery and independent security review.

The AI receives no Telegram ID, balance, keys or Pump session. Published messages and transactions are visible on their respective platforms. Deleting Glide data cannot erase blockchain history.

Disconnecting an imported key does not revoke copies of that key. Moving funds to a new wallet ends reliance on the old key.

Development status

ALPHA Settings menu, Normal and Turbo modes, confirmation, fixed budgets, an operation journal, one copied profile and basic account statistics.

SETUP REQUIRED Gemini credentials for Fast mode and a treasury address for service fees. The corresponding actions remain inactive until configured.

BEFORE PUBLIC LAUNCH User wallet and Pump onboarding, multiple copied profiles, historical prices, continuous bot hosting and security review.

These docs describe the current product boundaries. The landing page does not collect keys, offer public registration or promise investment returns.