> For the complete documentation index, see [llms.txt](https://docs.usd.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usd.ai/technical-overview/3rd-party-data.md).

# Oracles

Third-party oracle feeds covering the USD.AI protocol.

### Chainlink

USD.AI's [Chainlink integration announcement](https://usd.ai/blog/chainlink-usdai-data-feed) identifies two feed types:

**Exchange Rates, based on contract functions:**

* [sUSDai / USDai exchange rate — Ethereum](https://data.chain.link/feeds/ethereum/mainnet/susdai-usdai-exchange-rate)
* [sUSDai / USDai exchange rate — Base](https://data.chain.link/feeds/base/base/susdai-usdai-exchange-rate)
* [sUSDai / USDai exchange rate — BNB Chain](https://data.chain.link/feeds/bsc/mainnet/susdai-usdai-exchange-rate)

**Market Feeds, based on secondary pricing**

* [USDai / USD mark feed — Plasma](https://data.chain.link/feeds/plasma/plasma/usdai-usd)
* [USDai / USD market feed — Arbitrum](https://data.chain.link/feeds/arbitrum/mainnet/usdai-usd)
* [USDai / USD market feed — Base](https://data.chain.link/feeds/base/base/usdai-usd)
* [sUSDai / USD market feed — Ethereum](https://data.chain.link/feeds/ethereum/mainnet/susdai-usd)

View all data oracles at [Chainlink feed directory](https://data.chain.link/feeds)

### Atlas Oracle

* [sUSDai feed — Atlas](https://atlasoracle.io/feeds/1110)

Atlas has supplied an sUSDai feed with the following configuration:

* Feed ID: `1110`
* Provider-reported contract: `0x3a3ab5a8bc6070ee32554ceed7d729b3c3632f73`
* Provider-reported deviation threshold: `0.1%`
* Provider-reported heartbeat: `1 hour`

Atlas's integration guidance calls for Pull API integration, with WebSocket delivery available as an optional addition. Onchain reads require the consuming contract to be whitelisted by Atlas.


---

# 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.usd.ai/technical-overview/3rd-party-data.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.
