> For the complete documentation index, see [llms.txt](https://docs.chirptoken.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chirptoken.io/chirp-network/data-hunters.md).

# Data Hunters

## Who Are Data Hunters?

Data Hunters are Kage players who contribute to Chirp’s Decentralized Physical Infrastructure Network (DePIN) by scanning and mapping wireless networks. As they move through cities and buildings, Data Hunters detect Wi-Fi, Bluetooth, and cellular signals, helping build Chirp’s decentralized geolocation database.

Unlike traditional geolocation systems that rely solely on GPS, Chirp leverages crowdsourced wireless data to enable indoor wayfinding, power-efficient tracking, and real-world asset (RWA) applications. By playing Kage, Data Hunters gamify the process of expanding Chirp’s geolocation capabilities, ensuring more accurate positioning and unlocking new automation use cases.

To participate, Data Hunters walk, scan, and earn rewards in CHIRP tokens based on the quality and uniqueness of their collected data. Their contributions enhance Chirp’s IoT network, making it more robust for businesses, developers, and individuals who rely on precise location-based services.

<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 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://docs.chirptoken.io/chirp-network/data-hunters.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.