Before booking, check these 7 project inputs
Hours or days set each platform's review window. Your preparation starts with the project record. A 7-point check catches mismatched details before requests go out. Send what you have and flag anything needing confirmation.
- Identity: official project name, token name and symbol.
- Network: the correct chain and contract address.
- Official links: website and active project channels.
- Description: current wording about the token or product.
- Assets: logo files and available profile materials.
- Evidence: documents supporting supply figures or other claims.
- Existing records: profile links, known errors or old details.
We compare these inputs before submission. We flag conflicts, duplicate records and outdated links.
For CoinGecko supply requests, review the circulating supply verification route. For a changed contract or identity, include migration and rebranding updates.
This review gives your team one approved version of project facts. Use it across the destination list.
Which listing surface fits the user task?
4 destination types serve different user tasks. Aggregators help users compare project records. Explorers display on-chain token details. Wallets show token identity in a portfolio context. Exchanges handle a separate application process.
Start with the action your audience needs. Then choose a matching surface:
- Discovery: assess CoinMarketCap and CoinGecko records.
- On-chain checks: identify where users inspect the token and contract.
- Wallet display: check names, symbols and visual identity against official materials.
- Exchange access: keep exchange applications apart from data-platform submissions.
A useful destination list explains why each request matters. It names the record, the requested action and the person approving the information.
Add other crypto tracker listings when those platforms fit your audience. This keeps the list focused. Each request has a reason, instead of simply adding every available directory.
4 surfaces, 4 different request formats
4 surfaces call for different request materials. We map each destination, current record, requested action and available evidence. The table is a working checklist. It does not predict platform review times.
| Surface | What it is | Window | What you send |
|---|---|---|---|
| Aggregator | Public token record | Platform review | Contract, official links, project details |
| Explorer | On-chain token information | Platform review | Contract, network, verified profile details |
| Wallet | Token name and logo display | Platform review | Token identity, logo files, official links |
| Exchange | Separate listing application | Platform review | Project pack and requested application materials |
A new listing, an update and a correction are different requests. For a DEXTools or DEXScreener profile update, send the current profile link. Name the exact fields to change.
A missing record needs a separate destination request. Exchange work stays distinct. See centralized exchange listing support.
We record each request type. Your team can see what we prepare and why.
5 checks from first message to final report
5 checks keep listing work visible from intake to close. We confirm project facts with you before requests go out. Then we log each destination separately.
- Intake: send the contract, network, official links and target platforms.
- Review: we compare current records with your approved project facts.
- Confirmation: you approve the destination list and request details.
- Submission: work starts within 24 hours of confirmed payment. We log requests and report activity daily while a placement is live.
- Closeout: you receive a final report with links and screenshots within 2 working days of the window's end.
The written quote names the agreed work before payment. For listing issues, the report shows the destination and request status. It also shows visible profile changes and next actions.
A CoinMarketCap community verification request stays separate from a supply request. These are different review tasks, with separate status records.
What does the platform decide after submission?
The platform decides whether to approve a listing, change its record or display the profile. Its review timing and final status are outside our control. We promise the agreed preparation, submissions, follow-up and report.
We check what your team can inspect: the request sent, replies received and public profile changes. If a platform asks for more evidence, we log the question.
Then we identify project materials that could answer it. Your report shows a clear next action. It does not present a pending request as an approval.
For existing errors, listing profile remediation is the relevant route. For a broader destination mix, compare DefiLlama and DappRadar listings with your audience's needs.
Send us the token page, network, contract address, target platforms and current profile links. We will review the pack and return a written quote.
Frequently asked questions
Can one project pack cover several listing platforms?
1 reviewed project pack can support several requests when project facts match. Send the network, contract address, official links and target platforms. We map each destination separately, then flag any platform-specific materials still needed. You approve the details before we prepare the requests. Each platform keeps its own request record.
What should I send for a token profile correction?
2 items make the correction clear: the profile link and the exact detail needing a change. Add current project facts and any evidence supporting the correction. We check whether the issue needs an update request or a separate listing request. Then we prepare the appropriate next step.
How is a supply verification request different from a listing?
A supply request documents a specific figure; a listing creates or updates a project record. Send the figures your team can support and the profile they relate to. We identify the evidence needed for circulating supply verification. That keeps supply questions distinct from other listing work.
Can you update records after a token migration?
A migration needs a record-by-record check. Send the old and current contract details, network, official links and affected profile pages. We map destinations needing updates and prepare requests using current approved information. The migration and rebranding route covers this work.
How long until a listing or profile change appears?
The platform controls its review window and when an approved change becomes visible. Our work starts after payment is confirmed. We log submitted requests separately from platform replies and visible updates. Your report shows the actual status, not a submission presented as an approval.
Can you guarantee a platform will approve a token listing?
No. Each platform decides whether to accept a submission, change a record or display a profile. We prepare and send the agreed materials, follow up and check visible changes. Your report includes links and screenshots for results we can verify publicly.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…