Validate and create x402 payment configurations and HTTP 402 responses.
npx skills add https://github.com/rawgroundbeef/claw.fm --skill x402check
Please help me install this Agent Skill. Skill: x402check Source: https://github.com/rawgroundbeef/claw.fm/tree/main/.agents/skills/x402check Command: npx skills add https://github.com/rawgroundbeef/claw.fm --skill x402check
This Skill helps developers validate and create x402 payment configurations and endpoints, ensuring compliant and predictable payment prompts for protected resources.
Validate a sample x402 config using the x402check SDK: pass a config object or HTTP 402 response to check() and review the result.
High-intent search queries and answers about installing and using this skill.
To validate an x402 payment configuration, pass your existing v1 or v2 config object to the validation check. It verifies protocol rules, enforcing CAIP-2 networks, digit string amounts, valid EVM/Solana addresses, and a top-level resource URL, returning actionable errors if invalid.
Yes, you can normalize legacy v1 x402 data to v2 formats. The conversion process migrates older configurations to the current v2 protocol structure, ensuring compatibility for HTTP 402 payment requirement responses across CAIP-2 networks.
You generate an HTTP 402 payment requirement response by creating a v2 x402 configuration from your inputs. This builds a compliant endpoint response that guides clients to complete payment for accessing a given resource on a specified CAIP-2 network.
x402 payment endpoint validation fails when configurations break protocol rules. Common diagnostic failures include missing a top-level resource URL, using invalid EVM or Solana addresses, incorrect amount formats, or unsupported CAIP-2 network identifiers.
An x402 payment configuration defines the protocol rules for an HTTP 402 payment requirement response. It structures payment prompts for protected resources by specifying the CAIP-2 network, payment amount as a digit string, and accepted EVM or Solana addresses.
Yes, x402 payment validation supports both EVM and Solana addresses. The validation process strictly enforces these address formats alongside CAIP-2 network requirements and digit string amounts to ensure compliant HTTP 402 payment configurations.
aviral10xSign x402 payments for HTTP 402 payment-gated resources using TEE or EIP-3009.
NITISH-gitbitAutomate MPP payments for HTTP 402 Payment Required API responses.
fabricioctellesImplement x402 HTTP payments for protected Express, Hono, and Next.js API routes.
SomehowLivingIntegrate Algorand 402 payment flows into TypeScript apps.
