> For the complete documentation index, see [llms.txt](https://docs.epiora.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.epiora.xyz/data-architecture.md).

# Data Architecture

A trading interface can easily become inefficient if every visible market independently polls remote APIs.

Epiora avoids this architecture.

Market discovery and live market data use different update strategies.

Conceptually:

```
Market catalog
-> shared
-> cached
-> infrequently refreshed

Selected market data
-> live
-> focused
-> higher frequency

Inactive markets
-> no unnecessary live polling
```

Hyperliquid live data is WebSocket-oriented where appropriate.

HTTP endpoints act as controlled fallback or discovery sources rather than creating one polling loop per market.

Robinhood catalog and pricing requests are similarly shared and deduplicated.

This architecture reduces unnecessary infrastructure usage while allowing the interface to maintain a broad searchable market catalog.


---

# 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.epiora.xyz/data-architecture.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.