> 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/for-data-providers/operating-a-data-proxy/introduction-to-data-proxy.md).
# Introduction to Data Proxy
A Data proxy is a simple middleware component that acts as a pipeline or connector between a data provider and the SEDA network by holding an API key that has access to the data provider’s services. Additionally, Data Proxies verify conditions to inbound HTTP requests, checking that the requester is part of the SEDA network and that the provider’s fees have been paid. Additionally, they allow providers to add an SECP private key to the proxy, which would be used to sign the data before it’s forwarded back to the requester, adding additional security and verifiability.
In the end, the proxy nodes allow data providers to expose their entire suite of APIs through a single, one-time deployment and earn value based on onchain demand with minimal technical overhead or maintenance.
## Request Flow
How data is requested via the SEDA Network.
## Response Flow
How data is served from the Data Proxy to the SEDA Network.
---
# 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/for-data-providers/operating-a-data-proxy/introduction-to-data-proxy.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.
