# Summary

[**Q1-2026:** Update regarding $BIST](https://bistroo.medium.com/update-regarding-bistroo-bist-22f7307c22a9)\
\
Nowadays, a majority of people have ordered food online. However, the food delivery & takeaway market is dominated by a few, heavily centralized players. These parties control large portions of the online food ordering volume, but at the same time charge fees as high as 14-45% for facilitating this service. Restaurants run at an average cost basis of 78-93% of the order value. When you do the math, this means that many restaurants run these online services, on which they now have come to depend for a lot of their traffic, at or near a loss.

Bistroo is a fully Software-as-a-Service based ecosystem for restaurants and their consumers. Together with the users, Bistroo is creating the biggest DePIN to connect restaurants directly with their customers.&#x20;

This saves restaurants time, money and frustration. Restaurants can now digitally serve their customers at significantly lower fees and receive instant payouts. The ecosystem allows them to be in full control of their digital presence. Both customers and merchants can earn rewards by contributing to the BIST ecosystem or access protocol services against significantly reduced fees. Bistroo in turn will direct revenue generated by the platform's services to invest back into the $BIST Ecosystem.

<figure><img src="/files/6AOVT1im8h6wURHp0CIj" 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://bistroo.gitbook.io/bistroo-litepaper/summary.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.