> For the complete documentation index, see [llms.txt](https://docs.violet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violet.io/help/violet-sla.md). # Violet SLA At Violet, we are committed to providing a reliable and high-performing API service to power your applications. ## Service Availability We work hard to ensure 99.9% uptime for our API service on a monthly basis. This means that you can expect our API to be available and responsive at least 99.9% of the time, excluding planned maintenance windows. ## Historical Performance We take pride in consistently delivering exceptional uptime performance for our API service. Our historical uptime records demonstrate our commitment to reliability and availability: 2023 Uptime: 99.99996% 2024 Year-to-Date Uptime: 99.999995% These uptime figures include any subsystem downtime, demonstrating that our API service remains highly available and responsive to meet your application's needs. --- # 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.violet.io/help/violet-sla.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.