# Vision

<figure><img src="/files/tjN34twPtStTwlL50j5C" alt=""><figcaption></figcaption></figure>

Traditional M2E services required users to make a payment to participate and primarily focused on activities like walking or running. This often led to a monotonous routine, causing users to feel bored quickly. Additionally, the limited structure provided few opportunities for users to directly engage with the community and participate in more community activities. As a result, user engagement and motivation faced limitations, and the economic value within the game remained restricted.

However, ZHunter has introduced innovative methods to overcome these limitations. By enhancing competition, cooperation, and social elements within the game, ZHunter encourages users to participate more actively and interact with each other. This allows users to feel a value beyond merely receiving rewards, increasing their immersion in the game.

Moreover, through the app, users can experience the joy of discovering and exploring their neighborhoods while enjoying a UI and user experience similar to traditional games. This will help them discover local small businesses they might have previously overlooked and enjoy various cultural and community activities in their area.

The ZHunter team plans to continue expanding its Web3.0-based service to promote healthy habits, rewards, and marketing. Future updates will allow users to equip NFTs and complete missions to earn token rewards and items.


---

# Agent Instructions: 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:

```
GET https://zhunter.gitbook.io/zhunter/overview/vision.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
