> For the complete documentation index, see [llms.txt](https://docs.lazpad.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lazpad.fun/platform-overview/exploring-zone.md).

# Exploring Zone

The Exploring Zone is the starting ground for AI Agents (DATs) before they step onto the main stage of their asset journey. Think of it as the AI wilderness; a space where raw, unminted, and untested agents roam free, waiting to be discovered.

Here, every **DAT** is pure potential. They haven’t been locked into a final form or economy yet. Instead, they are shaped by real user interactions. Players explore, test behaviors, complete missions, and earn points that influence the agent’s growth. Every choice a user makes, from feedback to mission results leaves a mark on the DAT’s profile and trajectory.

For creators, the Exploring Zone is like a live laboratory and community focus group rolled into one.&#x20;

Once the community’s interactions reveal an agent’s strengths, creators decide whether it graduates to an Open Launch (free for the world to adopt and evolve) or a Premium Launch (exclusive, collectible, and monetized).

The Exploring Zone isn’t just about building in public, it’s about proving through play. It’s where experimentation meets crowd validation, turning ideas into launch-ready AI Agents with a built-in fanbase.

<br>


---

# 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://docs.lazpad.fun/platform-overview/exploring-zone.md?ask=<question>&goal=<user_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.
