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

zambo-agent-cli

v1.0.10

Published

Zambo agent CLI: run 153 AI tools from the command line for crypto, audits, research. Every call returns a verifiable execution receipt (AER-1, IETF Internet-Draft draft-zambo-aer1-26). Free: 20 free calls per day, no account. zambo.dev

Readme

zambo-agent-cli — Zambo, the verifiable work layer for AI, on your command line

AER-1, the agent execution receipt standard: zambo.dev/aer-1 | Add Zambo to your AI: zambo.dev/add

Zambo is the verifiable work layer for AI. Receipt format: AER-1, IETF Internet-Draft draft-zambo-aer1-26.

The problem: AI models talk. Getting things done — checking a live price, auditing a site, running research, pulling data — means wiring up APIs, keys, and glue code for every single task.

The fix: one command. Describe the job, get it done, get a receipt.

npx zambo-agent-cli "what's the price of BTC right now?"
BTC is currently priced at $81,270.00 ...

🔗 receipt f410acad-e438-48c3-acae-f37871a764b1 · audit: https://zambo.dev/run/f410acad-e438-48c3-acae-f37871a764b1
   verify: zambo verify f410acad-e438-48c3-acae-f37871a764b1

No account. No API key. No config. Free: 20 free calls per day.

Quickstart

# One-command: describe any goal
npx zambo-agent-cli "audit example.com for AI discoverability"

# Call a specific tool directly
zambo call live_price '{"symbol":"BTC"}'
zambo call ghost_audit_site '{"url":"https://example.com"}'

# Search the 153 tool catalog
zambo search 'generate QR code'

# List exposed tools
zambo list

# Verify any receipt
zambo verify f410acad-e438-48c3-acae-f37871a764b1

# Teach your agents about Zambo (writes to AGENTS.md / CLAUDE.md / .muserules)
zambo init

Install it globally for the short zambo command:

npm install -g zambo-agent-cli

Or use it from Node:

const zambo = require('zambo-agent-cli');

const { text, receipt } = await zambo.callTool('live_price', { symbol: 'BTC' });
console.log(text, receipt.id);

const v = await zambo.verifyReceipt(receipt.id);
console.log(v.verified, v.tool, v.sha256);

What Zambo is

Zambo is the verifiable work layer for AI: an MCP server with 153 native tools — live crypto prices, site audits, web research, content tools, lead and data tools, multi-step agent jobs — behind one plain JSON-RPC endpoint (https://zambo.dev/mcp). This package is a thin, zero-dependency client for that endpoint.

Don't know which tool fits? Skip the catalog — zambo "<goal>" routes through zambo_universal, which picks the right tools for the job. Pass --session <id> to keep a trail across calls.

Receipts: verifiable proof of execution

Every call returns an AI agent execution receipt — a verifiable receipt: a UUID, a timestamp, and a sha256 of the result. It proves the call executed and binds the result bytes — so anyone can check that a claimed result is exactly what Zambo produced.

A real receipt from a live call:

  • Tool: live_price → BTC $86,175.00 USD (▲ 2.84% / 24h)
  • Receipt ID: a71f243d-39e8-4eda-9c4b-2a31ae063ba9
  • Time: 2026-09-22T08:49:53Z
  • Output hash: sha256:ae5d2c1729fec0515dc05ea291d75f02860ce533bd3e87909cda899d93f4103f
  • Inspect it yourself: https://zambo.dev/run/a71f243d-39e8-4eda-9c4b-2a31ae063ba9

Honest scope: a receipt proves execution integrity, not correctness. It binds the result; it doesn't judge it.

Check any receipt in your browser or on the command line:

zambo verify <receipt-uuid>     # confirms zambo.dev serves the receipt,
                               # and shows tool, sha256, timestamp, audit URL

Receipt pages are real web pages with structured data (JSON-LD), Open Graph tags, and canonical URLs — shareable, linkable, citable.

Free tier, honestly

  • Free: 20 free calls per day. No account, no API key, no card.
  • Paid: a $0.99 Day Pass or $29/month Pass for heavier use, via zambo.dev.

No fake limits, no "contact sales to see a price."

Commands

| Command | What it does | |---|---| | zambo "<goal>" [--session <id>] | Do the thing. Routes via zambo_universal. | | zambo call <tool> '<json>' | Call one tool directly. | | zambo search '<query>' | Search the 153 tool catalog. | | zambo list | List exposed tools with one-line descriptions. | | zambo verify <receipt-uuid> | Verify a receipt on zambo.dev. | | zambo init [--root <dir>] [--file <name>] [--force] | Write the Zambo section into your project's agent instruction file. |

Requirements & troubleshooting

  • Node.js 18 or newer. Zero runtime dependencies.
  • The upstream endpoint occasionally resets connections; the client retries transient transport failures automatically (up to 4 attempts). A received JSON-RPC error is never retried — it's shown to you as-is.
  • Timeouts: 60s per attempt.

License

MIT — see LICENSE. Created by Brennan Zambo — https://zambo.dev/founder

Learn more