> For the complete documentation index, see [llms.txt](https://docs.kaito.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaito.ai/overview/attention-economy.md).
# Attention Economy
**"The currency of life isn’t money. It’s not even time. It’s attention."** — Naval Ravikant
The era of GenAI has drastically reduced the marginal cost of producing information, increasing its abundance while making it more challenging to filter for what is truly worth our time. In this new economy, what is scarce and valuable is the attention that information accrues — through clicks, likes, shares, and impressions — representing the flow of value in the trillion-dollar attention economy.
Yet, the attention economy today is broken. Creators produce content, users contribute personal data, brands spend huge amounts on advertising — yet the vast majority of the value flows to platforms.
How do we redefine the relationship among creators, users, brands, and platforms?
How do we collectively build a fairer and more efficient attention economy, while rewarding all market participants?
At Kaito, we believe InfoFi is the answer.
---
# 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.kaito.ai/overview/attention-economy.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.
