# AI overview

![](/files/q4d6gaqCbaPR2oFP9fCd)

Sudo’s AI and bot surfaces make complex wallet and on-chain activity easier to understand. They should feel like assistants inside the messenger, not separate dashboards.

## AI Explorer

AI Explorer helps users ask questions about chains, wallets, tokens, and Web3 concepts. It can reduce onboarding friction for users who are not comfortable reading raw blockchain data.

## Bot surfaces

| Bot             | Purpose                                                         |
| --------------- | --------------------------------------------------------------- |
| Transaction bot | Presents transaction history in a chat-style interface.         |
| Watcher bot     | Sends wallet/contract alerts and monitoring updates.            |
| Approvals bot   | Guides users toward approval risk review.                       |
| My Tokens bot   | Gives shortcuts to holdings and token-related state.            |
| My Locks bot    | Gives shortcuts to locked tokens and vesting-style information. |

## Design principles

* Keep responses explainable.
* Show sources or links when possible.
* Avoid pretending uncertain information is guaranteed.
* Never encourage users to share seed phrases or private keys.
* Use clear risk language around transactions and approvals.

## Example usage patterns

* “Why did this wallet receive this token?”
* “Show recent transactions.”
* “Alert me when this contract changes.”
* “Which approvals look risky?”
* “Show my token locks.”

## Important disclaimer

AI output should be treated as informational assistance. Users should verify on-chain data before acting.


---

# Agent Instructions: 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://docx.sudochat.app/ai-and-bots/ai.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.