Jupiter Vrfd logo

Jupiter Vrfd

OrganizationPopular
internet-court
jupiter-vrfd

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.

Overview

Publisherinternet-court
Repositoryinternet-court-skill
Skill namejupiter-vrfd
Stars
5.8K
Forks
106
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by internet-court on GitHub. Read the source before you install it.

Installation

Install the Jupiter Vrfd AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/internet-court/internet-court-skill.git /tmp/internet-court-skill
mkdir -p .claude/skills
cp -r /tmp/internet-court-skill/vendored/jupiter/jupiter-vrfd .claude/skills/jupiter-vrfd
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Jupiter Vrfd in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Jupiter Vrfd on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Jupiter Vrfd is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Jupiter Token Verification

This skill routes agents through the public Jupiter token-verification flow for a Solana token mint.

Base URL: https://api.jup.ag Auth: 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

Triggers: verify token, submit verification, check eligibility, craft payment transaction, execute payment, pay for verification, update token metadata, metadata-only submission

Intent Router

User intentEndpointMethod
Check eligibility/tokens/v2/verify/express/check-eligibility?tokenId={TOKEN_ID}GET
Craft payment transaction/tokens/v2/verify/express/craft-txn?senderAddress={SENDER_ADDRESS}GET
Sign and execute payment/tokens/v2/verify/express/executePOST

Eligibility Decision Matrix

canVerifycanMetadataAction
truetrueverification+metadata (if user has metadata) or verification only
truefalseverification only, omit tokenMetadata
falsetruemetadata-only
falsefalseSTOP — show verificationError / metadataError to user

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

Agent Operating Rules

  • 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.

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

Resources

  • Jupiter Burn Multisig: 8gMBNeKwXaoNi9bhbVUWFt4Uc5aobL9PeYMXfYDMePE2
  • JUP Token Mint: JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN
  • Jupiter Docs: developers.jup.ag
  • Jupiter Verified: verified.jup.ag

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Jupiter Vrfd AI skill do?

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.

Why use Jupiter Vrfd on TypingMind?

Because you install it once and use it with any model. Jupiter Vrfd is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Jupiter Vrfd in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/internet-court/internet-court-skill/tree/main/vendored/jupiter/jupiter-vrfd. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Jupiter Vrfd?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Jupiter Vrfd?

As many as you like. As long as a model supports skills, you can use Jupiter Vrfd with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Jupiter Vrfd AI skill free?

Yes. It is published on GitHub by internet-court under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇