> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/codashop-and-distribution/overview.md). # Overview Introduction to Codashop and Coda's Distribution network As a leading marketplace for digital content, Coda offers publishers an easy alternative to sell in-game currency and top-ups on Codashop and our Distribution network. Through our seamless integration, our partners are able to effortlessly distribute games, bundles, virtual items, and in-game currencies across the 60+ countries where we operate. Partners can broaden their game's reach, boost revenue, and tap into Coda's distinct user base for increased organic discoverability.\ \ This document provides a comprehensive overview of the entire process, including the APIs utilized by Codashop and Distribution partners for the verification and validation of game account information. It also covers retrieving server lists and efficiently processing top-up or recharge requests for the top-up products available on the Codashop and Distributor websites. Let's dive into the details!\ \ [Click here](https://bit.ly/4aNqHRf) to start selling on Codashop and Coda's Distributor 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.coda.co/codashop-and-distribution/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.