Quickstart

Go from zero to a finished automatic pentest with an active Rules of Engagement and findings, from the CLI, the Python SDK or the REST API.

What you’ll build

This quickstart launches an automatic web pentest against https://example.com: you create the pentest, activate a Rules of Engagement that covers the target, assign the default agents, stream the run, and read back the vulnerabilities.

Without an active RoE the orchestrator will not start (no_active_roe). That step is required in every client.

Before you start you need an API token. Generate one in the dashboard at aleex-rank.ai under Settings > API Tokens. Tokens look like rk_live_... (production) or rk_test_... (sandbox) and are sent in the X-API-Key header. For the full picture, see Authentication & API tokens.

Guided vs automatic

A pentest runs in one of two modes:

  • automatic — the platform assigns default agents to every phase and chains the phases end to end with no further input. Findings are processed in-stream. This is what the quickstart uses.
  • guided — you pick the agents for each phase and advance one phase at a time, giving you full control.

Both modes work the same across the CLI, SDK and API. See Core concepts for the mental model behind pentests, RoE, phases and agents.

Run your first pentest

In automatic mode the backend processes vulnerabilities in-stream and marks the pentest completed for you. In guided mode you advance phase by phase and finish the pentest yourself once findings are processed. Either way, an active RoE is required before the first phase starts.

Next steps