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

# FAQ

<details>

<summary><mark style="color:blue;">What kind of data can be stored in Context Documents?</mark></summary>

Context Documents are designed to hold any data in JSON format, including metadata and structured data. They are not designed for storing images, audio, or video files.

</details>

<details>

<summary><mark style="color:blue;">What is a Template?</mark></summary>

A template is a set of rules that defines how data is structured and how it should be stored in a database. It provides a blueprint for organizing and describing data elements, attributes, and the relationships between them. A schema can be used to define the data types, constraints, default values, and other rules that should be followed when creating and managing a database.

</details>

<details>

<summary><mark style="color:blue;">What is the Universal Name Registry?</mark></summary>

The Universal Name Registry or UNS, is the reference point for the schemas and SmartPods on the Context platform, allowing for easy access and organization of the data. It helps to ensure that data is standardized and easily accessible for all builders.

</details>

<details>

<summary><mark style="color:blue;">How is Context different from other data platforms?</mark></summary>

Context is unique in its focus on data interoperability and portability. By providing standardized schemas and a decentralized approach to data management, it makes it easier for builders to seamlessly integrate data from different sources and build innovative projects.

</details>

<details>

<summary><mark style="color:blue;">How can I get involved in Context?</mark></summary>

There are several ways to get involved in Context, including joining a Working Group, creating a SmartPod, or building a Front-end with Context technology. You can contact us through our website or [group of Telegram](https://t.me/contextdao) to learn more about Context.

</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://docs.ctx.xyz/dns3/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.