Okx A2a Payment
Resolve legacy agent invocations that still name okx-a2a-payment by redirecting the agent to okx-agent-payments-protocol without executing deprecated payment logic.
Overview
okx-a2a-payment is an agent skill for the Build phase that is a deprecated redirect stub—load okx-agent-payments-protocol instead of running any payment logic here.
Install
npx skills add https://github.com/okx/onchainos-skills --skill okx-a2a-paymentWhat is this skill?
- Explicitly deprecated in SKILL.md metadata with successor okx-agent-payments-protocol
- Instructs agents to load okx-agent-payments-protocol immediately and follow Path B (paymentId-based, no 402)
- Do NOT execute payment logic from this stub—zero triggers of its own on new conversations
- References a2a_charge.md playbook inside the successor skill for create / pay / status
- Version 3.3.9 MIT-licensed stub for legacy transcripts and external docs only
- Successor skill documents Path B as paymentId-based flow without HTTP 402
Adoption & trust: 2k installs on skills.sh; 284 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Legacy automations and chat logs still invoke okx-a2a-payment by name, which would otherwise leave agents without a correct payment playbook.
Who is it for?
Maintainers cleaning up old OKX A2A payment references who need a explicit handoff string for agents and docs.
Skip if: New OKX agent payment implementations—start with okx-agent-payments-protocol directly and skip this stub entirely.
When should I use this skill?
Legacy invocations reference okx-a2a-payment, paymentId, a2a_..., payment-link, or payment-status and must be redirected to okx-agent-payments-protocol.
What do I get? / Deliverables
The agent loads okx-agent-payments-protocol and follows Path B and a2a_charge.md for create, pay, and status—no payment execution from this stub.
- Redirect instruction to load okx-agent-payments-protocol
- No standalone payment transactions from this stub
Recommended Skills
Journey fit
Canonical shelf is Build integrations because agent-to-agent payment wiring happens while connecting OKX payment flows into agent stacks, even though this entry is only a redirect stub. Integrations fits a deprecated alias whose sole job is to point paymentId and a2a triggers at the unified dispatcher skill.
How it compares
This is a deprecated name alias, not a standalone MCP server or payment implementation—use okx-agent-payments-protocol for real dispatcher logic.
Common Questions / FAQ
Who is okx-a2a-payment for?
Developers and agents that encounter the old okx-a2a-payment skill id in legacy configs or transcripts and need an automatic redirect to the merged OKX payment protocol skill.
When should I use okx-a2a-payment?
Only when a tool call or doc explicitly references this deprecated name—then immediately switch to okx-agent-payments-protocol; for new paymentId or a2a flows in Build integrations, invoke the successor skill directly.
Is okx-a2a-payment safe to install?
The stub forbids executing payment logic; review the Security Audits panel on this Prism page and prefer okx-agent-payments-protocol for any live payment operations on mainnet or production keys.
Workflow Chain
Then invoke: okx agent payments protocol
SKILL.md
READMESKILL.md - Okx A2a Payment
# DEPRECATED — merged into `okx-agent-payments-protocol` This skill has been folded into the unified payment dispatcher. The functionality is unchanged; only the entry point has changed. **What to do**: load **`okx-agent-payments-protocol`** via the Skill tool and follow that skill instead. The a2a-pay flow lives at: - `okx-agent-payments-protocol/SKILL.md` — Path B (paymentId-based, no 402) - `okx-agent-payments-protocol/references/a2a_charge.md` — full create / pay / status playbook **Why this stub exists**: legacy transcripts, scripts, and external docs may still reference `okx-a2a-payment` by name. This stub catches those references and redirects to the merged skill. It carries no triggers of its own — new conversations mentioning paymentId / `a2a_...` / "create payment link" / "payment status" route directly to `okx-agent-payments-protocol` based on that skill's triggers.