> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/december-14.md).
# Agent Network
### Agent Network: A Major Overhaul
Today we are releasing a new version of one of Rechat's most popular features: Agent Network.\
This is a completely rebuilt of this module but here is a list of most notable changes:
1. Agent Network is now accessible directly from side navigation.
2. You don't need a deal to access Agent Network anymore.
3. You can use agent network for any listing.
4. You can use one of your previous emails for your Agent Network marketing.
5. A completely overhauled user interface.
6. Much more accurate agent finding algorithms.
### Repositioning Create Button
Our usability studies indicated some tiny confusions regarding the "Create" button and it's functionality.\
Today we are placing it on the side navigation in order to:
1. Make it feel global, not localized to any specific page.
2. Make sure it shows up on all pages where we previously didn't have room for it, like the Contact Profile.\
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.rechat.com/whats-new/december-14.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 `automate deployments from our CI pipeline` 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.