DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to check a country's instability risk from the terminal with Worldmonitor

Look up a country's risk score from a shell command without opening a browser.

Authorization notice. Worldmonitor is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. The example command passes the API key on the command line, which can leak into shell history; store the key in an environment variable or config file instead.

Who it is forAn analyst or journalist who needs a quick country risk check while working in a terminal.

The problemOpening a dashboard and searching for one country slows down routine checks on conflict or instability.

The outcomeA risk readout for a country code printed in the terminal, using the same live data as the web dashboard.

What you need first

  • Node.js and npm for the CLI, terminal dashboard, or local dev server
  • A World Monitor API key from worldmonitor.app/pro for authenticated calls such as risk lookups and MCP tool calls
  • Ollama installed if you want the local AI option, since the README says it runs with no API keys
  • Git for cloning the repo in the self-hosting path

Steps

  1. Run npm install -g worldmonitor
  2. Get an API key at Worldmonitor.app/pro
  3. Run worldmonitor risk IR --api-key wm_xxx and replace IR with the country code you need and wm_xxx with your key
  4. Run npx worldmonitor tools to list the available MCP tools; this needs no key

Prompt for your agent

Using the worldmonitor CLI from the worldmonitor repo, run `worldmonitor risk <COUNTRY_CODE> --api-key <API_KEY>` and return the risk output as text. Verify that the output names the country code you requested before reporting it.

Caveat. The README's risk example uses a placeholder key format (wm_xxx), so confirm the exact command output against the current docs before scripting it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page