> For the complete documentation index, see [llms.txt](https://stead.gitbook.io/stead/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stead.gitbook.io/stead/how-to-list-a-property.md).
# How to List a Property
Individuals and groups must first be approved before they can list their own floating properties / assets.
Once approved, they will become an Operator, as discussed on the previous page, Operators can now list properties to be approved on the marketplace, and once receiving sufficient funding, can withdraw their funds to construct or purchase their floating asset.
In order to list an asset in the marketplace to receive funding, you must first disclose your financial capability, whether with traditional assets and income or crypto, and then sign legal agreements to abide by the terms of the Stead platform. At listing time, an additional 5% of the total amount of tokens will be generated for the Stead Platform as a listing fee, this will be included in the amount to be bought back and burned. This listing fee may be different for different amounts, to compensate for the higher risk implied in low capital loans.
---
# 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://stead.gitbook.io/stead/how-to-list-a-property.md?ask=&goal=
```
`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.