> For the complete documentation index, see [llms.txt](https://verlexy.gitbook.io/about-verlexy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://verlexy.gitbook.io/about-verlexy/welcome-to-verlexy-engine.md).

# WELCOME TO VERLEXY ENGINE

Beta Release date: \[18/sept/2026]

<p align="center"><em><strong>Verlexy</strong></em> is a next-generation, strictly Safe-For-Work (SFW) AI Text RPG &#x26; Interactive Novel Engine running directly inside Discord. Powered by Google's advanced Gemini technology, Verlexy acts as a highly disciplined, reactive <strong>Dungeon Master (DM)</strong>. </p>

<p align="center">Unlike conventional, passive AI chatbots that suffer from rapid memory loss and narrative "railroading," Verlexy is engineered as an active, persistent sandbox. It grants writers, roleplayers, and worldbuilders absolute freedom to construct original universes, embark on immersive campaigns, and compile their journeys into beautiful visual web novels.</p>

***

<div data-with-frame="true"><figure><img src="https://33295490-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZuZj5Qug9otm5wF5RZSr%2Fuploads%2F4eUVxY1IT4H88fZe42dS%2F1000307748.jpg?alt=media&amp;token=f760a912-1889-4e4f-afa5-95ba1d018ffc" alt="" width="188"><figcaption></figcaption></figure></div>

<h4 align="center">🚨 CURRENT STATUS: FREE OPEN BETA (v1.0)</h4>

<p align="center">Verlexy is currently in its <strong>Free Open Beta (v1.0)</strong> phase. This is a testing ground designed to stress-test our backend logic, database stability, and user experience. <br><br>To show our appreciation to early adopters, <strong>every user who joins our server and completes the phone verification process will automatically receive a FREE VIP Tier Role!</strong></p>

<p align="center"></p>

<p align="center"><br></p>

***

<h2 align="center">⚠️ Critical Beta Disclaimers &#x26; Inherent Limitations</h2>

<p align="center">Because we are running this Beta on a highly restricted budget, you must be aware of the following technical realities:</p>

<h4 align="center">   💾 Resource-Constrained Hosting</h4>

<p align="center">Our current temporary server runs on a minimal budget setup. Because of this extreme storage limitation:</p>

<p align="center"><strong>- 7-Day Inactivity Auto-Cleanup:</strong> Active threads that receive no messages for <strong>7 consecutive days</strong> will be automatically purged from our server database.<br>   <strong>- Dynamic Cleanup Policy:</strong> To prevent our disk from filling up, this cleanup policy is highly volatile. It may be reduced to a 3-day limit, or in extreme cases, we may perform emergency database wipes (even on active threads). <br>   <strong>- Export Your Progress:</strong> We highly recommend utilizing our <code>/export-story</code> command frequently to save your adventure <code>.json</code> file to your local device.</p>

<h4 align="center">🖥️ Server Stability &#x26; Unpredictable Downtime</h4>

<p align="center"> Crashes, file corruptions, and database desynchronizations are expected during this phase. The bot may go offline mid-game, and in some instances, <strong>downtime may last for several days</strong> while the solo developer manually debugs the system. </p>

<h4 align="center">💾 Free-Tier API Memory Cap (250k Tokens)</h4>

<p align="center">Because v1.0 utilizes Google's Free-Tier API keys, your campaign memory is capped at a maximum of <strong>250,000 tokens</strong> (approximately ~1.04MB of raw JSON history data). </p>

<p align="center">  <strong>-</strong> <strong>Rate-Limit Warning:</strong> Free-tier keys are subject to Google's strict minute-by-minute rate limits. If the server is crowded, you may occasionally experience "Mana Depleted" cool-downs. Simply wait 1 minute for the API to reset.</p>

<h4 align="center">🔑 BYOK (Bring Your Own Key) Support</h4>

<p align="center"> To completely bypass public server queues and avoid cool-downs, you can link your personal, free Google API Key via the <strong><code>/set-my-key</code></strong> command. You will still enjoy the full 250k token memory, running entirely on your own free quota!</p>

***

<h2 align="center">🚀 THE ROAD TO VERLEXY v2.0 ($120 USD CROWDFUNDING GOAL)</h2>

<p align="center">To transition from an unstable, local prototype into a commercially viable, 24/7 autopilot service, we have launched a community crowdfunding campaign with a target goal of <strong>$120 USD</strong>.<br></p>

<h3 align="center">📊 How the $120 Funding Will Be Allocated</h3>

<h4 align="center">🌐 High-Performance VPS Hosting ($43.50 USD)</h4>

<p align="center">Securing a stable, lightning-fast <strong>DigitalOcean Droplet</strong> for 6 months, including their premium <em><strong>Automated Daily Backups ($1.25/mo)</strong></em> to ensure your active databases are 100% protected against corruption and server crashes.</p>

<h4 align="center">💳 Authorized Google Cloud Partner Deposit (~$64.00 USD)</h4>

Funding our initial prepaid billing deposit through !!! official Google Cloud Reseller (PointStar/Cloud Ace). This activates our **Paid Enterprise API Keys**, removing public queues, rate limits, and lowering bot response times to under 1.5 seconds.

<h4 align="center">🏦 Transaction Fees &#x26; Reserve (~$12.50 USD)</h4>

<p align="center">Covering standard PayPal/Stripe payment gateway processing taxes.<br>Once this milestone is reached, we will deploy <strong>Verlexy v2.0</strong>, introducing the <strong>True Anti-Amnesia AI (Up to 1M+ Context)</strong>, the <strong>Lexsi Coin Economy, UGC Template Sharing</strong>, and our <strong>Wattpad-style Forum Novel Hub</strong>!</p>

***

<h3 align="center">💎 EXCLUSIVE REWARD</h3>

<p align="center">THE LEGACY @Beta Supporter ROLE<br>As a tribute to those who help us build our foundations, anyone who donates any amount (ekven just $1!) to our Ko-fi page during this v1.0 phase will instantly receive the exclusive <strong><code>💎丨BETA SUPPORT</code></strong> role in our Discord.</p>

<p align="center"><strong>- A Lifetime Legacy:</strong> This role is highly limited. Once the Open Beta ends and Verlexy 2.0 launches, <em><strong>this role will be locked forever and will never be obtainable again.</strong></em></p>

<p align="center"><strong>- Future Perks:</strong> In future updates, this role will act as a "Founder's Badge of Honor," granting permanent aesthetic profile badges, special Lexsi Coin earning boosts, and exclusive community privileges as a thank-you for believing in us when we had nothing.<br><br>👉 Support Our Journey on Ko-fi: (Coming soon)<br>👉 Enter the Guild Hall on Discord: (Coming soon)</p>

<p align="center"></p>

<p align="center">notes: This information is preliminary and may change suddenly. We will not release the official links for our Discord and Ko-Fi platforms until we are certain our platform is ready for beta release.</p>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://verlexy.gitbook.io/about-verlexy/welcome-to-verlexy-engine.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
