> For the complete documentation index, see [llms.txt](https://kkone.gitbook.io/kkone-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kkone.gitbook.io/kkone-docs/auto-launch/token-metadata-and-links.md). # Token metadata and links KK.one uses the qualifying source post and detected narrative context to create one shared metadata snapshot for the concept. Each selected live network then receives its own independent deployment based on that snapshot. ## Coin name and ticker Coin name and ticker are automatically detected in V2. Manual editing is not available. The **Name & ticker case** setting changes capitalization only: * **Auto** — preserve the detected coin-name casing; keep the ticker uppercase. * **UPPERCASE** — force both values to uppercase. * **lowercase** — force both values to lowercase. It does not add, remove, or rewrite detected words, numbers, spaces, punctuation, or symbols. ## Description Descriptions are generated automatically from the source post, detected narrative keyword, and surrounding context. KK.one aims for a short readable description and avoids unsupported price, profit, or safety claims. Manual description editing is not available inside an Auto Launch Task in V2. After launch, a verified creator may edit supported metadata from Token Detail when Creator Tools makes that field available. Generated metadata can still be inaccurate. Review public output and use supported Creator Tools if a correction is available after launch. ## Image source The recommended policy is: 1. use a usable image from the source post; 2. if none is available, use the repost, quote, or triggering author's avatar. Other available rules may use the source post first with the original author's avatar as fallback, or use one configured author-avatar source only. Custom uploaded task-wide images are not available in V2. Rights in source images, avatars, names, and trademarks remain with their respective owners. Automated use does not imply endorsement. ## Website Choose: * **No website link**; or * **Use custom website** to apply the same valid `https://` or `http://` URL to every future token launched by the task. ## X / Twitter Choose: * **Use source post** (recommended); * **Use custom X link** for one validated `x.com` or `twitter.com` URL; or * **No X link**. Removing the public X link does not remove KK.one's internal source record where retention is lawful and necessary. ## Telegram Choose: * **No Telegram link**; or * **Use custom Telegram link** for one validated `t.me` or `telegram.me` URL applied to future tokens. ## Change boundary Metadata and link changes apply only to tokens launched after the updated task is saved. They do not alter a token that has already been deployed. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://kkone.gitbook.io/kkone-docs/auto-launch/token-metadata-and-links.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.