> For the complete documentation index, see [llms.txt](https://docs.jamaibase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jamaibase.com/developer-reference/openapi-documentation.md). # OpenAPI Documentation Welcome to the JamAI Base API documentation! This is your fast track to integrating powerful, secure AI solutions into any application using a clean RESTful design. JamAI Base lets you treat our expert-created AI components—Generative Tables—as simple, ready-to-use AI microservices. By interacting with a single, well-defined API endpoint, your developers can completely bypass the underlying complexity and 'plumbing' of Large Language Models (LLMs). This extensible architecture ensures a seamless developer handoff, enabling your team to focus on rapid UI development and integration, not complex AI logic. The platform is engineered for enterprise control. Every API interaction is managed by built-in Concurrency and Rate Control features, giving you the power to set departmental throttling, manage API keys, and secure your deployment. This ensures predictable performance and controlled resource allocation across your entire organization. Our RESTful API is organized around resource-oriented URLs, which directly correspond to the sections in our comprehensive [API Reference](https://jamaibase.readme.io/reference). When you're ready to start building, head to the Making your first API request guide and discover how easy, fast, and controlled AI integration can be. --- # 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.jamaibase.com/developer-reference/openapi-documentation.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.