Minimal, v402-scoped Verus daemon JSON-RPC client: only the RPC methods the v402 payment stack needs, wrapped in a 500ms-timeout + circuit-breaker policy. Includes a mock implementation for tests. Deliberately not a general-purpose Verus client.

v402 reverse proxy: a standalone payment guard in front of ANY origin (static site, WordPress, arbitrary API). Matches route rules, challenges with 402, verifies/reserves via a v402 facilitator (HTTP mode), streams paid requests through to the upstream —

v402 protocol core: types, wire-format schemas, canonical payload serialization, amount utilities. Framework-agnostic, browser-safe.

CrewAI integration for v402 paid tool access

Normative reference test vectors for the v402 payment protocol (verus-prepaid-sig/0.1). JSON fixtures for conformance-testing v402 implementations in any language.

NestJS adapter for v402: PaymentGuard + PaymentInterceptor (two-phase debit), @V402Payment route decorator, V402Module with in-process or facilitator-HTTP verification.

Framework-agnostic verification core of v402: multi-scheme registry and the verus-prepaid-sig verifier (RPC mode) — amount pre-check, extension validation, bodyHash policy, timestamp window, two-phase debit against injected storage.

Standalone v402 facilitator daemon: verify/reserve/commit/rollback API, balance state, deposit watching, discovery — NestJS, Pino JSON logs, Prometheus metrics, Zod-validated config.

Signer implementations for v402 clients: NodeSigner (Verus daemon signmessage), EnvSigner and FileSigner (local WIF signing, byte-compatible with verusd, validated against the reference test vectors).

SQLite (WAL) implementation of the v402 storage interface — Drizzle schema, embedded migrations, BEGIN IMMEDIATE write transactions, append-only ledger.

Storage interface for the v402 facilitator (identities, deposits, spent requests, append-only ledger, blocklist, watcher cursor, reconciliation) plus an in-memory reference implementation for tests.

Deposit watcher for the v402 facilitator: real mode (block polling, reorg detection, sender-VerusID attribution, confirmation crediting, re-mine handling) and simulated mode for dev/CI without a Verus node.

v402 client for AI agents and services: wrapFetchWithPayment (transparent 402 handshake) and V402Client (balance, topup, discovery). Parallel-safe ULIDs, normative M5 retry semantics, automatic price-mismatch recovery.

MCP server for v402: gives Claude (or any MCP host) tools to autonomously pay for APIs mid-conversation — paid fetch with spending caps, balance, topup instructions and service discovery over a prepaid VerusID balance.

Conformance runner for v402 implementations: drives any implementation through the normative reference test vectors (canonical form, extensions, boundaries, wire format, signing, verification) via a pluggable target interface and reports pass/fail per cas

LangChain integration for v402 paid tool access

MCP client with automatic v402 payment handling for AI agents

The lodash method `_.sum` exported as a module.

The internal lodash function `baseIsMatch` exported as a module.

MCP server with v402 payment gating for AI agent tool access