> For the complete documentation index, see [llms.txt](https://peeps-2.gitbook.io/peeps-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://peeps-2.gitbook.io/peeps-docs/peeps-whitepaper/how-it-works/creator-tools.md).

# creator tools

PEEPS is designed to give creators more than a deploy button.

## Launch configuration

* token name and ticker;
* token image and description;
* official website and social links;
* optional initial buy, if supported;
* content and legal confirmations; and
* preview of fees and graduation mechanics.

## Creator profile

A creator profile may show previous launches, public wallet information, verified social links and community reputation indicators.

## Updates

Creators can publish updates to their community page. Updates must not contain false promises, guaranteed-return language or misleading information.

## Earnings dashboard

Where enabled by the final fee contracts, creators can view accrued fees and claim eligible earnings from their own wallet.

## Analytics

Planned analytics include trade volume, unique traders, holder changes, page activity, social engagement and graduation progress.


---

# 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://peeps-2.gitbook.io/peeps-docs/peeps-whitepaper/how-it-works/creator-tools.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.