Use when a user mentions Jupiter token verification, VRFD eligibility, paying 1000 JUP to verify a token, submitting a verification request, or updating metadata via the Jupiter express verification flow.
SkillScore95Maintained
Automatic
◆Coding packjupiterjup-agjupiter-vrfd
Last verified 9/8/2026
What it changes
Passed 21 of 22 test cases with the skill, and 8 of 22 without it.
Without skill36%
With skill95%
Checks it passed that the model alone missed
States the verification cost as 1000 JUP.
Identifies the payment amount as 1000 JUP.
Directs proceeding with token verification.
and 15 more in the full report
13 fixed8 passed either way1 still failing0 broke
Pass-rate lift
+59 pp
Tokens
+11%
Agent turns
0%
Response time
-38%
Model gemini-3.6-flashMeasured 9/8/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
I am configuring a script to verify a Solana token mint on Jupiter and need to specify the mint address of the JUP token used for payment. What is the JUP token mint address?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies the JUP token mint address as JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN.
Missed
Passed
case-11 · gemini-3.6-flash · 9/8/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md71 lines2 files
Jupiter Token Verification
This skill routes agents through the public Jupiter token-verification flow for a Solana token mint.
Base URL: https://api.jup.agAuth: x-api-key from developers.jup.ag (required)
Cost: 1000 JUP
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
Build a production 1:1 stablecoin swap with LI.FI Intents — an interface or backend where
the amount the user sends equals the amount they receive (no visible gas or solver fees),
same-chain or cross-chain, filled by LI.FI's solver network and verifiable on-chain.
USE THIS SKILL WHEN USER WANTS TO:
- Build a 1:1 stablecoin swap interface ("send 100 USDC, receive 100 USDC"), same- or cross-chain
- Add stablecoin transfers with a guaranteed output amount to an app, backend, or bot
- Build enterpr