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

# Developer Guides

UDF is a modular oracle protocol that allows smart contracts to access both Web2 and Web3 data seamlessly, delivering authenticated, customizable data on-demand. It offers developers the flexibility to choose between push and pull data feeds, optimizing cost-efficiency and performance. UDF standardizes data streaming into a universal format, enabling dApps to easily connect with data sources across any EVM and non-EVM network.

Existing dApps or developers planning to build one requiring an oracle for price data, can integrate our data feeds into your smart contracts. Get started by taking a look at one of our guides.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Custom Data Feeds</td><td><a href="https://4040807501-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5AajewgFWO9EkufRORqL%2Fuploads%2FfgRGA9e7qIlL9VvNAfEa%2FConnecting%20Custom%20Data.png?alt=media&amp;token=f820395a-b977-4f76-b51f-6bfbd7d6491a">Connecting Custom Data.png</a></td><td><a href="/universal-data-feeds/developer-guides/custom-data-feeds.md">Custom Data Feeds</a></td></tr><tr><td>Fetch Data via Pull Model (PAYG)</td><td><a href="https://4040807501-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5AajewgFWO9EkufRORqL%2Fuploads%2FI3OHTZNvHC0PE8pqJGMb%2FLiquid%20Vault%20Audit.png?alt=media&amp;token=5ba9deb8-d430-4a0a-868a-be694448af72">Liquid Vault Audit.png</a></td><td><a href="/universal-data-feeds/developer-guides/fetch-data-via-pull-model-payg.md">Fetch Data via Pull Model (PAYG)</a></td></tr><tr><td>Fetch Data via Pull Model (Subscription)</td><td><a href="https://4040807501-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5AajewgFWO9EkufRORqL%2Fuploads%2FMxrz0JJYICzoDEaNASSe%2FETS%20Guides.png?alt=media&amp;token=92a8df20-217d-482f-bc20-b06df89bc48e">ETS Guides.png</a></td><td><a href="/universal-data-feeds/developer-guides/fetch-data-via-pull-model-subscriptions.md">Fetch Data via Pull Model (Subscriptions)</a></td></tr><tr><td>Fetch Data via Push Model</td><td><a href="https://4040807501-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5AajewgFWO9EkufRORqL%2Fuploads%2FemwP69atNJAnhXWl66Vt%2F15.png?alt=media&amp;token=544a1f5a-9502-41fe-ad8a-a90987e7dca3">15.png</a></td><td><a href="/universal-data-feeds/developer-guides/fetch-data-via-push-model.md">Fetch Data via Push Model</a></td></tr></tbody></table>


---

# 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.entangle.fi/universal-data-feeds/developer-guides.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.