> For the complete documentation index, see [llms.txt](https://docs.bueno.art/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bueno.art/generator/curating-your-collection/rarity/how-bueno-calculates-rarity.md).

# How Bueno Calculates Rarity

Bueno uses two popular methods for calculating the rarity of an NFT, **Rarity Score** and **Average Trait Rarity**. Understanding these methods will help you determine  the uniqueness of each NFT in your collection.

## Rarity Score

**Rarity scoring** is a straightforward and dependable method for assessing the rarity of an NFT. The rarity score for a token is the sum of trait scores:

**`Trait Rarity Score`**` ``= 1 / ([Number of Items with that Trait Value] / [Total Number of Items in Collection])`

This simple calculation gives consistent results for many NFT collection and serves as the basis for rarity rankings on several NFT platforms, including popular marketplaces.

## Average Trait Rarity

**Average trait rarity** is another way to calculate NFT rarity. This method is better suited for collections that have tokens containing a varying numbers of total traits. It works by **averaging the rarity score of its individual traits.**

For example, if an NFT possesses 2 traits:

* Trait A = 50%
* Trait B  = 10%

The average trait rarity would be: `(50+10) / 2 = 30%`

However, a common drawback with this approach is that it places considerable emphasis on the *combined* rarity of all traits, potentially undervaluing an exceptionally rare *single* trait, and causing the overall rarity value to be diluted by less rare traits. 

## Rarity Rank

The Rarity Rank for a token is simply how unique that NFT is relative to the collection. A rarity rank of 1 means that NFT is the most rare.

{% hint style="info" %}
When determining the **rarity rank** of a token, the **rarity score** is used.
{% endhint %}


---

# 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://docs.bueno.art/generator/curating-your-collection/rarity/how-bueno-calculates-rarity.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.