okx-x402-payment

Sign x402 payments for HTTP 402 payment-gated resources using TEE or EIP-3009.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/aviral10x/agent-arena --skill okx-x402-payment-aviral10x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: okx-x402-payment
Source: https://github.com/aviral10x/agent-arena/tree/main/.agents/skills/okx-x402-payment
Command: npx skills add https://github.com/aviral10x/agent-arena --skill okx-x402-payment-aviral10x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables secure access to paid resources by signing and delivering x402 payment proofs, using either a wallet-backed TEE session or local EIP-3009 signing when a wallet is unavailable.

Core Features & Use Cases

  • End-to-end x402 payment signing to access HTTP 402 gated resources.
  • Dual signing paths: wallet session (TEE) or offline local signing with a private key.
  • Replays the original request with the correct header (signature + authorization) to unlock the resource.

Quick Start

Decode the 402 payload, sign a payment with onchainos, and replay the original request with the appropriate header.

Frequently Asked Questions about okx-x402-payment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an HTTP 402 payment and how does x402 signing work?

x402 payment signing automates access to HTTP 402 gated resources by decoding the 402 payload and applying cryptographic signatures. It replays the original request with a constructed header containing the signature and authorization data to unlock the resource.

How do I sign x402 payments to access gated resources?

To sign x402 payments, decode the 402 payload, choose between wallet-based TEE signing or local EIP-3009 signing, and replay the original request with the appropriate header. This delivers the payment proof needed to unlock the gated resource.

Can I use local EIP-3009 signing for x402 payments without a wallet?

Yes, local EIP-3009 signing enables offline x402 payment signing with a private key when a wallet is unavailable. This provides a dual signing path alongside wallet-backed TEE sessions to satisfy network CAIP-2 and authorization requirements.

Does x402 payment signing support wallet-backed TEE sessions?

Yes, x402 payment signing supports wallet-backed TEE sessions as a dual signing path. This allows secure on-chainos payment signing through a wallet session, constructing the required header with signature and authorization to access gated resources.

What are the limitations of x402 payment signing for HTTP 402 responses?

x402 payment signing is limited to HTTP 402 gated resources and requires either a wallet-backed TEE session or a local EIP-3009 private key. It must satisfy network CAIP-2, authorization data, and header construction requirements to successfully replay the request.