> For the complete documentation index, see [llms.txt](https://moni-ai.gitbook.io/moni/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moni-ai.gitbook.io/moni/moni-extension/analytics/personal-context-tags.md).
# Personal context – Tags
**Tags** are your **Personal Context** layer in Moni — simple labels you attach to the accounts, wallets, tokens, and communities you care about. Assign meaning once, and Moni recognizes it every time you see that entity again — no memory required.
### Where Tags Are Used
Tags can be applied across **four** entity types:
| Entity type | What you tag |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **X (Twitter) Accounts** | Used to mark and categorize profiles you discover in your feed. |
| **Contract Addresses (CA)** | Used to label tokens so you can quickly recall their context or narrative. |
| **Wallets** | Used to track and identify specific holders, smart money, or any wallets you want to monitor. |
| **X Communities** | Tag X Communities to track their narrative and engagement. Tagged communities surface their context across supported platforms. |
{% hint style="info" %}
All tags sync with the extension and are available any time from the **Tags** page.
{% endhint %}
### How It Works
Tagging X Accounts
When you come across an interesting account on X, you can assign a tag to it directly.
Step 1. Open the profile of the account.
Step 2. Click the purple "edit" button.
Step 3. Enter your custom tag.
Step 4. Save!
{% hint style="info" %}
#### Once assigned, the tag will appear across X wherever this account is visible. It will also be available inside the extension.
A simple example would be tagging an account as “smart account”. The next time you see it in your feed, you immediately understand its relevance without needing to recall who it is.
{% endhint %}
Tagging Wallets
Tags can also be applied to wallets directly from token analytics.
Step 1. Open a token page.
Step 2. Navigate to the "Holders" section.
Step 3. Select a purple "Edit" button.
Step 4. Assign a tag.
Step 5. Save!
This allows you to label wallets based on behavior, strategy, or any pattern you identify.
{% hint style="info" %}
#### The tagged wallet will also be stored inside the extension for future reference.
{% endhint %}
Tagging Contract Addresses
The same approach applies to tokens. You can assign tags to contract addresses to describe their narrative, origin, or any important context. This makes it easier to recognize tokens when revisiting them later or encountering them again in different flows.
Step 1. Navigate to the token page.
Step 2. Click the purple "Edit" button.
Step 3. Assign the tag.
Step 4. Save!
{% hint style="info" %}
#### It's also stored in the Moni Extension "Tags" page.
{% endhint %}
### Unified Tag System
Tags created anywhere in Moni (a token page, the X feed, a wallet panel) all land in the same place. That gives you one consistent layer of context across:
* social discovery
* onchain analysis
* trading flow
Everything in one place, no scattered notes or mental bookmarks.
{% hint style="info" %}
#### Open the Tags page in the extension to sort and filter every tagged entity in one view.
{% endhint %}
---
# 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://moni-ai.gitbook.io/moni/moni-extension/analytics/personal-context-tags.md?ask=&goal=
```
`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.