> For the complete documentation index, see [llms.txt](https://docs.innova-drilling.com/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/8.0-menu-ribbons/8.3-tools/8.3.4-search.md).
# 8.3.4 - Search
## 8.3.4.1 - Asset Search
Figure 177: Asset Search
The Asset Search option allows the user to search all inventories in the database tree for a specific drill string component. The user should enter the serial number of the component and select its type in the **Asset Details** section and then click on **Search**. The user can also limit the search to a specific date range by checking the checkbox in the **Date Range** section before clicking Search.
Results of the search are shown in the three Data sections. The Well Data section will display wells that contain the selected asset in their Inventory. The Run Data section will show wells where the asset has been used in the Drill String Editor as part of a BHA. The Summary Data section displays a summary of the above two sections.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.innova-drilling.com/introduction/innova-engineering-manual/well-seeker-x-manual/8.0-menu-ribbons/8.3-tools/8.3.4-search.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 `automate deployments from our CI pipeline` 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.
