How to Get a Token Verified on Jupiter

Jupiter token verification adds a green checkmark that identifies the canonical token mint. It helps traders distinguish the intended token from copies, and Jupiter's verified data layer is used by wallets, DEXs, screeners, and other Solana apps. The checkmark is not an endorsement of the project or team, and it is not a safety guarantee.

Verification is also separate from tradability. Jupiter says an unverified token can still be traded when its pools have sufficient liquidity on integrated DEXs. If your immediate problem is that a token cannot be found or swapped, check the pool and token data before treating verification as the fix.

What Verification Means

Jupiter VRFD is the current portal for token verification, metadata updates, community content, and token information. The verified state answers a narrow but important question: is this the canonical mint for the token people are trying to find?

That distinction matters on Solana because anyone can create a token and reuse a familiar name or ticker. A checkmark reduces address confusion, but it does not certify the code, promise liquidity, approve the team, or predict performance. Jupiter also says verified tags can be removed later, including when a token's trading activity becomes too low for the list to remain useful.

Older articles may call this the Jupiter strict list or describe several badge tiers. Current Jupiter documentation uses the verified tag for verification queries, while an API example can still contain a strict tag. Treat “strict list” as legacy search language, not as the name of the current application lane.

Review Signals

Jupiter does not publish fixed minimums for approval in its current verification FAQ. The review is holistic. The listed signals are market cap, Organic Score, token holders, ticker uniqueness, onchain liquidity, and social support measured through smart social signals.

Organic Score combines organic volume, organic holders, organic traders, and organic buyers. Jupiter describes it as relative rather than absolute: it compares activity across the ecosystem instead of proving that a token has reached one universal target. Early organic growth has more effect than the same numerical increase at a much larger scale, and Jupiter recommends using the raw score instead of relying only on broad labels such as high, medium, or low.

Common rejection reasons in the official FAQ include a token duplicating another token, low trading activity, and insufficient social proof. Those are review patterns, not a complete formula. Avoid legacy claims such as a $100,000 market-cap minimum, 500 holders, a 21-day age requirement, or $10,000 in daily volume. Jupiter does not publish those cutoffs in the current VRFD criteria.

How to Submit

Start at the official portal rather than a third-party form. Search for the token by mint, review the token record, and make sure the project points users to the same mint everywhere. Prepare the official website and social links, a clear reason for the request, and any context that helps a reviewer distinguish the canonical token from duplicates.

1. Confirm the mint. Copy the Solana mint address from a trusted project source and compare it with the token record in VRFD.
2. Check public information. Make sure the token name, ticker, icon, website, and official social links are accurate. Metadata updates and verification are reviewed independently.
3. Choose a lane. Standard submissions on the VRFD site are free. Express is a paid priority-review lane.
4. Submit through VRFD. Sign in, select token verification, provide the requested token and project context, then review the transaction or submission details before confirming.
5. Track the request. Use the public Submissions page to check pending, approved, or rejected status.

Jupiter's current Express API documentation lists the cost as 1,000 JUP. Payment can be made in JUP or in SOL, USDC, or JUPUSD converted to 1,000 JUP through Jupiter Ultra. The VRFD FAQ says Express prioritizes review within 24–48 hours. It does not guarantee approval, and the same review criteria still apply.

Do not describe the Express payment as a burn unless Jupiter explicitly restores that wording in a current first-party source. Before paying, verify the amount and available payment currency in the live flow because costs and payment options are mutable.

After a Rejection

A rejection does not necessarily make the token untradable. Jupiter says it can surface unverified tokens when integrated pools have sufficient liquidity, using text similarity, volume, and liquidity to help order search results. Display the mint address prominently on the project's website so users can verify the correct token even without a checkmark.

Review the rejection against the current signals rather than chasing an unofficial threshold. Check for duplicate naming, weak or unstable trading activity, incomplete token information, thin onchain liquidity, and limited credible social context. If important context was missed, Jupiter directs projects to open a support ticket at support.jup.ag.

PandaBoost does not sell Jupiter verification, influence VRFD reviewers, or guarantee approval. This is an educational guide for launch teams. For broader token-launch preparation, use the PandaBoost Launch guides; keep the verification submission itself inside Jupiter's official portal.

FAQ