> For the complete documentation index, see [llms.txt](https://griffin-ai.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://griffin-ai.gitbook.io/knowledge-base/network-participants-and-contributors/client-providers-cps.md). # Client Providers (CPs) CPs are apps that provide accessible user interfaces, so their users don’t have to trigger API endpoints. Those apps can be both, either Web2 applications or Web3 / DApps. CPs play an important role in making Griffin AI accessible to a broad user base. Next to enabling their application and their user base to access AI Services, they may extend their offering to include account management and payment collection. Client Provider might offer their users complimentary access to their services to increase the value proposition of their solution – or they might choose to charge their clients fees. Moreover, CPs may choose to contribute to the maintenance and stability of the Griffin AI network by operating a Node, otherwise they can integrate utilizing the Griffin SDK. --- # 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://griffin-ai.gitbook.io/knowledge-base/network-participants-and-contributors/client-providers-cps.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.