> For the complete documentation index, see [llms.txt](https://jammy-1.gitbook.io/jammy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jammy-1.gitbook.io/jammy/introduction.md).

# INTRODUCTION

In an age where user engagement and community growth define the success of Web3 projects, Jammy emerges as a next-generation platform that merges gaming, social engagement, and task-based earning. It is not just another play-to-earn or task platform — it is a social layer of Web3 powered by gamified participation, underpinned by a sustainable token economy. \
\
At the core of Jammy lies a simple yet powerful loop: \
**Complete tasks. Earn chips. Play games. Win rewards. Stake tokens. Boost your power.**

By aligning project needs with user incentives in a fun, repeatable structure, Jammy provides an ecosystem where utility and entertainment are not mutually exclusive — they’re interwoven.


---

# 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://jammy-1.gitbook.io/jammy/introduction.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.