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

# Introduction

<figure><img src="/files/CN21oD4UrUqYUmgWSqmz" alt=""><figcaption></figcaption></figure>

### This whitepaper introduces a new category of intelligence infrastructure built around on-chain and off-chain behaviour. It covers how Equinox operates, what problems it solves, and how its architecture supports high-precision analysis at scale.

Equinox AI is a behavioural intelligence dApp that connects wallet activity with public social data. It offers tools for monitoring identity-linked movement, tracing mixer and bridge flows, and uncovering patterns across platforms like Telegram and X.

This document provides a full breakdown of the platform’s architecture, feature set, token model, privacy systems, and long-term plans. You’ll also get an early look at how Equinox is positioned to serve as a data engine for both independent users and institutional clients.

Equinox is built for people who need more than surface-level visibility. This is your starting point.


---

# 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://equinoxai.gitbook.io/equinox-ai-whitepaper/overview/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.