Sign x402 payments and assemble v2 or v1 headers for gated resources.
npx skills add https://github.com/Sarnav07/Nexus.AI --skill okx-x402-payment-sarnav07
Please help me install this Agent Skill. Skill: okx-x402-payment Source: https://github.com/Sarnav07/Nexus.AI/tree/main/.agents/skills/okx-x402-payment Command: npx skills add https://github.com/Sarnav07/Nexus.AI --skill okx-x402-payment-sarnav07
Sign and attach a verified x402 payment to access payment-gated resources. This workflow eliminates manual gate checks by producing a signed authorization that can be sent with the original request.
Run the x402 payment flow to obtain a signature and authorization, then replay the original request with the resulting header to access the resource.
High-intent search queries and answers about installing and using this skill.
The x402 payment signing process uses a default TEE-based wallet session to generate the signature. If unavailable, it falls back to local EIP-3009 signing, keeping your private key on the device while producing the required authorization header.
Payment signing supports both aggr_deferred and exact payment schemes. These schemes dictate how the authorization and signature are structured before being assembled into the v2 PAYMENT-SIGNATURE or v1 X-PAYMENT headers for the gated resource request.
Yes, the workflow supports both aggr_deferred and exact payment schemes. These schemes define how the payment authorization is structured before being signed and attached to the request header for accessing the gated resource.
After signing the x402 payment, you attach the resulting signature and authorization proof as a header to your original request. Replaying this updated request unlocks access to the payment-gated resource.
No, a TEE wallet session is the default signing method but not strictly required. You can opt into local EIP-3009 signing as a fallback, which keeps the private key on your device and bypasses the need for a TEE environment.
OkheerSign x402 payments and return verifiable proofs for HTTP 402 flows.
yikedu7Sign x402 payments and replay requests with payment headers.
gursheyssImplement HTTP routing, authentication, CORS, and webhook signature verification in Convex actions.
aviral10xSign x402 payments for HTTP 402 payment-gated resources using TEE or EIP-3009.
