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

# Supported Assets

Sphera currently has five NFT collections on Hedera, all of which can be bridged to Avalanche via the [NFT Bridge](/nft-bridge/bridge.md) and traded on the [Marketplace](https://market.sphera.world).

## INO Collections

These three collections were launched via Sphera's Initial NFT Offering on Headstarter. Each NFT entitles the holder to a token airdrop equivalent to the amount stated on the NFT at Token Generation Event (TGE).

### Sphera Amateur

| Field               | Details                                               |
| ------------------- | ----------------------------------------------------- |
| **Supply**          | 250                                                   |
| **Hedera Token ID** | 0.0.4154809                                           |
| **TGE Airdrop**     | Yes — token amount equivalent to the value on the NFT |

### Sphera Fan

| Field               | Details                                               |
| ------------------- | ----------------------------------------------------- |
| **Supply**          | 250                                                   |
| **Hedera Token ID** | 0.0.4154815                                           |
| **TGE Airdrop**     | Yes — token amount equivalent to the value on the NFT |

### Sphera Ultras

| Field               | Details                                               |
| ------------------- | ----------------------------------------------------- |
| **Supply**          | 250                                                   |
| **Hedera Token ID** | 0.0.4154820                                           |
| **TGE Airdrop**     | Yes — token amount equivalent to the value on the NFT |

## Pass Collections

### Legacy Pass

| Field               | Details                                       |
| ------------------- | --------------------------------------------- |
| **Supply**          | 100                                           |
| **Hedera Token ID** | 0.0.5943132                                   |
| **Utility**         | Under consideration — details to be announced |

### Annual Pass

| Field               | Details                                       |
| ------------------- | --------------------------------------------- |
| **Supply**          | 100                                           |
| **Hedera Token ID** | 0.0.5943120                                   |
| **Utility**         | Under consideration — details to be announced |

## Viewing Your NFTs

* **On Hedera:** Search your account on [HashScan](https://hashscan.io)
* **On Avalanche:** Check the [Sphera Marketplace](https://market.sphera.world) or [Snowtrace](https://snowtrace.io)
* **Bridge interface:** Connect your wallet at [nftbridge.sphera.world](https://nftbridge.sphera.world)


---

# 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.sphera.world/supported-assets.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.