# PUAI Utility

PUAI is a **pure utility token** created specifically for consuming AI-powered services within the Pumpad ecosystem. It is **not used for fundraising or investment purposes**, and serves as the core value exchange mechanism between platform services and users/projects.

#### 🛠 Key Use Cases of PUAI

**1. Access to AI Tools & Analysis**

* Blockchain data modeling (project tracking, token behavior analysis)
* Automated report generation and project research summaries
* Smart contract auditing and real-time risk alerts

**2. Community Automation & Growth Services**

* Activation of Telegram Bot plugins (tasks, points, leaderboards)
* Monitoring user engagement and segmentation tools
* Reward automation (address binding, task verification, airdrop execution)

**3. AI Content & Design Engine**

* One-click generation of tweets, summaries, AI-based visuals
* Multi-language content + Web3 keyword optimization
* Support for tone customization and influencer-style formatting

**4. Plugin Store & Modular Tools**

* Future Plugin Store will allow projects to activate custom modules using PUAI or even upload their own AI tools into the ecosystem

***

#### 🔄 Consumption & Deflation Model

* PUAI has **no staking/yield** and **no governance rights**
* Every AI request or tool interaction consumes PUAI based on frequency or compute cost
* All consumed PUAI is **burned automatically** with on-chain proof
* Free usage is limited to early testers and partners; PUAI is required for regular access


---

# 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://pumpad.gitbook.io/pumpad.ai/puai-utility.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.
