# Getting ready for tokenisation

{% hint style="info" %}
🚧 Our tokenisation feature is still under development and testing 🚧
{% endhint %}

Here is a sneak peak! 

Tokenisation in Carbon Central is flexible and dynamic. We allow easy customisation to suit your specific needs. We support two main approaches to tokenisation (linked to your digital twin configuration):

1. **Manual Tokenisation**: This is used for standards/methodologies that require grouped or batch information such as a vintage year or production month. The batch finalisation block serves as the last step before tokenisation. It enables users to merge all data and information from their digital twin using a set of rules. Batch finalisation is utilised as the manual final approval prior to token minting and aggregates all data that has been stored on-chain using the digital twin into your tokens.
2. **Real-time Tokenisation**: Automatic tokenisation based on a set of business rules. For example, you can set a rule to "mint 1 guarantee of origin token for every kg of Hydrogen produced" based on meter data. Once set up, Carbon Central will continuously generate tokens using these business rules from digital twin data. In most cases, automated tokenisation will still require batch information (such as sources of electricity, co products, etc).  A batch finalisation block can be used to include additional information to tokens that were minted in real-time by linking up additional data.

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


---

# Agent Instructions: 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:

```
GET https://docs.carboncentral.app/knowledge-base/getting-started/getting-ready-for-tokenisation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.