> For the complete documentation index, see [llms.txt](https://blocks-1.gitbook.io/blocks/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blocks-1.gitbook.io/blocks/verified-by-blocks/verification-and-registry-pricing.md).

# Verification and Registry Pricing

BLOCKS DAO is currently offering its proprietary verification service at no cost for partners. The fee schedule will become active once we verify 200K NFTs and have implemented the technical process of updating existing verifications.

### Pricing for NFT Collections:

* The fee for NFT verifications is 1 ETH per 10,000 NFT Collection\*
* This base fee is prorated for smaller NFT Collections
* There may also be alternative packages and pricing depending on volume and add-ons (i.e. marketing/promotional agreements)

###  Pricing for Business and Government Use Cases:

* Transactional based pricing is negotiated per partner based on volume
* The base rate per transaction is currently set per network as follows (based on API credit deductions)\*

| Ethereum | 100 BLOCKS |
| -------- | ---------- |
| Fantom   | 5 BLOCKS   |
| Binance  | 2 BLOCKS   |
| Polygon  | 1 BLOCKS   |
| Gnosis   | 1 BLOCKS   |
| Celo     | 1 BLOCKS   |

 

\*Rates are subject to change, based on the dynamic value of BLOCKS and Ethereum


---

# 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://blocks-1.gitbook.io/blocks/verified-by-blocks/verification-and-registry-pricing.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.