Jupiter Strict List: Current Token Verification Guide

If you are searching for the Jupiter strict list, use Jupiter's current VRFD verification process. The old GitHub token-list application steps are historical. Jupiter's Tokens API overview describes the transition from earlier registries and community lists to its current verification system.

This guide answers how to check a Solana token's status and submit a verification request. It does not treat token creation, swap availability, and a verification label as one operation.

Which result are you trying to achieve?

A token appearing in search answers only the first question. A pending application answers none of the others by itself.

Step 1: check the exact mint

Open Jupiter VRFD and look up your mint. Record the status and check that the project links identify your token, rather than another token with the same symbol.

For developers, Jupiter documents a read-only search request with an API key in its token-information guide:

curl --fail --silent --show-error \
  'https://api.jup.ag/tokens/v2/search?query=YOUR_MINT_ADDRESS' \
  -H 'x-api-key: YOUR_API_KEY'

Match the returned token's ID to your mint before using its fields. Inspect verification, metadata, and any available audit fields separately. Missing values should remain unknown in your interface; they should not become reassuring default labels.

Step 2: choose standard or Express submission

As checked on September 6, 2026, Jupiter's Express Verification documentation states:

The documentation allows metadata and verification requests together, but says they are reviewed independently. A metadata update can therefore have a different outcome from verification.

Prepare the correct mint, project links, and a factual reason for the request. Follow the current form's requirements and explain any inconsistent information before submitting. Paying for Express purchases the submission flow; it does not establish approval.

For API integrations, check eligibility first, retain the request identifier, and distinguish successful payment execution from the later review outcome. There is no reason to reproduce an old GitHub JSON edit when the current service provides a dedicated flow.

Step 3: follow the review result

Save your submission details and use VRFD's token browser to track progress. If a request is already pending, inspect its status instead of creating duplicate submissions.

If you receive a rejection, address the stated reason. Neither a guessed holder threshold nor a newly purchased social account establishes eligibility. This guide does not promise approval in a fixed number of days because the reviewed documentation does not provide that guarantee.

Verification, Organic Score, and swap routes answer different questions

Jupiter describes Organic Score as a relative measure of trading activity. A score of 80 should not be interpreted as an 80% probability of safety or success. Verification and suspicious-token flags also need their own interpretation. See the current field definitions.

For tradability, check an actual quote. The amount and route matter: a token can appear in metadata search while the trade you want has no usable route. Jupiter's quote documentation describes the inputs and routing response. An old quote is not a commitment to fill a later transaction.

For wallet display, verify the result in the wallet itself. A platform using Jupiter data can still apply its own caching, filters, and warning messages.

Troubleshooting a request

If you have not created the token yet, start with the Solana token creator and keep its mint address. Creation gives you the asset to identify in these systems; external verification remains a later, separate step.

Frequently asked questions

Is the Jupiter strict list still the application process?

The name comes from earlier token-list systems. Jupiter now directs token verification through VRFD. Older GitHub pull-request tutorials should not be treated as the current submission procedure.

Does Jupiter verification cost money?

Jupiter's documentation says standard VRFD submissions are free. As checked on September 6, 2026, Express submissions cost 1,000 JUP. Check the current terms before submitting.

Does a successful Express payment mean my token is verified?

No. Payment and successful submission create a request. The review result and the token's verification status must be checked separately.

Does verification guarantee my token can be swapped?

Verification status and a usable swap route are separate checks. Test a current quote for the exact mint, amount, and destination asset.

Will Jupiter verification remove every Phantom warning?

Do not assume that result. Wallets control their own presentation, risk checks, and refresh behavior. Check the wallet's current status separately.