> For the complete documentation index, see [llms.txt](https://docs.gpubase.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpubase.network/how-it-works/user-and-provider-interaction.md). # User and Provider Interaction GPUBase Network operates through a decentralized architecture where GPU providers can connect their resources using the Provider App. Users request computational power for tasks such as AI training, rendering, or data analysis. Smart contracts automate transactions, ensuring they are secure and transparent. The token economy drives the system, incentivizing providers and supporting the network's sustainability. ### User and Provider Interaction * **Users**: Individuals or organizations submit requests for GPU resources through the platform. These requests may include data processing, machine learning tasks, rendering, or other intensive computational needs. * **Providers**: GPU owners register their resources on the network, making them available for allocation to user tasks. Providers earn rewards and revenue based on the usage of their resources. --- # 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.gpubase.network/how-it-works/user-and-provider-interaction.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.