> 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/tech/seda-architecture/seda-network-architecture/what-is-a-data-request.md).

# What is a Data Request?

This section explains what DRs are, their importance, and how they function within the SEDA protocol.

Data Requests (DRs) are a foundational component of the SEDA protocol, enabling secure and decentralized access to off-chain data. They act as a bridge between blockchain networks and real-world information, allowing smart contracts and other blockchain applications to query and utilize data in a trust-less manner. Data requests consist of instructions on how data should be fetched and aggregated.

A Data Request (DR) in the SEDA protocol is a structured query that allows blockchain applications to obtain verifiable, real-world data in a decentralized manner. DRs enable the SEDA network to facilitate secure interactions between smart contracts and off-chain data sources by managing the process of data collection, verification, and delivery. This ensures that the data brought on-chain is accurate, trustworthy, and resistant to tampering, which is crucial for the reliable operation of decentralized applications.

### Why Are Data Requests Important?

Blockchains are inherently secure and immutable but are isolated from external data. This isolation poses challenges for decentralized applications and protocols that depend on real-world information to function effectively.

SEDA's Data Requests address this challenge by providing a secure and decentralized standard to access off-chain data across any blockchain network. They enable smart contracts to interact with external data sources in a trustless manner, ensuring that the information is accurate and tamper-resistant. This capability expands the potential of blockchain applications, allowing them to operate with reliable real-world data regardless of the underlying chain.


---

# 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/tech/seda-architecture/seda-network-architecture/what-is-a-data-request.md?ask=<question>&goal=<user_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.
