npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@qname/cli

v0.1.4

Published

Agent-native CLI for QName.AI WHOIS and traffic lookup APIs

Readme

@qname/cli

Agent-native CLI for QName.AI WHOIS and traffic lookup APIs.

The CLI is the recommended client for QName API keys. It intentionally exposes only the approved WHOIS scopes: domain.query.whois.single and domain.query.whois.batch, plus the traffic scope domain.traffic.lookup. Those scopes cover WHOIS/domain lookup through GET /api/whois/{domain} or POST /api/whois/batch, and traffic lookup through GET /api/domain-traffic?domain=example.com. Calls are capped by the API types, per-request domain quota, and daily request quota approved for your key. Realtime streams, registrar purchase actions, and domain rating data are outside the CLI command surface.

Install

npm install -g @qname/cli

Install the Agent Skill:

npx skills add QNameAI/qname-cli -y -g

Configure credentials once:

qname-cli init --api-key <approved-key>

Run a lookup:

qname-cli whois qname.ai --pretty
qname-cli whois qname.ai example.com --pretty
qname-cli traffic qname.ai --pretty

For local development inside this repository:

node bin/qname-cli.mjs --help

Request API Access

  1. Open https://qname.ai/settings/apikeys.
  2. Submit an API key request for qname-cli, choose the single-domain WHOIS, batch WHOIS, and traffic lookup API types you need, and choose the domain and daily request quota tiers.
  3. Wait for admin approval.
  4. Reveal the approved key once and initialize the CLI.
qname-cli init --api-key qname_xxx

You can also use environment variables in CI or Agent runs:

export QNAME_API_KEY="qname_xxx"
export QNAME_BASE_URL="https://qname.ai"

Commands

qname-cli whois qname.ai --pretty
qname-cli whois qname.ai example.com --pretty
qname-cli whois qname.ai --format text
qname-cli traffic qname.ai --pretty
qname-cli traffic qname.ai --format text
qname-cli config get --pretty
qname-cli config set --api-key qname_xxx
qname-cli doctor
qname-cli request-key
qname-cli skill --path

qname-cli defaults to JSON output so humans and AI Agents can parse results without screen scraping.

Agent Usage

Install the Agent Skill globally:

npx skills add QNameAI/qname-cli -y -g

Agent instructions are also bundled inside the npm package at:

qname-cli skill --path

Agents should prefer qname-cli whois <domain...> --pretty for domain availability evidence and qname-cli traffic <domain> --pretty for traffic analytics over direct curl unless they are debugging the API contract itself. They must stay within the approved API types, per-request domain quota, and daily request quota for the configured key.