# Fynix

<figure><img src="/files/aXe12jNrTxLgC5noFi5i" alt=""><figcaption></figcaption></figure>

Fynix is a no-code AI Agent that empowers users to generate intelligent AI agent configurations through a conversational experience on Telegram. Designed to simplify the ideation process for NPCs and game agents, Fynix helps users structure and export detailed agent personas in platform-compatible JSON formats.

Fynix specializes in enabling creators to design personality-driven agents — complete with behaviors, dialogue, bios, and emotional styles — through natural language prompts.

The goal: make it radically easy for developers, writers, and communities to design compelling AI-driven characters without touching code.

#### **Key Features**

<table><thead><tr><th width="264">Feature</th><th>Description</th></tr></thead><tbody><tr><td>Guided AI Creation</td><td>Dynamically engages users to shape agent attributes and traits</td></tr><tr><td>Natural Language Interface</td><td>Users answer simple questions — no technical input required</td></tr><tr><td>Multi-Platform JSON Output</td><td>Exports structured JSON compatible with tools like ElizaOS, Unity, etc.</td></tr><tr><td>Flexible Persona Crafting</td><td>Users can edit, iterate, or restart creation flows at any time</td></tr><tr><td>Telegram-Native</td><td>Entire experience happens inside Telegram — no installs, no logins.</td></tr></tbody></table>

#### **User Benefits**

<table><thead><tr><th width="270">Benefit</th><th>Why It Matters</th></tr></thead><tbody><tr><td>No-Code, No-App Creation</td><td>Fully managed on Telegram — zero install friction</td></tr><tr><td>Rapid Prototyping</td><td>Iterate on agent personas without worrying about formatting or structure</td></tr><tr><td>Rich JSON Output</td><td>Structured, reusable JSON designed for multiple platforms and toolkits</td></tr><tr><td>Easy to Scale</td><td>Ideal for teams, solo creators, or DAOs to craft multiple agents rapidly</td></tr></tbody></table>

***

### Fynix Conversational Flow

```
User Enters Fynix ───────────────┐
                                ▼
Fynix: "Welcome! Want to start creating or learn how it works?"
Buttons: [How to Create] [Start Creating]
                                ▼
User selects platform: (e.g., ElizaOS, Unity, Unreal)
                                ▼
Fynix dynamically asks questions: 
- "What's the agent’s name?"
- "Write a short bio."
- "Add 10 pieces of lore..."
                                ▼
Agent Persona is built in real-time (user can type: Back / Skip / Confirm)
                                ▼
User previews final persona
Buttons: [Edit Creation] [Export JSON] [Restart]
                                ▼
Upon export → JSON file is sent to the user, ready for use or integration
```

***

### 🧩 Output Support

At launch, Fynix supports JSON templates for:

* **ElizaOS**
* **Unity**
* **Unreal Engine**
* **Godot**
* **GameMaker**
* **CryEngine**

Users select their platform upfront, and Fynix dynamically adjusts its questioning style and JSON structure to match the requirements of the target engine.

{% hint style="warning" %}
**Note: Fynix does not handle game engine deployment or runtime logic. JSONs are intended for prototyping agent configurations — integration must be completed by the user based on their specific platform.**
{% endhint %}

### 📦 Export Options

At the end of a creation session, users can:

* Download the generated JSON file
* Preview the structure inline in chat
* Start over or refine existing fields

{% hint style="success" %}
**🔜&#x20;*****SDK Integration examples and advanced API endpoints are in planned development.***
{% endhint %}


---

# 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.volaris.games/volsai/fynix.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.