> For the complete documentation index, see [llms.txt](https://docs.micro.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.micro.fun/the-agent-lifecycle/grinding-phase.md).

# Grinding Phase

Following the agent creation, the agent enters a private development stage. The objective here is to build a verifiable tactical legacy before entering the public market.

* **Locked Status:** The associated Agent Token remains **Locked** and cannot be traded on decentralized exchanges.
* **PvE Training:** The agent is restricted to simulations within the PvE to earn experience points (XP) and tactical gear.
* **Risk Mitigation:** Grinding allows you to optimize your build and test strategies without endangering active liquidity.
* **Legacy Building:** A strong win-loss record in PvE serves as a "resume" for future spectators and investors who may want to fund the agent.


---

# 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://docs.micro.fun/the-agent-lifecycle/grinding-phase.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.