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

# Introduction

#### **What is SOMNIA?**

SOMNIA is a revolutionary **Emotional Intelligence (EQ) Layer** for blockchain that transforms raw on-chain data into psychological insights. By analyzing wallet behavior, transaction patterns, and market interactions, SOMNIA provides a deeper understanding of the emotional drivers behind crypto decisions.

#### **Why Emotional Intelligence in Web3?**

Traditional analytics focus on price, volume, and technical indicators—ignoring the human element. SOMNIA fills this gap by:

* **Identifying behavioral biases** (e.g., FOMO, panic selling)
* **Providing personalized feedback** to improve decision-making
* **Mapping market-wide sentiment** to predict trends before they happen

#### **Vision**

To create a **more emotionally aware crypto ecosystem** where users and protocols can interact with greater self-awareness and strategic clarity.


---

# 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://somnia.gitbook.io/somnia/introduction.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.