jupiter-vrfd
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseJupiter Token Verification
Jupiter 代币验证
This skill routes agents through the public Jupiter token-verification flow for a Solana token mint.
本技能引导Agent完成针对Solana代币铸造的公开Jupiter代币验证流程。
Use/Do Not Use
适用/不适用场景
Use when:
- checking whether a token is eligible for submission
- crafting and signing the submission payment transaction
- executing the submission flow
- optionally updating token metadata as part of the submission
- submitting a metadata-only paid update when eligibility allows metadata but not verification
Do not use when:
- the agent would need private or internal routes
- the agent needs to fetch or merge existing metadata from non-public endpoints
- the user wants swaps, trading, or unrelated Jupiter flows
Triggers: , , , , , , ,
verify tokensubmit verificationcheck eligibilitycraft payment transactionexecute paymentpay for verificationupdate token metadatametadata-only submission适用场景:
- 检查代币是否符合提交条件
- 构造并签署提交支付交易
- 执行提交流程
- 可选择在提交时同步更新代币元数据
- 当资格允许仅更新元数据而非验证时,提交仅元数据的付费更新
不适用场景:
- Agent需要访问私有或内部路由
- Agent需要从非公开端点获取或合并现有元数据
- 用户想要兑换、交易或其他无关的Jupiter流程
触发词: , , , , , , ,
verify tokensubmit verificationcheck eligibilitycraft payment transactionexecute paymentpay for verificationupdate token metadatametadata-only submissionIntent Router
意图路由
| User intent | Endpoint | Method |
|---|---|---|
| Check eligibility | | |
| Craft payment transaction | | |
| Sign and execute payment | | |
| 用户意图 | 接口端点 | 请求方法 |
|---|---|---|
| 资格校验 | | |
| 构造支付交易 | | |
| 签署并执行支付 | | |
Eligibility Decision Matrix
资格判定矩阵
| | Action |
|---|---|---|
| | verification+metadata (if user has metadata) or verification only |
| | verification only, omit |
| | metadata-only |
| | STOP — show |
| | 可执行操作 |
|---|---|---|
| | 验证+元数据更新(如果用户提供了元数据)或仅验证 |
| | 仅验证,省略 |
| | 仅更新元数据 |
| | 终止流程 — 向用户展示 |
Examples
示例
Load these on demand:
- API Reference for the exact request and response shapes, accepted input formats, normalization rules, submission-mode field requirements, and token metadata fields. This is the source of truth for request construction.
- Verify when the user wants to execute a request and has confirmed the paying wallet details
按需加载以下内容:
- API参考 包含确切的请求和响应结构、可接受的输入格式、标准化规则、提交模式字段要求以及代币元数据字段,是构造请求的权威依据。
- 验证流程 适用于用户想要执行请求且已确认支付钱包详情的场景
Agent Operating Rules
Agent运行规则
- Reuse as much as possible from the user's first message. Ask only for missing required fields.
- Never ask the user to paste a raw private key or seed phrase into chat.
- Never print secret values. Only mention non-sensitive file paths, key names, and derived public addresses.
- Do not claim a request was submitted unless you have a real API response or the user explicitly ran the local script themselves.
- If the current agent runtime cannot reach the network, install dependencies, or access local signer files, stop before execution and hand the user the exact local steps instead of fabricating progress.
- 尽可能复用用户首次消息中的内容,仅询问缺失的必填字段。
- 绝对不要要求用户在聊天中粘贴原始私钥或助记词。
- 绝对不要输出私密值,仅提及非敏感的文件路径、密钥名称以及派生的公开地址。
- 除非你收到了真实的API响应,或者用户明确自己运行了本地脚本,否则不要声称请求已提交。
- 如果当前Agent运行环境无法连接网络、安装依赖或访问本地签名器文件,在执行前终止流程,向用户提供准确的本地执行步骤,不要伪造进度。
Execution Notes
执行注意事项
For execute requests in constrained agent environments:
- outbound HTTP and package installation may require approval or user permission
- equivalent shell and package-manager commands are fine; do not block on a specific CLI if the environment already has an equivalent way to run the same steps
在受限Agent环境中执行请求时:
- 出站HTTP请求和包安装可能需要审批或用户权限
- 可以使用等效的shell和包管理器命令;如果环境已有等效方式完成相同步骤,不要强制要求使用特定CLI
Resources
相关资源
- Jupiter Burn Multisig:
8gMBNeKwXaoNi9bhbVUWFt4Uc5aobL9PeYMXfYDMePE2 - JUP Token Mint:
JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN - Jupiter Docs: dev.jup.ag
- Jupiter Verified: verified.jup.ag
- Jupiter销毁多签地址:
8gMBNeKwXaoNi9bhbVUWFt4Uc5aobL9PeYMXfYDMePE2 - JUP代币铸造地址:
JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN - Jupiter开发者文档: dev.jup.ag
- Jupiter验证入口: verified.jup.ag