> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/community/chiliz-chain-ecosystem/developer-tools/rarible.md).

# Rarible

Rarible multichain NFT protocol integrated with Chiliz Chain: SDK for minting, sell orders, royalty enforcement, and real-time NFT data for SportFi dApps.

## What is Rarible?

[Rarible](https://rarible.com/) is an Ethereum-based platform that facilitates the creation, sale, and purchase of ownership rights to digital works of art via non-fungible tokens (NFTs).

## What this means for you

With Chiliz Chain's integration on Rarible, SportFi dApps, wallets, and marketplaces can gain real-time access to NFT data. Rarible decentralized toolkit allows users to interact with multiple features, including multi-chain aggregation, enforced NFT royalties, and fast-indexing.

By leveraging Rarible's Multichain SDK, developers can seamlessly query, issue, and trade NFTs on the Chiliz Chain.


---

# 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://docs.chiliz.com/community/chiliz-chain-ecosystem/developer-tools/rarible.md?ask=<question>&goal=<user_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.
