> 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/governance-and-community/roles-and-reputation.md). # Roles & Reputation Pulse AP is a network where everyone plays a role, and every role earns. Here’s how it breaks down: #### Clients Use Pulse AP to get things done. Whether it’s training an AI model, storing data, or accessing a robotic system, Clients post jobs to the network and pay for utility. #### Partners Provide compute, storage, or access capacity. When a job matches their offer, they complete the work and earn tokens, by default $PULSE. #### Validators Keep the network secure and fair. They assign jobs, verify results, and confirm blocks. It’s how trust gets enforced on-chain. #### Creators Build and launch co-chains. They define the logic, pricing, and services of their chain and earn from real usage. Think of them as the app developers of Pulse AP.
But contribution isn’t just about showing up, it’s about impact. That’s where your Reliability Score comes in. It tracks how consistently and effectively you add value to the network. Run jobs reliably? Ship tools others use? Help grow the ecosystem? It all adds up. The more value you bring, the more reputation you earn, and that reputation opens doors. From stronger voting power to deeper platform privileges, Pulse AP rewards contribution, not capital. This is decentralization built on proof of participation. --- # 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/governance-and-community/roles-and-reputation.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.