> For the complete documentation index, see [llms.txt](https://blastr.gitbook.io/blastr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blastr.gitbook.io/blastr/nft-features/overview.md).

# Overview

**Your Own Smart Contract:** Every NFT collection you start on BLASTR gets its own ERC721 smart contract on the blockchain. This non-custodial approach ensures that you, and only you, manage your collections's funds and decisions.

**Security Comes First:** We take the safety of your NFTs seriously. BLASTR is not just reliable; it's also been thoroughly audited and approved by top security experts like @0xQuit. We follow the highest security standards to keep everything safe and sound.

**For All Kinds of Projects:** BLASTR is versatile. Whether you're setting up a DAO, launching an app with NFT access, creating a collection of digital art, or fundraising for an event, BLASTR fits right in with what you need.


---

# 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://blastr.gitbook.io/blastr/nft-features/overview.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.