> For the complete documentation index, see [llms.txt](https://docs.blocksquare.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blocksquare.io/faq/general-questions/other.md).

# Other

<details>

<summary>Can you provide references from other clients who have used your platform?</summary>

We work with numerous companies across the world to help them achieve their goals of opening up a marketplace and offering tokenized real estate deals to their investor base.

Our list of clients is ever expanding, but some of the companies we have worked with include Bricktrade (UK), Bravo (Brazil), HeroX (AU), Arms & McGregor (UAE), Tokeniza (Spain), Terramint (USA), Lumifund (Netherlands), MLT (Poland), T-Blocks (UK)...

</details>

<details>

<summary>What is your pricing model and what does it include?</summary>

Access and use of our real estate tokenization infrastructure is possible through the purchase of a on-time software license.

To accommodate businesses at any growth stage, we also offer monthly plans to acquire the software license throughout multiple instalments.

Once access to the protocol and platform is granted, costs of operating a marketplace are based on usage.

Please refer to the [Pricing](/certified-partners/pricing.md) section to see our latest fee schedules.

</details>


---

# 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.blocksquare.io/faq/general-questions/other.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.