> For the complete documentation index, see [llms.txt](https://docs.goop.gg/goop/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goop.gg/goop/overview/whats-goop.md).
# What's Goop?
**Goop** is an experimental generative NFT project for use in crypto games, metaverses, and interactive experiences.
The initial release are **specimen** tokens designed with 25+ base stats, abilities, and skills that can be adapted in a variety of ways and compatible with nearly any game style (RPGs, FPS games, card games, action games, sports games, racing games, etc.).
Additionally, there are more than 2 Quadrillion combinations possible for token attributes and characteristics.
The base stats in the specimen tokens can be used directly in a game, remapped to other stats, or completely ignored by game developers.
Specimen tokens are moldable like clay and serve as primitives in the Goop ecosystem.
First up are the **Legendary** batch.
These will be some of the most powerful specimen tokens in the collection.
There will only be 1024 available to mint.
{% hint style="info" %}
Goop specimen tokens will follow the **ERC-721** specification and be **CC0**.
{% endhint %}
---
# 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.goop.gg/goop/overview/whats-goop.md?ask=&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.
