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

# Tokenization

<figure><img src="/files/MTBg6t1lK2SoV78t4uo8" alt=""><figcaption></figcaption></figure>

Once your agent is built visually or through prompts, Botify turns it into a blockchain-based token, making it ownable and tradable.

Here’s how tokenization works:

* **Automatic Minting**: When you finalize your agent, Botify mints it as an **SPL NFT** (or semi-fungible token, depending on use case) on the Solana blockchain. This creates a digital certificate of ownership tied to your wallet.
* **Embedded Metadata**: Your token isn’t just a shell, it contains everything buyers need to know:
  * Agent name and category
  * Version number
  * Creator ID
  * Capabilities and licensing terms
* **Ownership You Can Prove**: As the creator, your wallet address is permanently linked to that agent. Even if someone buys, rents, or lists it elsewhere, the record of origin is always verifiable.
* **Licensing via Smart Contracts**: Tokens carry embedded rules for usage. Want to offer reusable bots, time-limited trials, or single-access licensing? Smart contracts write all of that into the token’s logic.
* **Upgradeable and Versioned**: Need to roll out an update? No problem. Botify lets you push new versions while maintaining a transparent history of past builds, giving users trust and giving you flexibility.

Tokenization turns your bots into digital products with **real-world value**, protected by blockchain and ready to sell, scale, and grow.


---

# 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://botify-cloud.gitbook.io/docs/core-features/tokenization.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.