# Quickstart The core Virusis experience is built around submitting a sample and following a structured result view from start to finish. ## 1. Choose an input type Virusis supports three primary input types in one guided flow: * file * URL * IP Each input is presented through the same product experience so teams do not need to switch between separate tools just to begin analysis. ## 2. Complete access and verification Depending on how you entered the product, Virusis may continue with: * a signed-in workspace session * a guided trial session * a shared result link Verification steps may appear before analysis begins, especially in trial or public-facing flows. ## 3. The platform prepares the submission Before a full analysis starts, Virusis may perform lightweight preparation steps so the experience stays consistent and efficient. In practical terms, this helps: * avoid unnecessary re-processing when a result is already available * keep the same sample easy to recognize across the workflow * prepare the item for a clean result experience ## 4. Analysis begins Once the submission is accepted, Virusis begins analysis and starts assembling the report view. Depending on the input and workflow, the result may appear progressively instead of all at once. ## 5. Review the result screen The result screen brings together: * sample identity and summary details * score cards and overall risk signals * detection and analysis sections * threat context when available * file insights when available * sharing and export tools For more detail, continue to [Result Screen and Reports](/malware-analysis/result-screen-and-reports.md). --- # 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/getting-started/quickstart.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.