> For the complete documentation index, see [llms.txt](https://wiki.apexcobblemon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.apexcobblemon.com/features/pokemon/pokedex.md). # PokéDex The **PokéDex** keeps track of all the Pokémon you've caught. **Normal**, **Shiny**, **Exotic** and **Legendary** Pokémon are each tracked and rewarded separately, as well as a **Living** PokéDex for true collectors. The first time the **base form** of a Pokémon is obtained, it's PokéDex entry will be saved automatically, even if the Pokémon is not kept after (with the exception of the [Living PokéDex](#living-pokedex)). | Command | Description | | :------------: | :---------------------: | | `/dex` | Opens the PokéDex menu | | `/livingvault` | Opens your Living Vault | | `/badges` | Opens your Badge menu |

## Living Pok**éDex** The **Living** PokéDex requires you to actively possess the base form of each Pokémon. The Pokémon can be in your **Living Vault** or **PC** but if the Pokémon is **sold**, **traded** or **released** you will **lose** the entry. {% hint style="info" %} Store Pokémon in your `/livingvault` to save space in your PC {% endhint %} ## Pok**éDex Badge Rewards** [PokéDex Badges](/features/player/badges.md#pokedex-badges) are unlocked upon reaching specific milestones, which grant powerful rewards and ![:trophy\_red:](https://cdn.discordapp.com/emojis/1460032517775298821.webp?size=40)**Skill Trophies**.

Normal PokéDex

Badge Tier	Requirement	Trophies	Rewards
I	88	30	15k
II	222	40	25k Cosmetic Key
III	293	50	45k Shiny Key
IV	355	70	60k Cosmetic Key Master Ball
V	444	95	125k Shiny Key
VI	666	125	100k Shiny Key Ultra Key
VII	800	170	125k Cosmetic Key Shiny Key
VIII	889	220	150k Cosmetic Key Shiny Key Dex Master Title Random Shiny Legendary

Shiny PokéDex

Badge Tier	Requirement	Trophies	Rewards
I	94	60	50k Cosmetic Key
II	236	80	75k Ultra Key
III	312	105	100k Shiny Key
IV	378	140	125k Cosmetic Key
V	473	185	150k 2x Shiny Key
VI	709	250	175k Cosmetic Key Shiny Key
VII	851	335	250k 2x Ultra Key Shiny Key Random Legendary
VIII	946	445	500k 2x Cosmetic Key 2x Shiny Key ShinyDexMaster Title 2x Random Shiny Legendary

Exotic PokéDex

Badge Tier	Requirement	Trophies
I	5	15
II	12	20
III	16	25
IV	20	35
V	25	50
VI	38	60
VII	45	85
VIII	50	110

Living PokéDex

Badge Tier	Requirement	Trophies	Rewards	Boosts
I	94	45	20k
II	236	60	40k Cosmetic Key
III	312	80	60k Shiny Key
IV	378	105	80k 1x Shiny Key 1x Cosmetic Key
V	473	140	100k Ultra Key
VI	756	185	200k Shiny Key Cosmetic Key	+5% Shiny Boost
VII	898	250	400k 2x Shiny Key 2x Ultra Key Legend Key	+15% Shiny Boost
VIII	946	335	600k 2x Shiny Key 2x Cosmetic Key LivingDexMaster Title GameChanger Title Random Shiny Legendary	+10% Breeding Rate Boost +10% Apex Boss Boost +10% Rare Spawn Boost +15% HA Boost +20% Shiny Boost

Legendary PokéDex

Badge Tier	Requirement	Trophies
I	5	30
II	14	40
III	18	50
IV	22	70
V	28	95
VI	42	125
VII	51	170
VIII	57	220

--- # 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://wiki.apexcobblemon.com/features/pokemon/pokedex.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.