> 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://somnia.gitbook.io/somnia/introduction.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.