> For the complete documentation index, see [llms.txt](https://docs.roboset.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roboset.org/revenue-model/business.md). # Business Roboset monetizes the demand side while paying the supply side. Four revenue streams, roughly in order of margin: Custom collection programs. Buyers fund specific campaigns upfront. Highest margin, because in enterprise data deals most of the price reflects contract quality — service levels, license terms, delivery guarantees — rather than raw collection cost. A network with crowd-scale supply and verifiable provenance meets the trust bar at a fraction of a traditional vendor's cost. Dataset licensing. Packaged datasets sold from the catalog. The economics live in license structure: non-exclusive licenses resell the same asset repeatedly (the first sale covers collection, every sale after is near-pure margin), while exclusive rights command a large premium. API and continuous access. Recurring subscriptions for labs that need fresh episodes monthly — turning lumpy project revenue into predictable revenue. Enrichment services. Annotation, format conversion, and dataset structuring sold on top of raw collection — margin-accretive and a driver of buyer lock-in. The network takes a percentage of every sale; the remainder flows to contributors through the RP revenue-share mechanism. Because contributor payout is a share of realized revenue rather than a fixed cost per submission, gross margin is structurally protected, and the catalog appreciates rather than depreciating like inventory. --- # 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://docs.roboset.org/revenue-model/business.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.