> 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/co-chains-explained/monetizing-with-co-chains.md). # Monetizing with Co-Chains When you operate a co-chain on **Pulse AP**, you are not just building technology, you are creating a business. You decide your own usage fees, in **$PULSE** or your own native token. Every time someone uses your co-chain, whether they are running a task, executing a function, or accessing a service, you earn revenue. Want to sell something on your co-chain? Go for it. That could be a license, a premium feature, or even digital assets. You do not need your own token to make it work either. The system supports a shared payment framework, allowing you to get paid seamlessly without managing token swaps or complex integrations. You build something valuable, users pay to use it, and you earn. It really is that simple. You can even sell your entire co-chain to another builder or organization, creating new ecosystems and markets that expand the broader **Pulse AP** economy. --- # 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/co-chains-explained/monetizing-with-co-chains.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.