> For the complete documentation index, see [llms.txt](https://doc.cryptostone.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.cryptostone.org/crypto-stone/crypto-stone-wp-cn/xi-you-du-yu-shou-cang/32-xi-you-du-deng-ji-jie-gou.md).

# 32. 稀有度等级结构

CryptoStone 将 Rarity Score 解释为最终等级体系。

| Tier      | Rarity Score Range | 解释              | 定位                     |
| --------- | ------------------ | --------------- | ---------------------- |
| Common    | 0 \~ 34            | 以普通属性为主         | 最常见的宝石群，形成基础收藏层与精炼材料   |
| Rare      | 35 \~ 50           | 包含部分上级属性        | 比普通挖矿结果更稀有的中间收藏层       |
| Epic      | 51 \~ 74           | 两个以上上级属性或高分组合   | 用户可感知为有意义成功的高等级宝石      |
| Legendary | 75 \~ 89           | 三个以上上级属性或非常高的分数 | 非常稀有的宝石，形成高价值收藏区间      |
| Genesis   | 90 \~ 100          | 极端属性组合与最高分      | 顶级收藏资产，追加发行与精炼生成应被严格限制 |

Genesis Tier 并不是由单一属性决定的。只有极低概率的 Weight、Color、Clarity、Cut 组合与矿池供应修正值共同作用时，才应被解释为可到达的最高等级。

稀有度统一为 Common、Rare、Epic、Legendary、Genesis 五个等级。个别属性说明中出现的稀有区间，也应最终在这五级最终 Gem NFT 等级体系中解释；Mythic、Ancient、Uncommon 等单独等级不作为最终 Gem NFT 等级使用。


---

# 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://doc.cryptostone.org/crypto-stone/crypto-stone-wp-cn/xi-you-du-yu-shou-cang/32-xi-you-du-deng-ji-jie-gou.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.