> For the complete documentation index, see [llms.txt](https://faq.coticommunity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.coticommunity.com/coti-faq.md).

# COTI FAQ

{% hint style="info" %}
This website aims at people who are new to COTI and serves as an all in one place knowledge base with the most important information for COTI holders.

The information provided is subject to change. Use the information on this website at your own responsibility. This is an unofficial COTI website run by COTI Unity Node (testnet). 

You can find offical information provided directly by COTI at <https://coti.io/> and <https://medium.com/cotinetwork>.
{% endhint %}

{% hint style="danger" %}
COTI V2 has launched. Still, we are in a transition period right now when it comes to certain features. That's why some content is not up to date right now. Once all releveant features are available on V2 and the transition is complete, the FAQ will be updated!
{% endhint %}

<figure><img src="https://1669873050-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fbb9VxoqAgZO2p5RjTuh9%2Fuploads%2FNZzbKCt5Nd4z04WShswM%2FCotit%20Unity%20Node%20Final%20transparent.png?alt=media&amp;token=d72c26bb-0491-4da7-92a0-e8c903520c38" alt="" width="188"><figcaption><p>powered by COTI Unity</p></figcaption></figure>


---

# 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://faq.coticommunity.com/coti-faq.md?ask=<question>&goal=<user_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.