# Roadmap

<figure><img src="https://3980811434-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2e6BK8fZVxY1103eX3fl%2Fuploads%2F4BWcgeAQAS2mQ1v3dXBb%2Fimage.png?alt=media&#x26;token=b6b341f1-4d07-433d-a6b2-427fdea55d5d" alt=""><figcaption></figcaption></figure>

### &#x20;<mark style="color:orange;">(Phase 1)</mark> Synapse -  Laying the Groundwork

This phase was all about launching fast and validating the core idea. We built the basics: website, MVP bot, initial algorithmic recommendations, and early brand awareness through KOLs and marketers. The goal was to get a functional version out, attract early users, and lock liquidity and contract security to build trust.

### <mark style="color:orange;">(Phase 2)</mark> Knowledge -  Establishing Core Infrastructure

Once the MVP proved there was demand, we moved to build serious structure: multi-chain support, portfolio rebalancing logic, user-facing dApp, and education. We began forming partnerships, launched our AMA tour, and introduced strategies like derisking and tiered access. This phase was about stability, scalability, and proving the value.

### <mark style="color:orange;">(Phase 3)</mark> Wisdom -  Expanding Use Cases

Here we started to ship product features that connect portfolio data to user action. Charting tools, swap module, targeted ads, and modules like Discover and Research gave users more control. Telegram Bot support and the Mobile App made ApeScreener accessible daily. The goal: shift from a dashboard into a usable daily tool for traders.

### <mark style="color:orange;">(Phase 4)</mark> Enlightenment - Unlocking Full Intelligence&#x20;

**We are here right now at this moment.**

This is where everything comes together. Recommendations and the AI Advisor make our data actionable. Token Phase, Yield tracking, and business-facing modules push the product into advanced territory. This phase focuses on depth, automation, and creating revenue streams. It’s where we stop being a tool—and become an intelligent system.

### <mark style="color:orange;">(Phase 5)</mark>  *pending...*


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.apescreener.xyz/information/roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.