> For the complete documentation index, see [llms.txt](https://gokiburi.gitbook.io/gokiburi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gokiburi.gitbook.io/gokiburi-docs/rare-specimens.md).

# Rare 1/1 Specimens

Eight token IDs identify named 1/1 specimens. They use a dedicated renderer so they can break the Common visual language without forcing every asset into a single oversized contract.

For the planned production mint, all eight Rare IDs will be included in the random Public pool. They are not part of the Owner reserve, and the Owner will not be able to select their recipients.

Every named specimen reports:

* `Rarity Class: Rare`
* `Edition: 1/1`

## Named specimens

| Token | Name        | Identity                  |
| ----- | ----------- | ------------------------- |
| #1    | GENESIS G   | Cyan origin core          |
| #9    | RED COMET G | Scarlet impact trail      |
| #404  | NOT FOUND G | Unstable glitch body      |
| #666  | ZOMBIE G    | Severed undead specimen   |
| #777  | GOLDEN G    | Crowned solar specimen    |
| #1337 | CYBER G     | Circuit scan specimen     |
| #2140 | HODL G      | Last-block Bitcoin holder |
| #4096 | MOTHER G    | Colossal brood source     |

![ZOMBIE G](/files/Fa2eulqfW2YmwHonFGSf)

![MOTHER G](/files/BsAoE5JMPiGCY8T40J7y)

Rare artwork is still generated on-chain. The separate renderer is an implementation boundary, not an off-chain exception.

See [Mint Allocation](/gokiburi-docs/allocation.md) for the planned Public and Owner allocation.


---

# 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://gokiburi.gitbook.io/gokiburi-docs/rare-specimens.md?ask=<question>&goal=<endgoal>
```

`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.