> For the complete documentation index, see [llms.txt](https://asynchronus.gitbook.io/asynchronus-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://asynchronus.gitbook.io/asynchronus-docs/frequently-asked-questions-faq.md).

# Frequently Asked Questions (FAQ)

Here are answers to some common questions about Asynchronus:

<details>

<summary><strong>What is Asynchronus in one sentence?</strong> </summary>

Asynchronus is a decentralized AI multi-agent system designed to autonomously execute complex Web3 workflows through a conversational interface.

</details>

<details>

<summary><strong>Is Asynchronus a wallet or an exchange?</strong> </summary>

Neither. Asynchronus is an *infrastructure and interface layer*. It connects to your existing Web3 wallet (non-custodially) and interacts with various exchanges (DEXs), bridges, and protocols on your behalf, based on your instructions.

</details>

<details>

<summary><strong>Is it safe to use? Can agents access my funds?</strong> </summary>

Security is paramount. Asynchronus is **non-custodial**, meaning we *never* have access to your private keys. All transactions that involve moving your funds or making critical changes **require your explicit approval and signature** via your connected wallet. Our Security Agent also works to vet protocols and transactions before presenting them to you.

</details>

<details>

<summary><strong>How does Asynchronus make money?</strong> </summary>

Our business model is designed to align with ecosystem growth and will likely involve several streams, such as:

* Fees on certain advanced or high-frequency agent actions.
* Revenue sharing or fees within the Open Agent Marketplace (for premium agents/tools).
* Partnership agreements with protocols seeking deep integration.

</details>

<details>

<summary><strong>Who can build agents for Asynchronus?</strong> </summary>

Anyone! Our **Graph** framework is designed for developers and research teams to build, test, and deploy their own specialized agents. We aim to foster an open ecosystem where the community can contribute new capabilities.

</details>

<details>

<summary><strong>When can I start using Shell?</strong> </summary>

Our MVP for Shell, featuring staking, bridging, and token discovery, is scheduled to launch in **June 2025**, starting with a closed beta. Stay tuned to our channels for launch announcements.

</details>

<details>

<summary><strong>What's the main difference between Shell and Graph?</strong> </summary>

**Shell** is the *user interface* – it's how you *talk* to Asynchronus and give it tasks. **Graph** is the *developer framework* – it's how you *build* the agents and tools that make Shell powerful.

</details>

<details>

<summary><strong>Do I need to know coding to use Shell?</strong> </summary>

No! Shell is designed to be used via **natural language**. If you can describe what you want to do in Web3, you can use Shell.

</details>


---

# 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://asynchronus.gitbook.io/asynchronus-docs/frequently-asked-questions-faq.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.