> For the complete documentation index, see [llms.txt](https://osintverse.gitbook.io/otinstaller/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://osintverse.gitbook.io/otinstaller/readme.md).

# Introduction

![OTinstaller](https://77012809-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyOEyP5jMop7g1dqmLWML%2Fuploads%2Fgit-blob-9404ddd46f351ab140298158be0c90399802fa5f%2Fotinstaller-banner.png?alt=media)

OTinstaller is a command line tool manager for Linux. It installs, runs, updates and removes open-source command line tools by name, each in its own virtualenv, through one standard command interface. `ot` is a short alias for `otinstaller`.

You pick a tool by name. OTinstaller installs it, runs it against a target, and saves the output under `./results/` with a metadata sidecar file. You do not learn a different install method for every tool.

## Watch the launch video

{% embed url="<https://www.youtube.com/watch?v=_AfUGMFRaKA>" %}
90 seconds: install, typed inputs, auto-detect, parallel runs, results and more.
{% endembed %}

![Installing and running a tool](https://77012809-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyOEyP5jMop7g1dqmLWML%2Fuploads%2Fgit-blob-ae65a086a59b791161f52a269089747803f73fdd%2Fotinstaller-demo.png?alt=media)

This site covers 47 tools. The tool list focuses on open-source intelligence (OSINT) tooling and is rebuilt from the OTinstaller registry whenever the registry changes.

## Contents

* [Getting started](/otinstaller/getting-started.md): install OTinstaller, run `otinstaller init`, and run your first tool.
* Guides: [typed inputs](/otinstaller/guides/typed-inputs.md), the [command reference](/otinstaller/guides/commands.md), [results and resume](/otinstaller/guides/results.md), [API keys](/otinstaller/guides/api-keys.md) and [responsible use](/otinstaller/guides/responsible-use.md).
* [FAQ](/otinstaller/faq.md): Windows and macOS, root, data, uninstalling, legality.
* [Changelog](/otinstaller/changelog.md): what changed in each release.
* Tools: one page per tool, grouped by what it searches, with source, install method, credentials, input flags, example output, and run commands.

## Links

* Source code: [github.com/OSINTVerseHQ/OTinstaller](https://github.com/OSINTVerseHQ/OTinstaller)
* Package: [pypi.org/project/otinstaller](https://pypi.org/project/otinstaller/)
* Report a bug or suggest a tool: [issues](https://github.com/OSINTVerseHQ/OTinstaller/issues)

## Team

* **Sushant Koul**, builder: [GitHub](https://github.com/Sushant-69x) · [LinkedIn](https://www.linkedin.com/in/sushantkoul07)
* **Dheeraj Yadav**: [GitHub](https://github.com/dheerajydv19) · [X](https://x.com/dheerajydv19)

Built by [OSINTverse](https://osintverse.com/).


---

# 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://osintverse.gitbook.io/otinstaller/readme.md?ask=<question>&goal=<user_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.
