> For the complete documentation index, see [llms.txt](https://docs.seda.xyz/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seda.xyz/home/token-overview/seda-token-utility/structural-alignment.md).
# Structural Alignment
Explanation of how SEDA’s token mechanics align network usage, deterministic burn, staking participation, and network security within a unified onchain token model.
SEDA’s onchain oracle model aligns adoption with token mechanics in a measurable way.
When builders launch products, data requests increase.\
When data requests increase, burn increases.\
When burn increases, circulating supply reduces as a consequence of network usage.
This relationship between ecosystem growth and network activity is visible via the explorer.
The SEDA onchain oracle token economy results in a simple yet powerful engine: Growth drives network usage, usage drives deterministic burn, and burn reinforces network security.\
\
All of it is observable onchain.
View Explorer
---
# 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://docs.seda.xyz/home/token-overview/seda-token-utility/structural-alignment.md?ask=&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.