> 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/legacy-documentation/manuals/well-seeker-pro-1/appendix-a-software-licensing.md).
# Appendix A – Software Licensing
Well Seeker PRO is by default shipped with a 2 day trial license which enables all software features.
After this period has expired a full license must be purchased. Each software license is issued for a specific PC and to do this a computer code must be provided to Innova so the license can be issued. If your trial period has not expired open Innova engineering and click on the **help menu-> License info** option to display the license info dialog.
Figure 344: License Details
If your trial copy Well Seeker PRO has expired or your license is invalid the computer code will be displayed on the start-up screen. The code can be copied to the clipboard by highlighting the code and pressing Ctrl + C. This can then be pasted into a text document or email.
Send the computer code string to and you will receive your license in the form of a **LICENSE.txt** file. Place this file in the same directory as WellSeeker.exe. usually **C:\Program Files (x86)\Innova Drilling & Intervention\Well Seeker**. And run the software.
**License Deactivation**
If you wish to deactivate a license (to move it to another machine), click on the deactivate license button in the license info dialog. Note the deactivation code and send a copy along with the computer code of the new PC to . Once the deactivation code has been verified a license for the new machine will be issued.
---
# 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/legacy-documentation/manuals/well-seeker-pro-1/appendix-a-software-licensing.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.
