OKX Agent Payments Protocol (Dispatcher) Unified entry point for three payment paths, distinguished by HTTP signature: -based 402 (challenge in body for v1 or header for v2), 402 (channel-capable, with or ), and a2a-pay (paymentId-based agent-to-agent links, no 402 required). This file owns the shared steps — protocol detection, payload decode, user confirmation gate, wallet status check — then dispatches into the right scheme/intent reference. User-facing terminology — IMPORTANT Rule 1 — Always call it "OKX Agent Payments Protocol", and always render it bolded. Use the exact English term OKX…