> For the complete documentation index, see [llms.txt](https://help.minted.network/minted-help-centre/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.minted.network/minted-help-centre/creators/royalties/collections-royalties-verification.md).

# Collections royalties verification

For both EIP-2981 and non-EIP2981 smart contract owners, you will be able to check whether royalties have been registered properly in this section.

1. Launch MintedExchange in your preferred web browser.
   * Click [here](https://explorer.cronos.org/address/0x55091b45E4a1bB494c52191323269C3A03893be7#code) for Cronos collections
   * Click [here](https://etherscan.io/address/0x55091b45E4a1bB494c52191323269C3A03893be7#readContract) for Ethereum collections
2. Select **Read Contract** and navigate to function `calculateRoyaltyFeeAndGetRecipent`<br>
3. Input the
   1. `collection (address):` Smart contract address
   2. `tokenid (uint256):` Any token ID (all token IDs have same royalties)
   3. `Amount(uint256):` NFT sale price
4. Once all the fields have been filled in, click **Query**. For example, 1,000 ETH/CRO in the `amount (uint256)` field and returns `uint256: 50`. This indicates that 50/1000 (5%) will be paid to the royalty’s recipient.

<br>


---

# 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://help.minted.network/minted-help-centre/creators/royalties/collections-royalties-verification.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.