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

openrouter-key-check

v0.1.0

Published

CLI to check OpenRouter API key usage, limits, and credits.

Readme

openrouter-key-check

A tiny CLI to check an OpenRouter API key: its usage (total / daily / weekly / monthly), spend limits, BYOK usage, and — for management keys — account credits.

Runs on Node (>=18) or Bun. The published CLI is a bundled, Node-compatible JS file, so both npx and bunx work.

Usage

No install needed:

npx openrouter-key-check
# or
bunx openrouter-key-check

By default it prompts for a key. You can also pass one explicitly or read it from the environment:

# read OPENROUTER_API_KEY from the environment
OPENROUTER_API_KEY=sk-or-... bunx openrouter-key-check --env

# pass the key directly
npx openrouter-key-check --key sk-or-...
npx openrouter-key-check --key=sk-or-...

Options

| Flag | Description | | -------------- | ------------------------------------------------- | | --env | Use OPENROUTER_API_KEY from the environment. | | --key <key> | Use the provided API key. | | --help, -h | Show help. |

If neither --env nor --key is given, you'll be prompted for a key.

Output

Prints the key label, usage and limit figures (in USD), BYOK usage, expiry, and flags such as whether it's a free-tier / management / provisioning key. For management keys it additionally fetches account credits and total usage.

Development

bun run check --help   # run the TypeScript source directly
bun run build          # bundle to dist/ (Node target)

License

MIT