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

# Welcome to Dopameme

Dopameme is an intelligence terminal for meme-market traders who want context before execution.

It helps users understand where attention is forming, which tokens deserve a closer look, and how new evidence compares against previous reads. Dopameme does this through tracked-wallet attention, token scans, operator reads, holder context, market-quality filters, and a packet memory layer that compounds over time.

Dopameme is not a wallet, broker, exchange, custody product, or trading bot. It does not ask for private keys and it does not execute trades. The terminal gives users better market context so they can make their own decisions wherever they choose to trade.

## What Dopameme Is

Dopameme turns raw meme-market behavior into structured intelligence.

Most tools show a chart, a price, a feed, and a list of transactions. Dopameme is built to answer the harder question: what does this activity actually mean in context?

The terminal looks at who is paying attention, whether the token is large enough and clean enough to inspect, what the chart structure says, where important levels sit, and whether the current evidence confirms or contradicts what was recorded before.

## The Questions It Answers

Use Dopameme to answer five questions:

1. What is getting attention?
2. Who is paying attention?
3. Is the token clean enough to deserve a read?
4. What does the current structure say?
5. Did the evidence improve, weaken, or contradict the last packet?

## How The Terminal Works

The dashboard gives a broad view of current opportunities, active confluence, and useful discovery surfaces.

The confluence board shows tokens that passed tracked-wallet and market-quality filters.

The token page gives the detailed read: chart, levels, market data, holder context when available, tracked-wallet context, and the latest operator read.

Packets preserve evidence over time. When a token is scanned again, Dopameme can compare the new read against the old one instead of treating the token like a blank slate.

Audits challenge packet quality. If a read was thin, wrong, late, or missing important evidence, that should become visible in the audit trail. Over time, the protocol learns which observations were useful, which were noise, and which patterns deserve more weight in future reads.

## The Product Philosophy

Dopameme is built around intelligence, not execution.

The goal is not to flood users with every low-cap alert. The goal is to surface useful market context and explain why something matters. If a token is too noisy, too small, pre-bond, or dominated by poor-quality behavior, it can be hidden from the user-facing board even if the system saw activity.

That discipline is part of the product. Dopameme should help users slow down, compare evidence, and make better decisions before they act.

## Standalone Runtime

The Papa-Bear Dopameme repo is intended to run without the old Earlybirds / Looking Glass checkout.

Basic server setup:

```bash
python3 -m venv .venv
.venv/bin/pip install -r requirements.txt
.venv/bin/uvicorn dopameme.app:app --host 127.0.0.1 --port 8791
```

Optional service files live under `deploy/dopameme/` and assume the repo is checked out at `/opt/dopameme`.

Runtime secrets belong in environment files, not Git. Common variables include `BIRDEYE_API_KEY`, `OPENAI_API_KEY`, Privy auth settings, and Telegram bot settings when the bot is enabled.


---

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