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

@zauthx402/openclaw-x402

v0.1.6

Published

x402 payment protocol integration for OpenClaw agents

Readme

Installation

openclaw plugins install @zauthx402/openclaw-x402

Configuration

Add to your ~/.openclaw/openclaw.json:

{
  "plugins": {
    "entries": {
      "openclaw-x402": {
        "enabled": true,
        "config": {
          "evmPrivateKey": "0x...",
          "svmPrivateKey": "base58...",
          "maxPaymentUSDC": "0.50",
          "defaultNetwork": "base"
        }
      }
    }
  }
}

Config Options

| Option | Type | Description | | ------------------ | ------ | ------------------------------------------------------------------------- | | evmPrivateKey | string | Private key for Base/EVM payments (hex format) | | svmPrivateKey | string | Private key for Solana payments (base58 format) | | maxPaymentUSDC | string | Maximum payment per request (e.g., "0.50") | | defaultNetwork | string | Default network:base, base-sepolia, solana, solana-devnet |

Tools

x402_payment

Call x402-enabled paid APIs with automatic USDC payment.

Agent: I'll fetch the weather data for you.
[Calls x402_payment with url="https://weather.example.com/api/conditions?city=NYC"]
[Automatically pays $0.01 USDC, receives response]
Agent: The current temperature in NYC is 45°F with partly cloudy skies.

Parameters:

  • url (required) - The x402-enabled endpoint URL
  • method - HTTP method (default: GET)
  • params - Query params (GET) or JSON body (POST/PUT/PATCH)
  • headers - Custom headers
  • network - Override network detection
  • maxPaymentUSDC - Override max payment for this request

x402_discover

Search the zauth directory for x402-enabled APIs.

Agent: Let me find weather APIs that accept x402 payments.
[Calls x402_discover with query="weather"]
Agent: I found 3 weather APIs - weather.example.com charges $0.01 per request...

Parameters:

  • query - Search term (searches url, title, description)
  • network - Filter by network: base, solana, etc.
  • verified - Only show verified endpoints
  • limit - Max results (default: 10, max: 50)

Supported Networks

EVM:

  • Base (mainnet)
  • Base Sepolia (testnet)

SVM:

  • Solana (mainnet)
  • Solana Devnet
  • Solana Testnet

How x402 Works

  1. Agent calls a paid endpoint
  2. Server returns HTTP 402 with payment requirements
  3. Extension signs and submits USDC payment
  4. Extension retries request with payment proof
  5. Server validates and returns the resource

All automatic - the agent just calls the API.

Links

License

MIT