> For the complete documentation index, see [llms.txt](https://docs.closed.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.closed.digital/readme.md). # Welcome to Closed Digital ## The Only Launchpad That Thinks of You Closed Digital is different. We check every creator before they launch. We protect every trade from bots. We say NO to bad projects so you don't have to worry about getting rugged. *** ## What Makes Us Different ### **Bot-Free Trading** No bots can trade for the first 15 minutes on our biggest launches. Only real people get to buy early. ### **Verified Creators** Every creator gets checked before approval. Real people behind every token. No anonymous launches. ### **Weekly Big Events** Every Friday we launch one massive token designed to go viral. Big influencers, big community, big potential. ### **Safe Environment** Clear migration rules. Locked liquidity. No rug pulls in our history. *** ## Choose Your Path ### **I Want to Launch a Token** → [See how to launch](/for-creators/launch-process.md) ### **I Want to Trade Tokens** → [Start trading safely](/for-traders/getting-started.md) ### **Tell Me About Weekly Drops** → [Token of the Week explained](/for-creators/token-of-week.md) ### **I Have Questions** → [Check out FAQs](/faq/common-questions.md) *** *Where creators get verified and traders stay safe.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.closed.digital/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.