> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/introduction/readme.md).
# Overview
## Designed for Data. Built for Truth.
XYO is building the future of data: a decentralized infrastructure network where data becomes trusted and real-world activity gains provable certainty. As a global DePIN with over 10 million node installs and billions of data points verified, XYO is redefining how the digital and physical worlds connect.
Our protocol does more than just bridge Web3 and reality. XYO captures, verifies, and immutably proves real-world events, from the movement of assets to the presence of people and devices, unlocking next-generation applications in supply chains, real-world gaming, insurance, tokenized real-world assets (RWA), and more.
#### XYO Layer One
**At the heart of this transformation is XYO Layer One, a blockchain for scale, speed, and sovereignty.**
With our dual-token system and XL1 Wallet, developers and users can seamlessly interact with a permissionless ecosystem optimized for permanent data validation and Proof of Location.
Whether you’re launching a dApp, verifying a delivery, securing AI data inputs, or building the next frontier of decentralized apps, XYO provides the trust layer the future demands.
This isn’t just data on-chain. This is the operating system for the real-world internet.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.xyo.network/introduction/readme.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 `build a script that syncs our docs to a CMS` 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.
