> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enokilabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> From zero to your first assessment in a few minutes, with Claude Code.

This walks you from nothing to a security assessment on one of your agents,
driving Enoki from **Claude Code** over MCP. Using Cursor or another client
instead? The steps are the same — see [Connect your agent](/connect-your-agent)
for its config.

<Steps>
  <Step title="Mint an API key">
    In [app.enokilabs.ai](https://app.enokilabs.ai) → **Settings → API Keys**,
    create a key with the **`read`** and **`write`** scopes (add **`test:run`** to
    trigger assessments). Copy it — it's shown once. Details:
    [API keys & scopes](/api-keys).
  </Step>

  <Step title="Connect Claude Code">
    Add the Enoki MCP server, with your key as a Bearer token:

    ```bash theme={null}
    claude mcp add --scope user --transport http enoki \
      https://mcp.enokilabs.ai/mcp \
      --header "Authorization: Bearer egk_your_key_here"
    ```

    Run `/mcp` in a session to confirm the Enoki tools are connected.
  </Step>

  <Step title="Register your target">
    Ask your agent to register your endpoint as a target. It should call
    **`get_setup_guide`** for the config reference, then **`create_target`** —
    which fires one live probe and only saves the target if it succeeds. On a
    failure it returns a categorized reason (`unreachable` / `auth_failed` /
    `parse_error`) so you can adjust and retry.
  </Step>

  <Step title="Run an assessment">
    With the target's `model_id`, call **`trigger_assessment`** to start a run,
    then poll **`get_assessment_status`** until it's complete. See
    [what we test for](/what-we-test).
  </Step>

  <Step title="Read and fix findings">
    Pull results with **`list_findings`** and **`get_finding`** (which includes the
    repro). Once you've fixed one, **`close_finding`** it and run
    **`validate_fix`** to re-run its attacks and confirm the fix holds.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="MCP tool reference" href="/mcp-tools">
    Every tool, grouped by area, with the scope each needs.
  </Card>

  <Card title="REST API" href="/api-reference">
    Drive the same flow from CI/CD or your own code.
  </Card>
</CardGroup>