okx-agent-payments-protocol
okx agent payments protocol
What it does
- summary — the human one-liner. needsConfirm is always true here.
- missingParams[] + merchantBody — params the CLI could not fill; find the rest in merchantBody.
- walletError — if loginrequired, tell the user to log in, then re-quote.
- recommended:null on every candidate ⇒ no balance anywhere; present the list and ask.
- success → report txHash; (Entry B) the task system marks the node paid.
- failed → surface data.error; offer retry.
- pending → poll / await terminal, then continue.
Requirements & configuration
- | Need to decode a PAYMENT-RESPONSE header or a charge receipt | payment decode-receipt (--header <b64> \| --receipt <json>) | (inline — read-only) |
- The user picked an alternative from A3.5's expanded list (the picked candidate still needs full-detail confirmation).
- This resource requires payment via the OKX Agent Payments Protocol:
- Token: <token symbol> (<option.asset>)
- Amount: <human-readable amount> (from option.amount for v2, or option.maxAmountRequired for v1; convert from minimal units using token decimals)
Configuration: PAYMENTHEADDELETEPOSTPATCHHTTP
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
okx-agent-payments-protocol FAQ
What does the okx-agent-payments-protocol skill do?
Use when an agent hits HTTP 402 / payment-required, or the user mentions x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, a payment channel / voucher / session, channelId / channel_id, opening / closing / topping up / settling / refunding a channel, a paymentId or a2a_ link, creating / checking a payment link, A2MCP / an A2MCP endpoint, or sending a request to / calling an Agent's endpoint with a concrete endpoint URL. Covers x402 (exact, exact+Permit2, upto, aggr_deferred), MPP (charge / session), and a2a-pay paymentId flows. Any close / topup / settle / voucher / refund near a channel_id or session is an MPP mid-session op. Two-phase quote/pay: `payment quote`, `payment pay --payment-id`, `decode-receipt`. The full bilingual trigger list (including Chinese) lives in the skill body. summary — the human one-liner. needsConfirm is always true here. missingParams[] + merchantBody — params the CLI could not fill; find the rest in merchantBody.
What does okx-agent-payments-protocol require?
| Need to decode a PAYMENT-RESPONSE header or a charge receipt | payment decode-receipt (--header <b64> \| --receipt <json>) | (inline — read-only) | The user picked an alternative from A3.5's expanded list (the picked candidate still needs full-detail confirmation). This resource requires payment via the OKX Agent Payments Protocol: Token: <token symbol> (<option.asset>) Amount: <human-readable amount> (from option.amount for v2, or option.maxAmountRequired for v1; convert from minimal units using token decimals) Configuration keys: PAYMENT, HEAD, DELETE, POST, PATCH, HTTP.
How do I install okx-agent-payments-protocol?
Run: npx -y skills add https://github.com/okx/onchainos-skills --skill okx-agent-payments-protocol --agent claude-code — the source lives at github.com/okx/onchainos-skills.
Maintain okx-agent-payments-protocol?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[](https://getagentictools.com/skills/okx-onchainos-skills-okx-agent-payments-protocol?ref=badge) npx agentictools info skills/okx-onchainos-skills-okx-agent-payments-protocol The second line is the CLI lookup for this page — handy in READMEs and docs.
