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

# Introduction

## What is Arcana Intelligence? 

Arcana Intelligence is a market-awareness protocol designed to interpret signals hidden inside:\
\
On-chain activity\
\
Sentiment patterns\
\
Liquidity behavior\
\
Trader psychology\
\
\
It began as an experiment:\
\
Tracking liquidity velocity, wallet heuristics, volatility pockets, and narrative momentum.\
The patterns aligned.\
The signals whispered before the market moved.\
\
Arcana is not a predictor.\
It is an interpreter.\
\
Arcana Intelligence provides a new layer of market cognition — helping traders, builders, and communities sense market shifts before they become obvious.\
\
This is the foundation of Arcana.


---

# 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://arcana-intelligence.gitbook.io/arcana-intelligence-docs/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.