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

# Key Insights

#### SpamSentry Bot Configuration

SpamSentry enables its users to configure their SpamSentry Bot in various unique ways. A crucial aspect of owning a SpamSentry Bot is providing sufficient information so it can respond to queries on your behalf, similar to a human moderator. This process is facilitated through the user-friendly SpamSentry DApp, allowing you to modify datasets at any time.

#### Adding Data for the First Time

When activating your SpamSentry Bot, users can add the core knowledge or context immediately after setup. This initial configuration ensures that the bot understands your community’s specific needs from the start.

#### Updating or Adding More Data

Users can easily update news, add new information, or make any other changes directly through the SpamSentry DApp with just a click. Data can be erased or replaced as needed, and these modifications will be immediately reflected in your SpamSentry Bot. This process significantly reduces the training time typically required for a moderator and minimizes errors, allowing for a smoother experience in community management.


---

# 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:

```
GET https://spamsentry.gitbook.io/spamsentry.xyz/spamsentry-dapp/key-insights.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.