# Quickstart

Set up your first scan and review your first finding. This page is the one-screen overview. Every product has its own deeper quickstart linked below.

## What You'll Set Up

1. **Your account**: sign in at [app.escape.tech](<https://app.escape.tech/login>) with your work email.
2. **Your first asset**: point Escape at a domain, an API spec (OpenAPI, GraphQL SDL, Postman collection), or a cloud account.
3. **Your first scan**: pick the product that matches the asset (ASM for inventory, DAST for testing, AI Pentesting for validation).
4. **Your first finding**: walk the results, open one issue, and ship the first fix from your IDE.

## Pick Your Starting Point

- **Discover first (recommended for a new estate)**: start with [ASM Quickstart](</documentation/asm/quickstart/>). Inventory-then-test is the cleanest flow.
- **Test an API you already know**: go straight to [DAST Quickstart](</documentation/dast/quickstart/>) with your OpenAPI spec or GraphQL endpoint.
- **Hunt the hard stuff**: if you want agent-driven exploit validation on top of DAST, start with [AI Pentesting Quickstart](</documentation/ai-pentesting/quickstart/>).

## After the First Scan

- Hook findings into your IDE via the [MCP Server](<https://docs.escape.tech/documentation/automate/mcp-server/index.md>) so engineers see them next to the code.
- Wire Escape into your CI/CD so every merge runs a scan. See [CI/CD Integrations](</documentation/automate/ci-cd/>).
- Route new findings to the right team using [Workflows](</documentation/automate/workflows/>).

If something's not working, drop a line to [support@escape.tech](<mailto:support@escape.tech>).