> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-graphql-api/products/billing/guides.md). # Guides This section contains step-by-step guides for the basic scenarios of using Billing, a product served by Navixy GraphQL API. Each guide covers one task about the billing of your own workspace, from the first query to the mutation or the list that completes it. ### Guides in this section * [Choosing a plan and subscribing](/docs/navixy-graphql-api/products/billing/guides/choosing-a-plan-and-subscribing.md): List the plans your workspace may take and what each one charges, subscribe your workspace, and confirm the subscription. * [Reading balance and statement](/docs/navixy-graphql-api/products/billing/guides/reading-balance-and-statement.md): Read your workspace's balance and list the payments, corrections, and invoice charges that changed it. * [Reading invoices](/docs/navixy-graphql-api/products/billing/guides/reading-invoices.md): List your workspace's invoices, read the lines of one invoice, match it to the balance statement, and find the invoices that are still unpaid. * [Reading usage submissions](/docs/navixy-graphql-api/products/billing/guides/reading-usage-submissions.md): List the usage that Navixy products reported for your workspace, read what each submission says, and follow one metric month by month. --- # 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://navixy.com/docs/navixy-graphql-api/products/billing/guides.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.