> For the complete documentation index, see [llms.txt](https://avano.gitbook.io/dmeter/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://avano.gitbook.io/dmeter/tokenomics/token-bonding.md).

# Token Bonding

Imagine you have a big jar of marbles, and everyone wants to buy marbles from it. But here's the trick: the more marbles people buy, the more expensive each marble becomes. If people start putting marbles back into the jar, the marbles get a little cheaper.

This is kind of like how the **Augmented Token Bonding Curve** works in dMeter. It's a way to make sure the price of the tokens (which are like the marbles) changes depending on how many people want them.

1. **Dynamic Pricing:** When lots of people want marbles (or tokens), the price goes up. If people start giving back their marbles, the price goes down. This way, the price always matches how many people want the tokens.
2. **Stability Mechanism:** To keep the price from going up or down too much too quickly, the system has special rules, like a reserve of extra marbles or small price changes. This helps everyone feel safe because they know the price won't suddenly change a lot.
3. **Programmable Parameters:** The system can be adjusted, like setting the starting price of the marbles or deciding how quickly the price goes up. This makes sure the rules work well for everyone involved.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://avano.gitbook.io/dmeter/tokenomics/token-bonding.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.