Skip to main content

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.
Test only POST /api/orders. Skip everything else in the collection.
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.
Run the scenarios tagged checkout.
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?

NeedBest option
One-time route investigationChat instruction
Recurring subset of testsTags
Exact route and exact assertionsSingle scenario

Next steps

API testing scenarios

Learn the API scenario model.

Run a single scenario

Execute one saved test.

Run tag-filtered scenarios

Run a reusable subset.

API governance

Keep endpoint coverage organized.