otinstaller · Frameworks

Install OpenOSINT on Linux in one command

OpenOSINT is an agent-style tool: you describe what you want in a REPL and it chooses and runs lookups on usernames, emails, and domains. It also exposes an MCP server so other agents can drive it.

OpenOSINT in three lines

pipx install otinstaller
ot install openosint
ot run openosint -- u:jane_doe

Runs OpenOSINT/OpenOSINT (MIT, ★ 1.6k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.

What OpenOSINT is for

Exploratory sessions where you do not know which tool to run first.
Wiring open-source lookups into an agent over MCP.

Typed inputs for OpenOSINT

otinstaller translates these prefixes into OpenOSINT's own flags. Anything else after -- is passed through unchanged, so every original flag still works.

u:: username · ot run openosint -- u:jane_doe
e:: email · ot run openosint -- e:jane@example.com
d:: domain · ot run openosint -- d:example.com

Run every installed tool that takes the same input at once: ot run --all u:jane_doe

Where the results go

Every run lands under ./results/openosint/<target>/ as a timestamped output file plus a .meta.json sidecar: the exact command, start and end time, exit code, and the SHA-256 of the output. Group runs with --case, compare the last two with ot diff openosint <target>, and pull indicators out with ot extract.

Before you run it

Needs a model provider configured; read the project's setup first.

Update, remove, inspect

ot info openosint      # inputs, flags, keys
ot example openosint   # sample output
ot update openosint    # move to the next tested version
ot remove openosint    # delete its virtualenv

Full reference for this tool: docs for openosint.

Pairs with

user-scanner

user-scanner takes a username or email and checks platforms that reveal whether an account exists.

SpiderFoot

SpiderFoot runs two hundred-odd modules against a domain, IP, email, or username and links what they return into one graph.

secator

secator wraps dozens of recon and scanning tools behind one command with a shared output format, and runs them as tasks, workflows, or full scans.

FAQ

OpenOSINT with otinstaller, answered

How do I install OpenOSINT on Kali or Ubuntu?

Install otinstaller once with pipx install otinstaller, run ot init, then ot install openosint. The tool lands in its own virtualenv under ~/.otinstaller/, pinned to a version that was tested on Ubuntu, so nothing touches your system Python. ot doctor flags a missing git or venv module.

Which inputs does OpenOSINT take through otinstaller?

u: (username), e: (email), d: (domain). otinstaller maps each prefix to OpenOSINT's own flag. Everything after -- that is not a typed input is passed through unchanged, so the original flags still work.

Where does otinstaller save OpenOSINT results?

Under ./results/openosint/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar with the exact command, timing, exit code, and SHA-256. Add --case <name> to group runs, and ot diff openosint <target> to compare the last two.

Does OpenOSINT need an API key or a login?

No key is required for the basic run. Optional keys, where the project supports them, go in ~/.otinstaller/.env and are passed only to tools that declare them.

Can I run OpenOSINT together with other tools?

Yes. ot run --all u:jane_doe runs every installed tool that accepts username input, in parallel, including OpenOSINT. Save the combination as a playbook to repeat it.