skill: name: build-x402-client category: client purpose: Full procedure for building an x402 payment client from scratch, covering challenge detection through proof submission. whentouse: When implementing a new x402 client without using the X402Client SDK, or when understanding the complete client-side payment flow…
skill: name: call-x402-api category: client purpose: Use the X402Client SDK to call x402-protected APIs with automatic payment handling. whentouse: When integrating with an x402-protected API using the official SDK rather than implementing the protocol manually. inputs: Delegator URL, broadcast URL (optional), target…
skill: name: construct-payment-transaction category: client purpose: Low-level BSV transaction construction for x402 payment proofs, covering both Profile A and Profile B. whentouse: When building the partial transaction that the delegator will complete, or when understanding the exact byte-level transaction structure…
skill: name: operate-nonce-mint category: infrastructure purpose: Manage the full lifecycle of nonce UTXOs from minting through lease, spend, and replenishment. whentouse: When minting new nonce UTXOs, diagnosing pool depletion, configuring auto-replenishment, or cleaning up stale pool state. inputs: NONCEWIF (private…
skill: name: run-delegator category: infrastructure purpose: Operate the delegator service that completes partial transactions by adding fee inputs without ever broadcasting. whentouse: When deploying or debugging the delegator component that bridges client-signed partial transactions to broadcast-ready completed…
skill: name: run-x402-gateway category: infrastructure purpose: Deploy and operate an x402 payment gateway with UTXO pool management and monitoring. whentouse: When standing up a new x402 gateway instance for development or production, or when troubleshooting an existing deployment. inputs: BSV private keys (WIF…
skill: name: architecture-overview category: protocol purpose: Describe the 5-layer x402 architecture and the separation invariants between layers. whentouse: When a developer needs to understand which component is responsible for what, and what each component must never do. inputs: None. This is a reference…
skill: name: deterministic-binding category: protocol purpose: Describe how x402 deterministically binds a challenge to a specific HTTP request and how challenge hashes are computed. whentouse: When implementing challenge generation, proof verification, or any component that must produce or validate request binding…
skill: name: explain-x402-protocol category: protocol purpose: Explain the complete x402 stateless settlement-gated HTTP protocol from first principles. whentouse: When a developer needs a comprehensive understanding of x402 before building clients, gateways, or delegators. inputs: None. This is a reference…
skill: name: protocol-flow category: protocol purpose: Describe the complete 8-step x402 settlement flow from initial request to gated response. whentouse: When a developer needs to implement a client, gatekeeper, or delegator and must understand the exact sequence of operations. inputs: None. This is a reference…
skill: name: detect-double-spend category: security purpose: Detect and reject double-spend attempts across three defensive layers — consensus, replay cache, and mempool verification. whentouse: When evaluating whether a submitted proof transaction is a legitimate first spend or an attempt to reuse a nonce outpoint…
skill: name: enforce-request-binding category: security purpose: Bind each payment challenge to a specific HTTP request so that a proof for one request cannot be replayed against a different request. whentouse: When issuing a 402 challenge (to embed binding fields) and when verifying a proof (to confirm the proof…
skill: name: validate-proof category: security purpose: Verify an X402-Proof header against the original challenge and the current request to confirm payment validity. whentouse: When a client submits an X402-Proof header and the server must determine whether to grant access to the paid resource. inputs: The…
skill: name: add-x402-to-http-api category: server purpose: HTTP middleware pattern for adding x402 payment gating to any HTTP API endpoint. whentouse: When protecting an existing HTTP API with x402 payment requirements, or when implementing the server-side challenge/verify flow as middleware. inputs: Payee locking…
skill: name: implement-gateway category: server purpose: Full x402 gateway implementation covering all server-side components: gatekeeper, delegator, nonce pool, fee pool, treasury, and dashboard. whentouse: When building a complete x402 gateway that issues challenges, delegates transaction signing, manages UTXO…
skill: name: verify-payment-proof category: server purpose: Complete 16-step payment proof verification procedure for x402 server-side gatekeeper middleware. whentouse: When implementing the server-side proof verification logic that determines whether a client's payment is valid and the protected resource should be…