> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flowterminal.com/llms.txt
> Use this file to discover all available pages before exploring further.

# General FAQ

> Practical answers about agents, analytics, alerts, contracts, events, and integrations.

### ⚙️ Agents

<AccordionGroup>
  <Accordion title="Do I need to connect a contract before using agents?">
    No. You can start running agents as soon as your exchange connection is active.\
    Adding a contract is only needed to access on-chain analytics (Holders, Alerts, Sell Pressure).\
    Agents operate directly through your exchange API connection, not through smart contracts.
  </Accordion>

  <Accordion title="How do I launch agent?">
    1. Go to  and add API keys.
    2. Open  and choose a strategy.
    3. Configure spread, depth, order size, and refresh interval — then start the agent.\
       \
       Once launched, the agent immediately begins quoting on the exchange with your selected parameters.
  </Accordion>

  <Accordion title="What’s the difference between Spread and Depth, Support-Level, and Treasury-Building agent?">
    • Spread and Depth: continuously provides buy/sell liquidity to tighten the spread and stabilize the market.\
    • Support-Level: protects key price levels by placing liquidity walls below support zones.\
    • Treasury-Building: accumulates token inventory or builds reserves using algorithmic accumulation logic.
  </Accordion>

  <Accordion title="Can I run multiple agents at once?">
    Yes — you can run several agents at the same time, as long as they operate on different pairs or have non-conflicting logic.\
    For example, you can run one Spread and Depth agent to manage liquidity and another Support-Level agent to defend price levels.\
    Avoid overlapping orders on the same pair to prevent internal collisions.
  </Accordion>

  <Accordion title="How can I see what my agents are doing in real time?">
    Once your agent is launched, the system automatically tracks its Target and Current parameters.\
    You’ll see how the agent performs relative to your defined configuration:\
    • Target Spread / Current Spread\
    • Target Depth / Current Depth\
    • Filled Orders, Executed Volume, Open Orders\
    \
    This allows you to monitor how close your live orderbook state is to the intended setup and adjust parameters if needed.
  </Accordion>

  <Accordion title="Does Flow Terminal take responsibility for trading losses?">
    No. Flow Terminal provides automation and analytics tools, but you are fully responsible for how agents are configured and what funds are used.\
    Always define a clear risk allocation for each agent — only use funds you are comfortable risking.\
    The platform does not guarantee profitability or compensate for losses resulting from strategy settings or market movements.
  </Accordion>

  <Accordion title="What happens if my exchange API keys expire or disconnect?">
    The agent automatically detects lost connectivity and transitions to Suspended state.\
    It will stop placing or managing orders until a valid connection is restored.\
    You’ll be notified via system alerts and Telegram (if connected).
  </Accordion>

  <Accordion title="Is there a limit to how many agents I can run simultaneously?">
    Each plan or workspace may include a maximum active agent limit based on performance capacity.\
    If you reach your limit, you’ll need to stop an existing agent or upgrade your workspace to launch more.
  </Accordion>
</AccordionGroup>

### 📊 Analytics

<AccordionGroup>
  <Accordion title="Where does the analytics data come from?">
    From on-chain sources (holders, transfers, contracts) and connected exchange feeds.\
    Minor data delays are possible depending on chain/network speed.
  </Accordion>

  <Accordion title="Why do numbers differ from other sites?">
    Methodologies and data windows differ.\
    Flow Terminal prioritizes on-chain truth and verified exchange feeds.
  </Accordion>

  <Accordion title="Can I track the same token on another chain?">
    Yes — add the token’s contract for that chain separately.\
    Each contract operates as an independent analytics scope.
  </Accordion>
</AccordionGroup>

### 🔔 Alerts

<AccordionGroup>
  <Accordion title="Are alerts enabled by default?">
    Yes. Built-in types: Whale Transfer, Exchange Inflow, Exchange Outflow, Sell-Pressure Touch.\
    → Manage them in .
  </Accordion>

  <Accordion title="How do I adjust alert thresholds?">
    In Alerts, set minimum amounts (Token / USD) or a × multiplier for Sell-Pressure events.\
    Tune them to match your trading volume and volatility.
  </Accordion>

  <Accordion title="I receive too many or too few alerts — what should I do?">
    Raise or lower thresholds, or disable certain alert types in Manage Alerts.
  </Accordion>

  <Accordion title="Why are some tx links delayed?">
    Some data providers publish transaction hashes with a short delay.\
    Refresh the page — they’ll appear automatically.
  </Accordion>
</AccordionGroup>

### 📨 Telegram

<AccordionGroup>
  <Accordion title="How do I receive alerts in Telegram?">
    Go to , authorize the agent, then Send test.\
    Choose the chat/channel where you want messages delivered.
  </Accordion>

  <Accordion title="Connected but not receiving messages?">
    • Use Send test.\
    • Ensure the agent is in the chat with post permissions.\
    • For private groups, invite the agent and select the correct destination.
  </Accordion>
</AccordionGroup>

### 🔍 Troubleshooting

<AccordionGroup>
  <Accordion title="Common issues and quick fixes">
    • No data after adding a contract: initial sync may take time — refresh or verify address.\
    • Telegram silent: check agent permissions and resend test.\
    • Too many alerts: raise thresholds or disable types.\
    • CSV import fails: use UTF-8 CSV with headers: address,title,category,sell\_probability,comment.
  </Accordion>

  <Accordion title="Need more help?">
    Visit  or contact the team with details:\
    contract, network, exchange, and a short description of the issue.
  </Accordion>
</AccordionGroup>