Jupiter and Raydium token visibility, from application to review

Which Jupiter or Raydium application track fits?

2 tracks, one working plan. The first review separates the platform requests and checks token details. Choose Jupiter if that is the platform you want to approach; choose Raydium if that is your priority. Use both rows when you want support with both applications.

Listing applications and verified-status requests are related, but distinct. Tell us which work you need for each platform. We confirm the application path and prepare the relevant materials. For a wider view of platform options, see listings and verification.

This service suits Solana token teams with current public project information. A team member must be available to confirm it. If the immediate need is DEX listing or liquidity setup, review DEX listing and liquidity setup as a separate workstream. Jupiter and Raydium application support does not replace that work.

5 moves from project details to platform follow-up

5 moves keep the application work visible. We track Jupiter and Raydium separately. Each platform has a clear status and next action.

1. Confirm the platform or platforms and the requested work.
2. Collect current project details, official links, and existing correspondence.
3. Check the materials for gaps, inconsistencies, and open questions.
4. Prepare the application information and coordinate submission.
5. Track responses, organize follow-up, and send status updates.

Your team confirms project facts and approves wording where needed. We manage the preparation and coordination around those inputs. Work starts within 24 hours of confirmed payment, once the agreed application work is clear.

Keep other profile changes separate from these applications. For existing DEXTools or DEXScreener profiles, see DEXTools and DEXScreener profile updates. For token details shown by an explorer, review explorer token information and logo updates. Those are distinct tasks, not steps in a Jupiter or Raydium application.

6 inputs we need for the first review

6 inputs give us a workable starting point. Send the latest public information, not an old collection of files. That helps us spot conflicts before preparing an application.

• Token identifier: the identifier your team uses for the token.
• Project name: the name shown in current public materials.
• Official links: current destinations controlled by the project.
• Project description: a concise account of what the project does.
• Application record: any existing submission status or platform correspondence.
• Project contact: the person who can confirm facts and approve wording.

We check names, links, and descriptions against the information you send. If details conflict, we flag the exact question for your team. You resolve factual gaps before submission; we organize the materials and check them for consistency.

A Jupiter or Raydium application is not a CoinMarketCap or CoinGecko submission. If those tracker applications are also on your list, review CoinMarketCap listing support and CoinGecko listing support. Each request is handled as its own platform track.

What sets the Jupiter and Raydium review window?

3 timing points shape the work: preparation, submission coordination, and platform review. We set the working schedule after checking your materials and the applicable application path.

The schedule is more useful once we know whether the materials are ready. If the platform asks for clarification, your project contact confirms the facts. They also approve any response. We keep the current status clear, including which platform has an open action.

For projects also working on broader tracker coverage, other crypto tracker listings can be planned as separate applications. This helps your team keep each submission, response, and follow-up in the right record.

2 editorial teams make the final listing decisions

2 platform editorial teams make the final decisions on listings and verified status. We prepare the agreed materials and coordinate application work. We also report each platform’s status. Neither team’s decision is ours to make.

• Jupiter review: approval and verified status remain Jupiter’s decision.
• Raydium review: approval and verified status remain Raydium’s decision.
• Criteria: each platform may change its review criteria.

Treat an application as pending until the platform confirms an outcome. A changed token identity may need a correction to existing public information. Check contract migration and rebranding updates before treating that as a new application. The report keeps completed work separate from pending platform decisions.

For kickoff, send the token identifier, project name, official links, and current application messages. Name the person who can confirm project details. DigitalMedia1 will review the materials and return a written quote. You’ll receive it within 2 working days.

How it works

1. Confirm the 2 platform tracksTell us whether you need Jupiter, Raydium, or both. Specify listing applications, verified-status requests, or both.
2. Send current project detailsShare the token identifier, official links, project description, and any application correspondence. Name a contact who can confirm facts.
3. Review materialsWe check for missing details, conflicting information, and questions to resolve. Your team confirms project facts before submission.
4. Prepare and coordinateWe organize the application information and manage the agreed submission work for each platform.
5. Track status and follow upYou receive status updates that separate Jupiter from Raydium. We organize follow-up when a response or clarification is needed.