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

# How do I scope a scan to one route?

> Keep Qodex focused on one route by using a clear chat instruction, tags, or a pre-authored scenario.

# How do I scope a scan to one route?

Use the lightest control that matches how precise you need the run to be.

For one-off work, tell Qodex the exact route in chat. For repeatable subsets, use tags. For strict control, run one pre-authored scenario.

## Option 1: Tell Qodex in chat

Use this while Qodex is exploring or authoring tests.

```text theme={null}
Test only POST /api/orders. Skip everything else in the collection.
```

```text theme={null}
Run the security skill against /api/v1/users/{id}. Focus on BOLA.
```

This tells the coordinator and sub-agents to keep the run focused.

## Option 2: Use tags

Use tags when the same scope should run again.

```text theme={null}
Run the scenarios tagged checkout.
```

```bash theme={null}
qodex run --tag checkout
```

Tags work well for scopes like `smoke`, `checkout`, `security`, `critical`, or `auth`.

## Option 3: Run one scenario

Use this when you know exactly what should execute.

A single pre-authored scenario gives the tightest scope: one route, one test shape, and no extra exploration.

## Which option should I choose?

| Need                             | Best option      |
| -------------------------------- | ---------------- |
| One-time route investigation     | Chat instruction |
| Recurring subset of tests        | Tags             |
| Exact route and exact assertions | Single scenario  |

## Next steps

<CardGroup cols={2}>
  <Card title="API testing scenarios" icon="plug" href="/api-testing-scenarios">
    Learn the API scenario model.
  </Card>

  <Card title="Run a single scenario" icon="play" href="/run-tests-single-scenario">
    Execute one saved test.
  </Card>

  <Card title="Run tag-filtered scenarios" icon="tag" href="/run-tests-tag-filtered">
    Run a reusable subset.
  </Card>

  <Card title="API governance" icon="map" href="/api-testing-governance">
    Keep endpoint coverage organized.
  </Card>
</CardGroup>