Auto Archiver
1.2.9Automatically archive web content from various sources.
- Verified 24 Sept 2026
- pip 1.2.9
- MIT
- 1.1k stars
- Optional API keys
- Dual-use
- Needs setup
Install and run
otlite install auto-archiverInstalls
auto-archiver==1.2.9into its own virtualenv. otlite lists what it will install and asks before it starts.otlite run auto-archiver -- url:https://example.comType your own value to rewrite the commands. It stays in this page: nothing is sent or saved.
auto-archiverreceivesauto-archiver --url https://example.com
No otlite yet? Install it in one line
curl -fsSL https://get.otinstaller.com/otlite | shLinux and macOS, no Docker. It uses your Python and pipx when both are there, and otherwise brings its own Python. About otlite · otlite docs
Before you run it
- Dual-use. otlite prints this before installing it: You are solely responsible for how you use these tools and for complying with all applicable laws. Use them only on targets you are authorized to investigate.
- Needs a login or API key. Set it up before the first lookup; batch runs skip it unless you pass
--include-credentialed. - Needs Python older than 3.13. Its dependency pdqhash has no wheel for 3.13 or newer and needs a C++ compiler. otlite checks your Python before installing and says which version to use;
otlite doctorlists the tools your Python can't run.
What it takes
Typed inputs after -- become Auto Archiver's own arguments. Anything else after -- passes through unchanged, so every option of the tool still works.
| Input | With otlite | auto-archiver receives |
|---|---|---|
URLurl: | otlite run auto-archiver -- url:https://example.com | auto-archiver --url https://example.com |
API keys
All optional: Auto Archiver runs without them and uses each one you set. otlite keys set asks for the value without showing it and saves it in ~/.otlite/.env, readable only by you. Each tool receives only the keys it declares, and values never appear in logs or results.
| Key | Needed | Set it |
|---|---|---|
GOOGLE_API_KEY | Optional | otlite keys set GOOGLE_API_KEY |
GOOGLE_CREDENTIALS | Optional | otlite keys set GOOGLE_CREDENTIALS |
AWS_ACCESS_KEY_ID | Optional | otlite keys set AWS_ACCESS_KEY_ID |
AWS_SECRET_ACCESS_KEY | Optional | otlite keys set AWS_SECRET_ACCESS_KEY |
What a run leaves
Every run is saved under results/ where you run otlite (or --output, or OTLITE_RESULTS_DIR): what the tool printed, a sidecar with how it ran, and an envelope.
results/auto-archiver/https_example.com/<time>_auto-archiver_https_example.com_<run id>.txtresults/auto-archiver/https_example.com/<time>_auto-archiver_https_example.com_<run id>.meta.jsonresults/auto-archiver/https_example.com/<time>_auto-archiver_https_example.com_<run id>.envelope.json
{
"envelope": 1,
"tool": "auto-archiver@1.2.9",
"runtime": "otlite",
"input": { "target": "https://example.com" },
"case": null,
"started_at": "…", "ended_at": "…", "duration_ms": …,
"exit_code": 0,
"status": "complete",
"entities": [{ "type": "url", "value": "…" }, …],
"warnings": [],
"output": { "path": "results/auto-archiver/https_example.com/<time>_auto-archiver_https_example.com_<run id>.txt", "sha256": "…", "bytes": … }
}otlite results --tool auto-archiverotlite extract auto-archiverotlite diff auto-archiver https://example.comList the saved runs, pull out every indicator, or compare the two latest runs against the same target.
With other tools
Batch runs skip it: needs API keys or setup; pass --include-credentialed.