> For the complete documentation index, see [llms.txt](https://wp.saplings.earth/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.saplings.earth/presentation/the-project.md).

# The Project

\
**Discover the first FREE 3D dynamic Collection of 3000 NFTs healing humanity.** 🌎🔥\
\
Saplings wishes to give back its rights to Nature by working with the community to address the biggest world crisis: climate change – demonstrating that we can drive change together.\
\
It is a nostalgic mash-up of games we played as kids, including Animal Crossing, Pokemon, and Tamagotchi—and we're building on top of that.

Meet Saplings, our 3D Interactive Mascot, see their growing, enjoy community-driven events and get rewarded on the [long-term](/vision/roadmap.md) while helping fight climate change. 💪

{% embed url="<https://www.saplings.earth>" %}
**Link to the website**
{% endembed %}


---

# 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://wp.saplings.earth/presentation/the-project.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.