# Businese Model

In the beginning, we had no idea we would need to create a business model for this project. This necessity quickly became apparent after our decision to build a decentralized sports book; after all, to effectively operate a service that handles the transfer of other people’s money, that service will need to sustain its own endeavors as well. By coincidence, as our operational designs evolved, a simple and clear business approach emerged. The diagram below pictures the fundamental connections OpenBook maintains with its different users and the primary value transfers that occur between each:

![](https://lh4.googleusercontent.com/ADvJxICcKrABjKbeZn3quKtxn5074QRrL4PAFuxgTv6RXhyN4Ei2Qoo3nMYo5-ceMw1ouuR1eALl2xpuMVbJTDstyV-Lz5bEoJ_9qLFXLiArMXIyxNC6OVnf1V1pUhsw1UOeYCQNmV6t3MOS)

Our choice to fuse the current centralized and decentralized sports book standards left us with a litany of directions to choose in service of sustaining OpenBook’s activities. All the same, we felt the best option was a simple one that removed the predatory quality of centralized profit patterns.


---

# 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://openbook.gitbook.io/copy-of-openbook-whitepaper/business-model/businese-model.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.