> 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/changelog/legacy-changelog/detailed-fixed-price-points-moved-to-readme.md). # Detailed Fixed Price Points Moved to Readme We are excited to announce an important update regarding the Detailed Fixed Price Points feature in our API documentation. Previously, the fixed price points for various payment channels were available in a Google sheet. However, as part of our ongoing efforts to enhance accessibility and convenience, we have now moved this valuable information to our API documentation: [Detail Fixed Price Points](broken://pages/L6rF0lkG8KyR8M6q7LhL) ![](https://files.readme.io/f315dc2-image.png) With this update, you can now find all the specific fixed price points for payment channels, including Telkomsel, Unitel, AIS, TrueMoney cash card, Truemove H, One-2-Call Cash Card, Telemor, and GASH Gift Card, directly within the online API documentation. As always, our team is committed to providing a seamless and efficient integration experience. If you have any questions or need further assistance with this update, please don't hesitate to reach out to our support team. Thank you for your continued support and collaboration. We look forward to enhancing your payment experience with our API. --- # 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/changelog/legacy-changelog/detailed-fixed-price-points-moved-to-readme.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.