> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/trades/find-trades.md).
# Find Trades
The Trades module contains a list over all Trades in your system. Here you can search for, filter and sort all your trades.
### Sorting and filtering
There are several [sorting and filtering](/release-8.31/voyage-management-system/step-by-step-guides/sorting-and-filtering-lists.md) options available for you to narrow down what you see in the list view, as well as the ability to toggle which columns are displayed (with the [customised columns](/release-8.31/voyage-management-system/step-by-step-guides/customising-list-columns.md) setup).
For sorting, look for the *arrow* to the right of the column headers or the blue  icon above and to the right of the list. For filtering, you can use the *quick filters* provided above the Trades list. Which include filtering on the year, which trades and/or routes, and disabled trades.
#### Trade Quick Filter
The Trade quick filter consists of two filters. The top filter filters on specific trades and the bottom one filters trades based on the selected route(s), see the first tab below. The available options in the top filter will change based on the selected route(s). Such that the top filter will only show trades that are part of the selected route, see the second tab below.
{% tabs %}
{% tab title="Default Trade Filter" %}
{% endtab %}
{% tab title="Route Selected" %}
The trade options are based on the selected route
{% endtab %}
{% endtabs %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/trades/find-trades.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
