# Searching for Data

Once documents are uploaded to Aerofiler, you will typically want to capture key metadata such as counterparty, title, start date and governing law. This example steps through a workflow for capturing governing law in your repository. You can begin with a keyword search of the documents that you just uploaded:

<figure><img src="/files/kj4r66qyAlp2n9FLdJkw" alt=""><figcaption></figcaption></figure>

This will return a screen showing the highlighted search term, along with the surrounding text:

<figure><img src="/files/YB95eejGV3fmRYCc0PuS" alt=""><figcaption></figcaption></figure>

Often, the extracted text will be enough to find the data you need. If you need to view the full contract, you can click on “Show Preview”:

<figure><img src="/files/tBArEkztuShz7zHT7cCW" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/yz4QwimIGhw8BoSAOys8" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
As you move from row to row in Preview mode, the document on the right will automatically update.
{% endhint %}


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://userguidesgitbook.aerofiler.com.au/documents/searching-for-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.