What problem does it solve? When an API or web resource returns HTTP 402 Payment Required, you need to decode the payment payload, sign an EIP-3009 authorization, and replay the request with a payment header — a multi-step cryptographic flow that is tedious to perform manually. ## Core Features & Use Cases - 402 Payload Decoding: Parses the base64-encoded x402 payload and extracts network, amount, payTo, asset, and timeout parameters. - TEE or Local Signing: Signs via the OKX Onchain OS TEE wallet session, or falls back to local EIP-3009 signing with the user's own private key. - Header Assembly and Replay: Builds the PAYMENT-SIGNATURE or X-PAYMENT header based on x402Version and replays the original request. - Use Case: You request a paid API endpoint, receive HTTP 402, confirm the payment details, sign the authorization, and automatically retry the request to receive the gated content. ## Quick Start Ask the agent to fetch a URL that requires x402 payment and it will decode the 402 response, confirm the amount with you, sign the payment, and return the resource.
