> For the complete documentation index, see [llms.txt](https://docs.asphodel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.asphodel.io/whitepaper/intro/premium-context.md).
# Premium Context
Decentralized worlds built in this way acquire value over time. They not only acquire value from the funds locked in their systems, but also from human engagement, from cultural significance, and from accumulation of data. We think of this overall relationship as creating a **Premium Context**.
A **Premium Context** is a digital environment that is differentiated from the wider internet through its quality. Financialization of actions and objects within the environment embeds a cost to action, and in doing so we avoid the accumulation of useless content and behavior - that is, slop.
Dead Internet Theory is the idea that, with time, almost all public spaces online have become infested with various forms of bots and automation through constant lowering of the bar to entry - that real users are now drastically outnumbered by agents and ghosts. We believe this is now more or less self-evidently true and would encourage doubters to create an X account.
Our Worlds avoid this issue in a very simple way. Because they are built on blockchains, every action costs resources - specifically gas, which has financial value. Because they are decentralized economies, it is also possible for players to extract profit through playing sufficiently well. The end result is an economy of attention and action that rewards a focus on significant play rather than spam or slop. Just like in reality, wasteful and inefficient action is punished, and the system selects for efficient and sustainable players.
This also encourages individuals to collaborate and band together, and in the process creates a social environment that is more high-trust, more relationship based, and less transient than the typical modern internet. Such an environment is inherently valuable to human beings. We expect that as current trends progress, and the default value of action or content online becomes lower and lower, such an environment will become more and more intrinsically valuable to humans: a **Premium Context** that emphasizes signal over noise.
At the same time, such an environment now also becomes more valuable to agents - a higher proportion of real human communications as opposed to AI-generated content, alongside a world in which an agent can potentially profit independently and generate its own income. A world in which all information is verifiable and the current state has an absolute, objective answer that an agent can query at any time. A permissionless world that isn't hostile to agents and doesn't restrict their access. An intrinsically appealing environment for an agent to parse.
This is why we use the term 'context' specifically here - because this dynamic quite literally creates a substrate that is more valuable to LLMs than the rest of the internet. **Premium Context.**
---
# 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.asphodel.io/whitepaper/intro/premium-context.md?ask=&goal=
```
`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.