> For the complete documentation index, see [llms.txt](https://developers.madkudu.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.madkudu.com/getting-started/your-api-usage.md). # Your API Usage Monitor your API usage ## How to monitor your API usage You can track how many API calls your team is making directly in the[ MadKudu Admin console ](https://admin.madkudu.com/) > **Settings** > **API Usage** You can track the usage by API key and endpoints > 💡 **Note:** API calls made via **MCP tools** (e.g. AI agents, workflows) also count toward your usage. ## What’s included in my plan If your workspace has the **API Access add-on**, it includes a monthly allowance of API calls. > Need more volume?\ > → Reach out to your CSM to discuss increasing your limit or upgrading your plan. --- # 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://developers.madkudu.com/getting-started/your-api-usage.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.