jupiter-vrfd

Guide agents through Jupiter VRFD eligibility checks, transaction crafting, and metadata submission.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/frederik-maker/jupiter-pulse --skill jupiter-vrfd-frederik-maker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jupiter-vrfd
Source: https://github.com/frederik-maker/jupiter-pulse/tree/main/.agents/skills/jupiter-vrfd
Command: npx skills add https://github.com/frederik-maker/jupiter-pulse --skill jupiter-vrfd-frederik-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enables AI agents to navigate the public Jupiter Token Verification (VRFD) flow, handling eligibility checks, unsigned-transaction crafting, and metadata submission with safety guidance.

Core Features & Use Cases

  • Eligibility checks via GET /tokens/v2/verify/express/check-eligibility to determine canVerify and canMetadata.
  • Crafting the unsigned 1000 JUP payment transaction via GET /tokens/v2/verify/express/craft-txn, with validation of receiver, mint, amount, and expiry.
  • Submitting the signed transaction and creating verification/metadata updates via POST /tokens/v2/verify/express/execute, including normalization of handles and optional tokenMetadata payload.
  • Documentation and examples outlining request/response shapes, error handling, and local execution guidance.

Quick Start

Check eligibility, craft the unsigned transaction, sign it locally, and execute the submission.

Frequently Asked Questions about jupiter-vrfd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Jupiter token verification for Solana using an API?

Solana token verification via the Jupiter VRFD API is automated by guiding agents through eligibility checks, crafting unsigned 1000 JUP payment transactions, and executing signed metadata submissions.

How do I check Solana token verification eligibility before submitting metadata?

Token verification eligibility is checked using the Jupiter VRFD GET endpoint to determine canVerify and canMetadata status before crafting any unsigned transaction or submitting metadata updates.

How do I craft an unsigned transaction for Jupiter VRFD token verification?

Unsigned verification transactions are crafted via the Jupiter VRFD GET endpoint, which validates the 1000 JUP payment receiver, mint address, amount, and expiry before requiring your local signature.

Can I execute Jupiter VRFD metadata updates through an automated agent workflow?

Automated agents can execute Jupiter VRFD metadata updates by submitting signed transactions via the POST endpoint, which handles verification creation, handle normalization, and optional tokenMetadata payloads.

What limitations should I expect when integrating Jupiter VRFD API routes?

Jupiter VRFD API integration requires handling specific request shapes, error handling, and normalization rules, meaning agents must strictly validate receiver, mint, amount, and expiry fields to avoid transaction failures.