# Revenue Model

SensorVM is built to generate protocol-level revenue based on actual device interactions, logic deployment, and network usage. The goal isn’t speculative value — it's sustained and verifiable economic activity.

***

#### 📊 Revenue Sources

The Sensor protocol earns revenue from multiple on-chain and platform-side operations:

***

| Stream                    | Functionality                                                 |
| ------------------------- | ------------------------------------------------------------- |
| **VM Usage Charges**      | Fees from machines executing on-chain robotic logic           |
| **Permissioned Access**   | Charges for API keys, SDKs, and special VM functions          |
| **Proof Anchoring**       | Fees from anchoring real-world task proofs and uptime reports |
| **Public Logic Use**      | Developers earn when their shared modules are reused          |
| **Referral System Logic** | Referrers are rewarded from the new usage they help generate  |

***

***

#### 🧬 On-Chain Distribution Logic

Revenue collected by SensorVM is divided into 3 main paths:

* **Bonded Wallets**: Holders of Sensor Bonds receive automatic distributions
* **Creator Streams**: Developers of logic blocks receive a royalty based on public usage
* **Protocol Reserve**: Retained funds are used for tech scaling, audits, and infra incentives

There’s no team wallet draining fees or opaque treasury fund — everything flows through code.

***

#### ♻️ Closed Revenue Loop

SensorVM encourages a self-sustaining design:

```plaintext
Machine executes logic → Pays micro-fee → Fee gets routed to bond-holders & logic authors
```

This makes each interaction valuable:

* Robots that work pay a toll
* Builders who build get royalties
* Contributors who hold stay rewarded

SensorVM doesn’t just enable machine work — it monetizes it, distributes the outcome, and locks value within the protocol.

**It’s robotics with built-in revenue logic.**


---

# 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://sensorvm.gitbook.io/sensorvm-docs/token-utility/revenue-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.