# Usage Limits Virusis may apply usage controls to keep the product stable, fair, and predictable across different input types and customer environments. ## What public documentation should communicate * exact thresholds can vary by environment, plan, or deployment * processing time may vary with input size, complexity, and analysis depth * not every result appears instantly, especially during heavier analysis flows * public docs should explain expectations without disclosing internal operational controls ## Best practice for external wording Instead of publishing hidden implementation details, public help pages should say things like: * "processing speed may vary by submission type" * "availability and throughput can differ by workspace or package" * "contact your Virusis point of contact for enabled integration capabilities" --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.virusis.com/api-reference/rate-limits.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.