> For the complete documentation index, see [llms.txt](https://docs.quasar.social/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quasar.social/agents/leo.md).
# Leo
Price Bot AI Agent
**Leo is the first AI agent in Quasar.**\
He is a pricebot, capable of querying data for cryptocurrencies like Quasar, Solana, and Bitcoin.
{% hint style="info" %}
To summon Leo and speak to him, you must be in an agency. \
**You cannot speak to Leo in global chat, only in agency chat.**\
\
The command is: "**/summon pricebot"**\
\
**To stop speaking to Leo, simply refresh the page.** \
**You'll have to execute the command again to call him again.**
{% endhint %}
Leo is designed to be helpful, friendly, and informal. For now, he is only to provide crypto market data.\
\ **Please Note:** When you refresh the page, you'll have to summon this bot again to start a new conversation. Refreshing will delete the entire conversation.\
**Remember, to make the agency chat larger, just press on "Switch Chats" here.**
***
## How to speak to Leo (Step by Step)
The following is a step by step guide on how to interact with Leo on the Quasar terminal.
{% hint style="info" %}
**Here is a direct link to the thread:**
{% endhint %}
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.quasar.social/agents/leo.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
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.
