> 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-agents/agent-modules/accessing-data-on-seda.md).

# Accessing Data On SEDA

## Define Your Data Source

**Canonical page:** <https://docs.seda.xyz/home/for-agents/modules/10-data-access>

Authoritative entry:

* <https://docs.seda.xyz/home/for-developers/define-your-data-source>

Your job on this page is to decide:

* where the data comes from
* whether you need a Data Proxy
* what the Oracle Program will consider a valid response

**Rule:** If a value is not explicitly provided by docs or config, stop and ask.

***

### 1) Supported feeds

Use when:

* a feed already exists in SEDA’s supported catalog.

Action:

* identify the feed (provider + symbol)
* decide if you need custom logic (smoothing, fallbacks, blending)
  * if yes, you still build a custom Oracle Program

Browse Supported Feeds

{% file src="/files/XEZrFVInEmEu0hfF91Sg" %}

{% file src="/files/W6VRMxZtzFe907SiRIn1" %}

Checkpoint:

* you can name the provider/feed and the exact output fields you expect.

***

### 2) Public API

Use when:

* the endpoint requires no credentials.

Action:

* confirm response format (JSON preferred)
* define parsing rules and validation rules (schema, bounds, freshness)
* read timeout defaults and set per-request timeout if needed: <https://docs.seda.xyz/home/for-agents/agent-modules/http-fetch-timeouts>

Checkpoint:

* you can state the JSON path(s) you will parse and the bounds you will enforce.

***

### 3) Private API / proprietary data

Use when:

* upstream requires API keys, tokens, cookies, or internal access.

Rules:

* do not embed secrets in Oracle Program code or repos
* use a Data Proxy route to hold credentials and enforce access/proof

Next:

* <https://docs.seda.xyz/home/for-agents/agent-modules/deploying-data-proxies> (deploy + route + register + validate + run)

Checkpoint:

* you can describe your intended proxy route shape:
  * `baseURL`, `routeGroup`, `path`, and upstream URL mapping.

***

### 4) Website-only source

Use when:

* no stable API exists and you rely on scraping or a “website-to-API” service.

Rules:

* treat it as private/proprietary behind a proxy route
* plan for breakage (define fallbacks or fail-closed behavior)

Next:

* [`https://docs.seda.xyz/home/for-agents/agent-modules/deploying-data-proxies`](https://docs.seda.xyz/home/for-agents/agent-modules/deploying-data-proxies)

Checkpoint:

* you can name at least one fallback source or a defined “fail closed” behavior.

***

### Recommended output contract

Before writing code, define:

* `source`: provider + endpoint domain
* `fetched_at`: timestamp requirement (freshness)
* `payload_hash`: hash of raw payload
* `parsed_result`: normalized fields your OP outputs
* `validation`: schema + bounds + freshness rules

This prevents ambiguous Oracle Programs that are hard to verify.


---

# 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.seda.xyz/home/for-agents/agent-modules/accessing-data-on-seda.md?ask=<question>&goal=<endgoal>
```

`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.