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

@curless/agentbank-protocols

v0.2.0

Published

Agent-runtime client helpers for the agent-commerce protocols agentbank supports. One package, one subpath per protocol: import what you actually use.

Readme

@curless/agentbank-protocols

Agent-runtime client helpers for the agent-commerce protocols agentbank supports. One package, one subpath per protocol — import only what you actually use, no forced heavy deps.

Pair with @curless/agentbank-sdk on the agent's backend (API calls) and @curless/agentbank-merchant-sdk on the merchant's backend.

Subpaths

| Subpath | What it does | Extra dep | |---|---|---| | /x402 | Sign EIP-3009 transferWithAuthorization + auto-retry 402 with X-PAYMENT. | viem (peer, optional) | | /ap2 (planned) | Local JWS signing for AP2 mandates. | — | | /acp (planned, if needed) | Delegated-token helpers. | — |

/x402 quick start

npm i @curless/agentbank-protocols viem
import { payWithFetch, signerFromPrivateKey } from '@curless/agentbank-protocols/x402';

// async — viem loads lazily on first signing use
const signer = await signerFromPrivateKey(process.env.AGENT_PRIVATE_KEY as `0x${string}`);

// Auto-handle 402 → sign → retry. Just replace your fetch().
const res = await payWithFetch(
  'https://shop.example/api/buy/latte',
  { method: 'POST', body: JSON.stringify({ qty: 1 }) },
  { signer },
);
const order = await res.json();

signer is any viem LocalAccount-shaped object ({ address, signTypedData }), so an agent runtime can plug in an HSM or a Curless-managed wallet later without changing call sites.

Design

  • viem is a peer-dependency, marked optional, loaded lazily. Only code paths that actually SIGN (signX402Payment / signerFromPrivateKey) touch it — importing /x402 just to encode/decode X-PAYMENT headers works without viem installed at all.
  • Edge-safe: header encode/decode uses @curless/agentbank-core's portable base64 (no raw Buffer), so it runs on Workers / Deno.
  • One subpath per protocol keeps imports and discovery clean. Adding a protocol = adding a sibling folder, not a new npm package.

Replaces

This package replaces @curless/[email protected] (deprecated). The wire shapes and exported symbols are identical; only the import path changed: from '@curless/agentbank-x402-client'from '@curless/agentbank-protocols/x402'.