> For the complete documentation index, see [llms.txt](https://docs-v4.venus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v4.venus.io/technical-reference/reference-oracle.md).

# Oracle

Venus markets obtain USD prices through a chain-specific `ResilientOracle`. Each underlying asset has a configurable main source and may also have pivot and fallback sources. Source roles, enable flags, validation bounds, proxy implementations, and market lifecycle state can change through governance.

{% hint style="warning" %}
Documentation tables are snapshots, not live configuration. Resolve the oracle used by the relevant Comptroller and read its per-asset configuration on-chain before using a price or source address in an integration.
{% endhint %}

## Architecture and risk

* [Resilient Price Oracle](/risk/resilient-price-oracle.md) — role model, correlated-asset assumptions, and configuration snapshot
* [ResilientOracle contract](/technical-reference/reference-oracle/resilient-oracle.md) — current contract behavior and API
* [DeviationBoundedOracle](/technical-reference/reference-oracle/deviation-bounded-oracle.md) — bounded borrow-power prices for configured assets

## Source adapters

* [Source adapter overview](/technical-reference/reference-oracle/oracles.md)
* [Correlated token oracles](/technical-reference/reference-oracle/correlated-token-oracles.md)

## Deployment references

* [Deployed oracle addresses](/deployed-contracts/oracles.md)
* [Oracle repository](https://github.com/VenusProtocol/oracle)


---

# 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-v4.venus.io/technical-reference/reference-oracle.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.