> 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

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.

<a href="https://explorer.seda.xyz/" class="button primary">View Explorer</a>


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.seda.xyz/home/token-overview/seda-token-utility/structural-alignment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.