jupiter-vrfd
installsforks
How to install jupiter-vrfd?
jup-ag/agent-skills/jupiter-vrfd
$npx -y skills add jup-ag/agent-skills --skill jupiter-vrfdUse 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.
SKILL.md
| 1 | # Jupiter Token Verification |
| 2 | |
| 3 | This skill routes agents through the public Jupiter token-verification flow for a Solana token mint. |
| 4 | |
| 5 | **Base URL**: `https://api.jup.ag` |
| 6 | **Auth**: `x-api-key` from [developers.jup.ag](https://developers.jup.ag/) (required) |
| 7 | **Cost**: 1000 JUP |
| 8 | |
| 9 | ## Use/Do Not Use |
| 10 | |
| 11 | Use when: |
| 12 | |
| 13 | - checking whether a token is eligible for submission |
| 14 | - crafting and signing the submission payment transaction |
| 15 | - executing the submission flow |
| 16 | - optionally updating token metadata as part of the submission |
| 17 | - submitting a metadata-only paid update when eligibility allows metadata but not verification |
| 18 | |
| 19 | Do not use when: |
| 20 | |
| 21 | - the agent would need private or internal routes |
| 22 | - the agent needs to fetch or merge existing metadata from non-public endpoints |
| 23 | - the user wants swaps, trading, or unrelated Jupiter flows |
| 24 | |
| 25 | **Triggers**: `verify token`, `submit verification`, `check eligibility`, `craft payment transaction`, `execute payment`, `pay for verification`, `update token metadata`, `metadata-only submission` |
| 26 | |
| 27 | ## Intent Router |
| 28 | |
| 29 | | User intent | Endpoint | Method | |
| 30 | | ------------------------- | -------------------------------------------------------------------- | ------ | |
| 31 | | Check eligibility | `/tokens/v2/verify/express/check-eligibility?tokenId={TOKEN_ID}` | `GET` | |
| 32 | | Craft payment transaction | `/tokens/v2/verify/express/craft-txn?senderAddress={SENDER_ADDRESS}` | `GET` | |
| 33 | | Sign and execute payment | `/tokens/v2/verify/express/execute` | `POST` | |
| 34 | |
| 35 | ## Eligibility Decision Matrix |
| 36 | |
| 37 | | `canVerify` | `canMetadata` | Action | |
| 38 | | ----------- | ------------- | ----------------------------------------------------------------- | |
| 39 | | `true` | `true` | verification+metadata (if user has metadata) or verification only | |
| 40 | | `true` | `false` | verification only, omit `tokenMetadata` | |
| 41 | | `false` | `true` | metadata-only | |
| 42 | | `false` | `false` | **STOP** — show `verificationError` / `metadataError` to user | |
| 43 | |
| 44 | ## Examples |
| 45 | |
| 46 | Load these on demand: |
| 47 | |
| 48 | - **[API Reference](./references/api-reference.md)** 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. |
| 49 | - **[Verify](./examples/verify.md)** when the user wants to execute a request and has confirmed the paying wallet details |
| 50 | |
| 51 | ## Agent Operating Rules |
| 52 | |
| 53 | - Reuse as much as possible from the user's first message. Ask only for missing required fields. |
| 54 | - Never ask the user to paste a raw private key or seed phrase into chat. |
| 55 | - Never print secret values. Only mention non-sensitive file paths, key names, and derived public addresses. |
| 56 | - Do not claim a request was submitted unless you have a real API response or the user explicitly ran the local script themselves. |
| 57 | - 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. |
| 58 | |
| 59 | ## Execution Notes |
| 60 | |
| 61 | For execute requests in constrained agent environments: |
| 62 | |
| 63 | - outbound HTTP and package installation may require approval or user permission |
| 64 | - 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 |
| 65 | |
| 66 | ## Resources |
| 67 | |
| 68 | - **Jupiter Burn Multisig**: `8gMBNeKwXaoNi9bhbVUWFt4Uc5aobL9PeYMXfYDMePE2` |
| 69 | - **JUP Token Mint**: `JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN` |
| 70 | - **Jupiter Docs**: [developers.jup.ag](https://developers.jup.ag) |
| 71 | - **Jupiter Verified**: [verified.jup.ag](https://verified.jup.ag) |
People who liked this also viewed
6 picksType
- remotion-to-hyperframesPort an existing Remotion (React) composition''s source to HyperFrames HTML. Use ONLY on an explicit ask to port/convert/migrate/translate a Remotion source — one-way, Remotion-only. A passing RemotioSkillsJul 2026
- solana-devUse when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain SSkillsJul 2026
- grimoire-polymarketQueries Polymarket market data and CLOB state, and manages CLOB orders via the Grimoire venue CLI wrapper backed by the official Polymarket CLI.SkillsMay 2026
- shopify-storefront-graphqlUse for custom storefronts requiring direct GraphQL queries/mutations for data fetching and cart operations. Choose this when you need full control over data fetching and rendering your own UI. NOT foSkillsJul 2026
- agentic-walletCrypto wallet operations via the awal CLI — sign in, check balances, send USDC/ETH/POL/SOL, trade tokens, fund the wallet, and use the x402 payment protocol to discover paid services, pay for API callSkillsJun 2026
- quicknode-skillQuicknode blockchain infrastructure for 80+ chains: Core RPC API, Streams, Webhooks, Blazar WSS, Solana gRPC, HyperCore gRPC, SQL Explorer, Metaplex DAS API, Blockbook, Ordinals & Runes API, Swap API,SkillsJul 2026
