> For the complete documentation index, see [llms.txt](https://docs.fractise.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fractise.xyz/readme.md).

# Welcome to Fractise

## Introduction

Fractise is a blockchain-based platform revolutionizing asset ownership by enabling fractionalization of high-value assets. Starting with real estate, we now aim to expand into multiple asset categories, including luxury assets, entertainment and media, infrastructure projects, collectibles, commodities, technology and innovation, private jets/yachts, gaming, and metaverse. By leveraging decentralized technology, Fractise offers a transparent, secure, and accessible way for individuals to co-own and invest in valuable assets without the traditional barriers of high entry costs or exclusivity.

## Our Vision

Democratizing access to high-value real-world and digital assets by enabling secure, efficient, and scalable fractional ownership.

## Our Mission

To create a multi-asset fractionalization platform that empowers users to invest in diverse asset classes—from real estate to gaming and metaverse items—using blockchain technology for transparency and trust.

<br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fractise.xyz/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.