# $SVM Token Info

$SVM is the native utility token of the SensorVM ecosystem. It serves as the backbone for network access, user interaction, developer tooling, and economic alignment between all actors in the Sensor protocol.

***

#### 🧩 Why We Use a Token

SensorVM operates at the intersection of robotics, IoT, and DeFi. To manage on-chain interactions between machines, people, and smart contracts — a tokenized system is essential.

$SVM is not just a trading asset — it’s the access key to the ecosystem.

***

#### 🔑 Core Functions of $SVM

***

| Function                 | Purpose                                                                  |
| ------------------------ | ------------------------------------------------------------------------ |
| **Access Control**       | Unlock features like SensorVM logic execution, deployment, and APIs      |
| **Sensor Bonds**         | Holding/locking $SVM earns you Sensor Bonds, which control revenue share |
| **Usage Fees**           | Pay for storage, compute, or network requests via token micro-fees       |
| **Incentives & Rewards** | Used to incentivize developers, referrers, and task validators           |

***

***

#### ⚙️ Designed for Long-Term Utility

* No team allocations or presale — launched fair and clean
* 95% of supply seeded into LP
* Taxes go back to development, Sensor Bonds, and marketing

By aligning network utility with token ownership, Sensor ensures that every participant — from a robotic developer to a token holder — has skin in the game.

**$SVM is not just a utility token. It’s a protocol passport.**


---

# 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/usdsvm-token-info.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.