> For the complete documentation index, see [llms.txt](https://wiki.privai.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.privai.cloud/ecosystem-components/ai-analyst.md).

# AI Analyst

The AI Analyst turns scan results into readable guidance. It helps users understand what the evidence means, what matters most, and what actions may reduce risk.

## Active Modules

| Module                     | Purpose                                                                                                          | Status     |
| -------------------------- | ---------------------------------------------------------------------------------------------------------------- | ---------- |
| **security\_expert.chat**  | Natural-language security expert terminal.                                                                       | Active     |
| **risk\_summary.aic**      | Summarizes saved scan results into a risk overview.                                                              | Active     |
| **action\_plan.aic**       | Converts saved findings into prioritized next steps.                                                             | Active     |
| **project\_osint.brief**   | Generates a project OSINT brief from pasted token, website, social, deployer, liquidity, or team-claim evidence. | MVP active |
| **signature\_explain.aic** | Explains approvals, signatures, and transaction intent defensively.                                              | Staged     |

## What Good Output Looks Like

AI output should be:

* Evidence-backed.
* Plain-language.
* Practical.
* Defensive in scope.
* Clear about uncertainty.
* Easy to save into Case Files.

## Guardrails

The PRIVAI analyst is scoped to defensive security and privacy use cases.

It should help users with:

* Wallet hygiene.
* Scam detection.
* Approval risk review.
* Incident triage.
* Phishing and domain review.
* Token and project risk interpretation.
* Personal OpSec planning.

It should not help users with:

* Stealing keys or funds.
* Phishing.
* Wallet draining.
* Malware.
* Cleaning or hiding stolen funds.
* Evading compliance.
* Laundering or obfuscating illicit assets.


---

# 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://wiki.privai.cloud/ecosystem-components/ai-analyst.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.