> 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/introduction.md).
# Introduction
**PRIVAI** is a privacy intelligence operating system for Web3 users who want to understand risk before they connect a wallet, sign a message, buy a token, bridge funds, or trust a project.
Web3 moves fast. A single unsafe approval, fake claim page, compromised domain, suspicious deployer, or exposed identity signal can create real damage. PRIVAI brings those checks into one focused workspace so users can investigate first and act with better context.
> **See the risks before they see you.**
### What PRIVAI Is
PRIVAI is a defensive privacy and threat-intelligence platform.
It helps users review:
* Wallet exposure and public on-chain behavior.
* Token approvals, account authorities, and wallet hygiene.
* Token, deployer, liquidity, and project-risk signals.
* Suspicious domains, phishing URLs, fake claim pages, and site posture.
* Public identity exposure across emails, usernames, domains, and phone metadata.
* Privacy-aware swap and bridge preparation for supported workflows.
* AI-assisted summaries, action plans, and saved investigation reports.
### How It Works
PRIVAI is designed around a simple investigation flow.
| Step | What Happens |
| ------------------------- | ---------------------------------------------------------------------------------------- |
| **1. Enter a target** | Start with a wallet, token, domain, URL, username, email, phone number, or project link. |
| **2. Run modules** | Open focused tools inside the PRIVAI OS interface. |
| **3. Review findings** | Read structured reports with evidence-backed risk signals. |
| **4. Ask the AI Analyst** | Generate summaries, explanations, and practical next steps. |
| **5. Save Case Files** | Keep scan results and exports for later review. |
### Product Areas
PRIVAI is organized like a cloud-style Web3 operating system. Each folder represents a major security category.
| Area | Purpose |
| -------------------- | ------------------------------------------------------------------------------------------- |
| **Wallet OpSec** | Understand wallet exposure, approvals, counterparties, and on-chain behavior. |
| **Private Routing** | Prepare supported swap and bridge workflows with stronger route awareness. |
| **Token Intel** | Review token contracts, deployers, holders, liquidity, rug-risk, and project reuse signals. |
| **Identity Defense** | Check breach exposure, username reuse, phone metadata, and public identity links. |
| **Threat Intel** | Investigate domains, phishing pages, fake claims, and risky web infrastructure. |
| **AI Analyst** | Turn scan results into readable summaries, project briefs, and action plans. |
| **Case Files** | Save reports, scan history, and exportable evidence from investigations. |
### Access
Current PRIVAI OS access is token-gated.
Users must connect a Solana wallet, sign a login message to prove ownership, and hold at least:
```
1,000,000 $PRIVAI
```
Configured mint:
```
Gc7QGptjL88oM8uzGTBKw8Zhnm2Gp3P73sYdf6zZpump
```
Signing the login message does **not** authorize a transaction or transfer funds.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://wiki.privai.cloud/introduction.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
