confidential // case file // everjust field intelligence // do not redistribute
get it — cli & npm

Company research from the command line.

The company-dossier npm package is a company research CLI and library. Point it at a name or a domain and it writes a complete, sourced dossier — the same nine sections you get everywhere else — straight to disk, plus a machine-readable dossier.json. Free, public sources only, scriptable to the core.

View on GitHub See a sample file
OSINT cli, public information only — nothing you couldn't find yourself, just gathered for you.
quick start

One command to a finished file

No account, no config. Run it with npx, or install it globally if you'll reach for it often.

as a library

import { buildDossier }

Need the data, not the terminal output? The package exports buildDossier so you can fold company research into your own tools, dashboards or agents.

buildDossier(nameOrDomain) resolves to a structured object — the same nine sections, each with its sourced claims — so you can render it, store it, or hand it to an LLM as context. The CLI is just a thin wrapper around this call.

the output

A markdown folder + dossier.json

Every run produces two things: a folder of nine readable markdown sections, and one dossier.json that holds the whole file in a machine-readable shape.

The markdown is for humans — open it in your editor, skim it, paste a section into a brief. The dossier.json is for everything else: diff two runs over time, feed it to a model, or load it into a database. Same nine sections, every claim pointed back to its public source.

in the wild

Use it in CI, agents & scripts

Because it's a single command that returns structured data, the company data npm package slots into whatever you've already built.

  • CI / scheduled jobs — refresh a dossier on a cron and commit the diff.
  • AI agents — call the CLI or buildDossier as a tool and let the agent reason over the result. It's what powers the ChatGPT and Claude integrations.
  • Batch scripts — pipe a list of domains in, get one sourced file per company out.
configuration

Optional API keys

The CLI runs with zero configuration. Optional environment variables only widen the public sources it can reach — they never unlock anything private.

good to know

Questions, answered

Q. Do I need to install it?

No. npx company-dossier <company-or-domain> runs it without a global install. If you'll use it daily, npm i -g company-dossier puts it on your PATH.

Q. Is the output the same as the web app?

Same nine-section file. The web app renders it for the screen; the CLI writes it to disk as markdown plus a dossier.json.

Q. Where does the data come from?

Public sources only — job boards, filings, news and the open web. No private data, no login bypass. Optional API keys just widen the sweep.

View on GitHub
Open me

Run it on a real company.

npx company-dossier · sourced, in your terminal.

Open a dossier See a sample file