> For the complete documentation index, see [llms.txt](https://docs.inabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inabit.com/introduction.md). # Introduction Read our documentation and get up to speed on how to access our API capabilities. ### Documentation Overview Welcome to the inabit Developer Portal! Here, you'll find everything you need to start using our API and seamlessly integrate it into your existing solutions. Our comprehensive API reference, code libraries, and tutorials are designed to help you get up and running quickly while also enabling you to build advanced features with ease. *** ### Explore & Learn Discover inabit’s platform, features, and cutting-edge security technology. Whether you're setting up test or production environments, these guides will walk you through the essentials to ensure a smooth start. When you're ready, head over to the Quick Start section to make your first request. ***
Quick Start
Learn the basics and send your first request.		https://docs.inabit.com/api-reference/develop-with-inabit-api/getting-started/authenticationquickstart (3).png
API Reference
Explore all API endpoints and details.		https://docs.inabit.com/api-reference/api (1).png

Use Cases

See how others utilize inabit's API.

Use Casesusecases (1).png
{% hint style="info" %} #### Need Help? If you have questions or suggestions, our support team is here for you: **.** {% endhint %} --- # 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.inabit.com/introduction.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.