> For the complete documentation index, see [llms.txt](https://documentation.pulseap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pulseap.com/core-concepts/proof-of-utility-pou.md).
# Proof of Utility (PoU)
If you are not deep into the blockchain space, terms like Proof of Work, Proof of Stake, or Proof of Utility might sound confusing.
The key thing to understand is what **Proof of Utility (PoU)** represents and why it is different. Instead of burning energy to solve meaningless puzzles like Proof of Work, or earning passive rewards just for locking up tokens like Proof of Stake, Proof of Utility rewards and incentivizes real, measurable work.
This model links token emissions directly to verifiable tasks such as images processed, deliveries completed, or hectares scanned. Contributors earn only when useful work is successfully verified, capturing the measurable and trackable value that robotics and AI applications generate.
On **Pulse AP**, this means completing compute tasks, storing data, or managing secure access operations. When a task is finished, it is verified and recorded on-chain, turning real work into blockchain-anchored proof of utility. That is how blocks are created and how contributors earn **$PULSE**.
It is a model designed to reward those who contribute tangible value to the network.
---
# 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://documentation.pulseap.com/core-concepts/proof-of-utility-pou.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.