# Pricing

Vision Credits are priced in **USD, not in $SIGHT**. The protocol uses a **Chainlink-fed oracle** to convert the USD price into $SIGHT at the moment of purchase.

> Buyers do not need to think about token volatility — they think in dollars.

***

## How It Works

| Parameter            | Value                                                    |
| -------------------- | -------------------------------------------------------- |
| **Initial price**    | $0.01 USD per Credit                                     |
| **Payment method**   | Buyers acquire $SIGHT on the open market                 |
| **Mechanism**        | $SIGHT is burned through the Vision Credit contract      |
| **Price governance** | Adjustable via [CIP](file:///0129295/governance/cips.md) |

***

## Burn Split

Of every $SIGHT burned for Vision Credits:

| Destination            | Share | Purpose                            |
| ---------------------- | ----- | ---------------------------------- |
| **Permanent burn**     | 75%   | Reduces circulating supply         |
| **Mining Reward Pool** | 25%   | Recycled into next epoch's rewards |

***

## Enterprise-Friendly Design

This mirrors Hivemapper's Honey burn-and-mint and Helium's HNT-DC mechanism: a **stable USD-denominated unit** of data demand sits on top of a volatile mining-side asset.

Enterprise buyers can **budget cleanly** while miners benefit from buy-side pressure.


---

# 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://clawglasses.gitbook.io/clawglasses-docs/vision-credits/pricing.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.