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

# Oracles

Oracles are third-party services that provide smart contracts with external information. They act as a bridge between blockchains and the outside world, enabling smart contracts to access off-chain data. Oracles are essential in expanding the functionality of smart contracts by enabling them to interact with data sources beyond their native networks.

There are oracle providers are available on Zircuit, you can learn more about them below.

## Redstone

{% embed url="<https://docs.redstone.finance/docs/get-started/price-feeds>" %}

RedStone is a modular oracle specializing in providing gas-optimized data feeds and offering price feeds for new LSTs, LRTs, Bitcoin LSTs, and emerging types of stablecoins. Their services are available cross-chain including EVM and non-EVM chains, rollups, and appchains.

## **API3**

{% embed url="<https://docs.api3.org/>" %}

API3 provides price feed services to smart contracts in a decentralized, trust-minimized way, using first-party oracles, with each source being verifiable on-chain. A key feature of API3 oracles is the ability to fast-track the most accurate asset value through API3's Oracle Extractable Value (OEV) network. API3 focuses on maximizing security and minimizing latency.


---

# 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.zircuit.com/infra/oracles.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.