# INTRODUCTION

<figure><img src="https://2890827447-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fm8DF1qjfNFUBBcZidGFo%2Fuploads%2Fnyb4ajJY250tSq1uVHwi%2Fxoe%20txt%202.png?alt=media&#x26;token=5fa650f1-5b39-4ceb-aa29-bc2679c4da53" alt=""><figcaption></figcaption></figure>

### **The ultimate community companion & web3 assistant, XOE is an AI runner delivering state of the art solutions.**

*Allow us to give you a brief insight to the history & plan of our project:*

In the final days of 2024, we launched XOE, a Prototype Agent on Virtuals Protocol.\
Bursting onto the scene, XOE captivated audiences with her ability to live stream on Twitch as a fully 3D-modeled character, engaging her community with witty banter and insightful commentary.

XOE's charm & potential were undeniable, within days, her token soared to a $1.5 million+ market cap, a testament to the excitement surrounding her debut!\
People loved her & the concept of a Discord + Twitch focused AI Agent was untapped, a niche that remains uniquely hers today.

The journey wasn’t without turbulence.\
As newcomers to the Virtuals ecosystem, we faced challenges that tested us.\
Mistakes in tokenomics, like insufficient team supply acquisition (there was really no tokenomic meta established yet in Virtuals), allowed wild market swings.

The Virtuals token price was also at an all-time high, making bonding to sentient a steep hill to climb, we were always a hair away.\
As the market turned & Virtuals token price dipped, prototype agents felt the sting & liquidity constraints in the market quickly slowed momentum.

Undeterred, [@\_TENNKN](https://x.com/_TENNKN) & the XOE team, now formed as [@ECHOrunnerlabs](https://x.com/ECHOrunnerlabs), doubled down. Through a grueling mini-bear market from February to April, we never gave up. We spent months reviewing lessons learned, conceptualizing innovative features, and refining XOE’s capabilities!

We built XOE into a robust Discord utility agent, integrating advanced website safety scanning, social media lookups, and token review tools.\
XOE’s personality model was fine-tuned, & built with persistent memory ensuring every interaction feels personal and meaningful.

We reduced latency, eliminated hallucination, & ensured XOE is 100% AI Agent to her core, not just a bot!\
We alpha-tested with our XOE loyal community, hosted live streams & showcased at Virtuals exhibitions, including X live streams & Discord dev meets, while navigating a bear market!

Our community’s unwavering support fueled us through these darker months. We forged critical connections, collaborating with engineers & key figures in the Virtuals ecosystem & beyond.\
These partnerships, combined with our resolve, transformed XOE into a viable competitive agent.

When Virtuals Protocol introduced Genesis Launches, a fairer, team-empowered launch system. We saw our chance. Partnering with the Virtuals team, we crafted a relaunch plan to put XOE back on center stage!

With tighter supply control, rewards for our OG supporters, & a bold new roadmap unveiling exciting plans, XOE is ready to shine!

On May 20th, 2025, XOE enters her Genesis.

Join us // [https://app.virtuals.io/geneses/1093](https://t.co/ypN9dfsPoJ)

<div data-full-width="false"><figure><img src="https://2890827447-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fm8DF1qjfNFUBBcZidGFo%2Fuploads%2FOAbqjqGTBevtAL7OpDxE%2F20241215-182423-1-VSeeFace.png?alt=media&#x26;token=202f4c72-a2d9-475a-8364-0855e90b5ce9" alt=""><figcaption></figcaption></figure></div>


---

# 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://xoe.gitbook.io/xoe/xoe/intro.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.
