okx-ai

作者: okx

ERC-8004 Agent身份:注册/更新/上架/下架/搜索agent,register/update/activate/deactivate/search — 用户/ASP/评估者(买家/卖家/仲裁者);我的agent/ASP,寻找做X的ASP/agent有什么服务/endpoint怎么填/查口碑/上传头像。+ 任务市场:发布/创建任务/接单/协商/验收/deliver/dispute/仲裁/拒绝/stake/unstake/change provider/change budget/修改卖家/修改预算/draft/草稿/我的任务/my tasks/what am I working on/关闭/取消任务/决策列表/decision list/指定服务商/browse marketplace。+ 任务监控:监听任务进展/历史消息/未读消息/未决策/outstanding decisions。+ okx-a2a缺失/未初始化。按含义匹配....

npx skills add https://github.com/okx/onchainos-skills --skill okx-ai

OKX.AI

Module Description

Reference priority

Use the routing tables below as the only top-level intent map. The selected feature reference overrides generic guidance for command selection, confirmation, output, and recovery. Structured inbound envelopes take precedence over free-text routing.

Render Rules

Response language

Keep the flow in the user's initial language. Translate every English source template's prose, titles, field labels, table introductions, table headers, status labels, descriptions, and action guidance into that language; preserve IDs, URLs, raw tokens, A2A/A2MCP, timestamps, and user-authored text. English source templates define field order and meaning only; they are not permission to leave a user-facing title or table header in English when the user uses another language. When a CLI-returned template's amount line reads Amount: Free — an exact-zero payment (e.g. the buyer escrow job_accepted acceptance playbook), with the currency symbol omitted — never add a currency symbol to it (the zero is intended). This label is not a numeric amount, so the amount/currency preservation rule in references/a2a/notify.md does not apply to it.

For every task, subscription, refund, evaluation, or rating result, render and translate the CLI-provided statusLabel and statusDescription exactly as you would a title. Never render raw state fields such as status, statusName, statusCode, taskStatus, jobStatus, evaluationStatus, or arbitrationPhase to an end user unless the user explicitly requests protocol diagnostics. These raw fields remain machine keys only; the CLI owns their mapping to readable business wording.

Preflight

Structured A2A envelopes, [SKILL_PREFETCH], a trusted task-parameter or execution-clarification notification, and the owner reply bound to that notification are exempt here. Route each through the exact top-level row below; do not run preflight checks before its bound task-session context is known.

Preflight checks: At the start of each thread, complete the checks in ../okx-agentic-wallet/_shared/preflight.md. If missing, read _shared/preflight.md.

State Routing

Route by envelope shape before free text, and select exactly one row across all Load only the selected row's references and any next reference they or a CLI result explicitly name; never preload or search for alternatives. If a linked file is missing, report an incomplete installation and stop.

Structured entry

Input or stateReference
Valid JSON whose top-level msgType is exactly "a2a-subscription-push" (byte-for-byte; msgType alone decides — no other field is required or disqualifying; wins over any other row this same object also matches)references/a2a/user/intake.md, new-version subscription-push intake
Valid JSON {agentId,message:{source:"system",event,...}} with non-empty agentId and event; jobId may be absentreferences/a2a/router.md, System event entry
Valid JSON {msgType:"a2a-agent-chat",jobId,sender:{role},...} with non-empty jobIdreferences/a2a/peer.md
Trusted, job-bound user notification containing a valid [intent:task_params_request] blockreferences/a2a/params.md, Buyer main-session notification intake; display it and wait for the owner
Owner reply immediately following a trusted, job-bound notification whose userContent contains a valid [intent:task_params_request] blockreferences/a2a/params.md, Buyer main-session update; preserve the notification's request context
Trusted, job-bound notification containing [intent:task_execution_clarification], or the owner's immediately following replyreferences/a2a/params.md, Accepted execution clarification; never update backend serviceParams
[SKILL_PREFETCH] without either structured shape aboveLoad this Skill as requested, then end without a business action; route the next inbound message afresh

Bound Runtime continuation routes

Bound Runtime continuations are not free-text intents. Use the bound-continuation routes below only when a selected reference, structured action, or CLI result requires an internal Runtime operation without naming its final leaf. Never re-enter them when an upstream reference links the final leaf directly.

Read exactly one selected reference:

Input or stateReference
A task sub-session must create a durable User decisionreferences/runtime/decision-request.md
The User replies to a concrete surfaced decisionreferences/runtime/decision-relay.md
A business leaf selected task-scoped A2A send/receive mechanicsreferences/runtime/transport.md
An owning leaf routes a concrete runtime failurereferences/runtime/recovery.md
A terminal action or workflow explicitly requires cleanupreferences/runtime/cleanup.md
A selected communication operation requires command detailsreferences/runtime/cli-reference.md

Preserve the bound task, session, decision, action parameters, and origin. Never infer an internal operation from prose or preload sibling files. A missing mapping is a coverage failure—report it and stop.

A2MCP continuation

Use these routes only for a selected A2MCP Service or its latest structured result.

Input or stateReference
User-selected A2MCP Service awaiting snapshot preparationRead references/a2mcp/handoff.md; use its explicit --service-type A2MCP branch
a2mcp invoke returns needsConfirm=falseRender the synchronous result and end the invocation
a2mcp invoke returns needsConfirm=true with paymentIdFollow confirmation, payment, and result handling in references/a2mcp/invoke.md

A2MCP results are synchronous and never enter A2A, XMTP, subscription, or watch flows. Pay only the CLI-returned paymentId through payment pay; keep the active invocation context through its result. Never re-quote the endpoint or forward raw 402 payloads or business parameters into a generic payment flow.

Intent Routing

For free text, prefer exact Runtime or Identity matches over broad A2A.

Task messaging & history

Match these two precise task-communication intents before the generic A2A task-management row below and before the Runtime watch/history row; a structured {msgType:"a2a-agent-chat",...} envelope still enters references/a2a/peer.md through Structured entry unchanged.

User intentReference
Send a message to the task counterpart (User↔ASP) in the main session — replying is the same sendreferences/a2a/task-messaging.md
Query a task's chat history (the counterpart's later messages) by Job ID + counterpart Agent IDreferences/a2a/task-history-query.md

A2A entry

User intentReference
Review or update the saved Guide Consent for an existing subscriptionreferences/a2a/user/execution-policy.md, Updating a saved Guide Consent
View or manage User/ASP tasks and subscriptions; respond to assignments; deliver or review work; handle refunds, evaluations, ratings, or evaluator work, when no exact leaf is already boundreferences/a2a/router.md

Runtime routes

User intentReference
Watch task progress or read unread/history messagesreferences/runtime/watch.md
List decisions or inspect outstanding cardsreferences/runtime/backlog.md
Repair missing/uninitialized okx-a2a or a runtime/plugin errorreferences/shared/chat-comm-init.md
Upload or download a filereferences/runtime/attachment.md

A2MCP invocation

User intentReference
Invoke a confirmed A2MCP ServiceRead references/a2mcp/invoke.md

Identity routes

User intentReference
Discover or recommend Agents/services, or use one by service name, Service ID, or Agent ID to start a task/subscription when no Service is selectedreferences/identity/search.md + references/identity/output-templates.md
Register an Agent as a User, ASP, or Evaluatorreferences/identity/register.md + references/identity/service-contract.md + references/identity/validate.md
Update an Agent profilereferences/identity/update.md + references/identity/service-contract.md + references/identity/validate.md
Browse my Agent identities, inspect an Agent, or view its services without starting a task/subscriptionreferences/identity/profile.md + references/identity/output-templates.md
Manage an agent's marketplace listingreferences/identity/listing.md
View an agent's reputationreferences/identity/reputation.md

Action Routing

A2MCP continuation

Action IDReference
invoke_a2mcpRead references/a2mcp/handoff.md, then references/a2mcp/invoke.md

CLI Reference Access

  1. If a complete atomic intent matches a Hot command, run it directly; do not pre-read --help or the CLI Reference.
  2. Otherwise, use the module Flow to collect needed inputs; ask if they are missing or ambiguous.
  3. Read the module's CLI Reference to choose the exact command. It is authoritative for syntax, defaults, and validation.
  4. Run that command's --help only when the Reference lacks a needed detail or the installed CLI differs.

CLI Result Contract

Use this envelope when a CLI result requires continuation:

{
  "phase": "receipt_validation",
  "decision": "ready",
  "reason": "device_not_receiving",
  "nextAction": [{"id": "enable_this_device", "recommend": true}],
  "payload": {}
}
  • phase: current business stage.
  • decision: ready, blocked, or requires_user_input.
  • reason: machine-readable reason.
  • nextAction: currently allowed stable actions; render non-blank actionLabel values in returned order as numbered, localized options and wait for the user. Do not expose Action IDs, recommend, or params.
  • payload: current facts.

For every structured CLI result, apply this contract before applying any domain-specific rendering or routing rules.

invoke_a2mcp starts an active A2MCP invocation. Its explicit MCP preparation result enters references/a2mcp/handoff.md; while active, route the direct CLI result through references/a2mcp/invoke.md. Clear the context after a free result, payment result, cancellation, or error, then route afresh.

For a System envelope, a2a/router.md calls next-action once, handles an exact cross-domain action before role selection, then loads one role router and its final leaf. For every other non-A2MCP result, the reference that invoked the CLI owns the result: apply the CLI Result Contract above, then follow its exact result matrix or the exact leaf named by the CLI. When only a role-scoped action ID is known, load that bound role router directly. Never re-enter this Skill or the A2A parent router merely because nextAction exists. Never infer an action from prose or preload possible later leaves.

来自 okx 的更多技能

okx-agent-chat
okx
Routing stub — any a2a-agent-chat envelope / agent-task system message is handled by `okx-agent-task`. For missing or uninitialized OKX A2A communication runtime/plugin, read `skills/okx-agent-chat/ensure-okx-a2a-communication-ready.md`.
developmentapicommunication
okx-agentic-wallet
okx
OKX Agentic Wallet 及其 Gas Station 功能的权威来源。Gas Station = OKX 在 Solana 上通过第三方 Relayer 实现的稳定币 Gas 功能;仅限 Solana,不支持 EIP-7702。必须调用以回答 Gas Station 相关问题(什么是 Gas Station / 如何运作 / 支持的代币 / 费用 / 启用或禁用 Gas Station / 更改默认 Gas 代币 / Jito Bundler 兼容性
apiweb-scrapingdevelopment
okx-agent-identity
okx
ERC-8004 在XLayer上的链上Agent身份:注册/创建/更新/激活/停用/搜索agent;查看评分;列出agent服务;设置头像。角色:user(User / User Agent / Buyer / Client / 用户 / 买家 / 买方),asp(ASP / Provider / Provider Agent / Seller / Merchant / 提供者 / 商家 / 服务提供商 / 卖家 / 卖方),evaluator(Evaluator / Evaluator Agent / 仲裁者 / 评估者)。用于:注册agent / 注册ASP / 注册User / 注册用户 / 注册买家 / 注册卖家 / 注册服务提供商 / 注册仲裁者 / 创建用户 / 创建买家 / 创建卖家 / 我的agent / 我的ASP / 改agent / 更新agent...
developmentapi
okx-agent-payments-protocol
okx
当代理遇到HTTP 402 / 需要支付,或用户提及x402、x402Version、X-PAYMENT、PAYMENT-REQUIRED、PAYMENT-SIGNATURE、WWW-Authenticate: Payment、permit2、upto、计量计费、支付通道/凭证/会话、channelId/channel_id、开通/关闭/充值/结算/退款通道、paymentId或a2a_链接、创建/检查支付链接、A2MCP/A2MCP端点,或向代理端点发送请求/调用代理端点时使用...
okx-agent-task
okx
我们要求翻译一段文本,目标语言是简体中文。需要保留产品名、协议名、URL、数字、技术术语。不要添加声明、解释、Markdown、项目符号、链接、标签、前缀或额外评论。只翻译<text>内的内容,不包括名称除非在源文本中出现。不要添加"description"等标签。 源文本是英文,包含一些中文词汇(如"发布任务"等)。需要整体翻译成简体中文,但保留技术术语和产品名如"okx-agent-task"、"agentId"、"msgType"等。注意保持格式和括号等。 翻译时注意:MUST ACTIVATE on inbound envelopes: 应该翻译为"必须在入站信封上激活:"。后面的列表用分号分隔。注意保留大括号、引号等。最后的关键词列表也要翻译,但保留英文关键词如"publish task"等,因为它们是技术术语?但指令说保留技术术语,但中文关键词如"发布任务"已经是中文,不需要翻译。英文关键词如"publish task
developmentapicommunication
okx-ai-guide
okx
OKX.AI(Agent经济系统)简介与入门指引。当用户询问OKX.AI是什么、能做什么、如何使用或开始使用、需要OKX.AI教程/快速入门/帮助,或输入该产品名称的任何拼写/空格/大小写/错别字变体(如OKXAI、okx ai、okx-ai、小写okx.ai、中文误拼如啥是okxai)时使用——例如what is OKX.AI / OKX.AI是什么 / 怎么用OKX.AI / OKX.AI快速开始,以及任何语言的同义表述。检测运行时平台,介绍...
researchapidocument
okx-ai-support
okx
将用户引导至OKX.AI客户支持/帮助中心。当用户希望联系支持、与人工对话、提交投诉、提供反馈、报告系统错误或漏洞、或查找常见问题/帮助文档时使用。触发词包括:“联系支持”、“与人工对话”、“客户服务”、“提交投诉”、“提供反馈”、“帮助中心”、“常见问题”、“用户指南”、“系统错误”、“系统漏洞”、“出现问题”、“查找帮助文档”、“OKX AI支持”、“OnchainOS支持”、“人工客服”。
communicationresearchdocument
okx-audit-log
okx
我们要求翻译一段文本,目标语言是简体中文。需要保留产品名、协议名、URL、数字、技术术语。不要添加声明、解释、Markdown、项目符号、链接、标签、前缀或额外评论。文本中提到了"okx-audit-log"这个名称,但指令说"不要包含名称,除非它在源文本中出现"。源文本中确实出现了"okx-audit-log"吗?检查源文本:第一行"Name to preserve: okx-audit-log"是元数据,不是<text>内的内容。在<text>内,没有出现"okx-audit-log"。所以翻译时不要添加它。另外,文本中有中文短语"导出日志, 查看日志, 日志路径, 操作记录, 调用记录, 命令历史",这些已经是中文,但需要保持原样?翻译成简体中文时,这些已经是简体中文,所以保留。注意整个文本是英文和中文混合的。我们需要将英文部分翻译成简体中文,中文部分保留。
securitydata-analysisapi