> For the complete documentation index, see [llms.txt](https://pregator-documentation.gitbook.io/pregator-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pregator-documentation.gitbook.io/pregator-whitepaper/pregator-labs-official-whitepaper-v1.0/welcome-to-pregator.md).

# Welcome to Pregator

1. **Vision & Ecosystem**

**Pregator ($GATOR) is a next-generation utility-driven memecoin built on the Solana blockchain using the advanced Token-2022 standard.**

Unlike traditional memecoins that rely solely on speculative hype and often struggle to sustain long-term growth, Pregator is built with a different approach. We bridge the gap between meme culture and real-world software utility by creating a sustainable ecosystem powered by continuous development.

Led by the cyberpunk mascot **Pregator**, our mission is to build a transparent, community-driven ecosystem where **$GATOR** serves as the core utility, payment, and governance asset.


---

# 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://pregator-documentation.gitbook.io/pregator-whitepaper/pregator-labs-official-whitepaper-v1.0/welcome-to-pregator.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.