> For the complete documentation index, see [llms.txt](https://docs.spydra.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spydra.app/how-to/public-chain/create-a-token/define-your-token.md).

# Define your token

Defining your token is a crucial step in tokenizing a real-world asset. This process involves setting specific attributes that will determine how your token functions and is traded. Follow this guide to properly define your token:

#### 1. Essential Token Attributes

* **Token Name:** Choose a unique and descriptive name for your token. This name should be easily recognizable and related to your asset.
* **Token Symbol:** Create a short, memorable symbol (usually 3-5 letters) for your token. This will be used for quick reference in trading.
* **Token Icon (optional):** Upload a distinctive icon that visually represents your token. This helps in brand recognition.
* **Token Price:** Set the initial price for your token. This should reflect the value of the fractional asset it represents.
* **Maximum Token Supply:** Determine the total number of tokens that will be created. This is often based on the total value of the asset divided by the price per token.


---

# 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://docs.spydra.app/how-to/public-chain/create-a-token/define-your-token.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.