> 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-token/what-is-a-usdchirp-token.md). # What is a $CHIRP token $CHIRP is the utility and incentive token that aligns participation across the Chirp DePIN ecosystem on the Sui blockchain. It underpins how the network grows, how contributors are rewarded, and how demand from real-world usage is translated into on-chain economic activity. As Chirp expands its infrastructure footprint and service layer—connectivity, device operations, automation, and geolocation—$CHIRP functions as the settlement asset that coordinates incentives between infrastructure operators, data contributors, and the businesses building on top of Chirp. A key mechanism tied to $CHIRP is the network’s Data Credits model. When businesses and developers purchase Data Credits to consume Chirp services, that purchase triggers an open-market buy of $CHIRP. This purchase flow is designed to create demand that links real network usage to the token, while contributors across the ecosystem can earn $CHIRP for expanding coverage and producing valuable network data. Together, these mechanisms support a demand-driven token economy where utility—not speculation—is the primary driver of token demand. --- # 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-token/what-is-a-usdchirp-token.md?ask=&goal= ``` `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.