okx-x402-payment

Sign x402 payments and return verifiable proofs for HTTP 402 flows.

Updated Apr 10, 2026

Search Tags:#payment #wallet #signing #x402 #tee #eip-3009 #onchainos

Ready to run

npx skills add https://github.com/Okheer/SENTINX --skill okx-x402-payment-okheer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: okx-x402-payment
Source: https://github.com/Okheer/SENTINX/tree/main/agent/enclave/.agents/skills/okx-x402-payment
Command: npx skills add https://github.com/Okheer/SENTINX --skill okx-x402-payment-okheer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines and secures the HTTP 402 payment flow by automatically signing x402 authorizations and returning verifiable proofs to access payment-gated resources, eliminating manual back-and-forth.

Core Features & Use Cases

TEE-based signing with a wallet session to generate payment proofs for x402-based access control.
Fallback local signing (EIP-3009) for environments without a wallet session, enabling offline readiness.
End-to-end workflow: decode the 402 payload, verify wallet status, sign via TEE or local key, assemble the correct v1/v2 header, and replay the original request to obtain the resource.

Quick Start

Ask the agent to sign an x402 payment for a payment-gated resource using the TEE wallet session, with an optional local EIP-3009 signing fallback.

Frequently Asked Questions about okx-x402-payment

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

FAQPage Schema

How do I sign x402 payments to access HTTP 402 payment-gated APIs?▼

The HTTP 402 flow requires decoding the payment payload, verifying wallet status, signing via TEE or local EIP-3009 keys, and assembling v1/v2 headers to replay the request. This returns verifiable proofs for accessing payment-gated on-chain APIs.

What is TEE-based signing for x402 payment authorizations?▼

TEE-based signing uses a Trusted Execution Environment wallet session to generate deterministic payment proofs for x402 access control. It automates HTTP 402 authorization by securely signing requests and returning verifiable proofs for payment-gated resources.

Can I sign x402 payments locally if I don't have a TEE wallet session?▼

Yes, local EIP-3009 signing serves as a fallback path when a TEE wallet session is unavailable. It enables offline readiness by using local keys to generate payment proofs and assemble v1/v2 headers for x402 payment-gated resources.

What's the best way to automate HTTP 402 payment flows for on-chain APIs?▼

Automating HTTP 402 flows involves preflight decoding, wallet verification, signing via TEE or local EIP-3009, and assembling v1/v2 headers to replay the original request. This end-to-end workflow returns verifiable x402 proofs for on-chain resources.

Do I need EIP-3009 to handle x402 payment header assembly?▼

EIP-3009 is only required for the local fallback signing path when no TEE wallet session exists. The primary path uses TEE-based deterministic signing to generate proofs and assemble v1/v2 headers for replaying the x402 payment-gated request.