> For the complete documentation index, see [llms.txt](https://docs.rome.builders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rome.builders/zh/rome-shang-de-ying-yong/oracle-gateway.md).

# Oracle Gateway 门户

Oracle Gateway 门户——注册价格数据源并按链配置消费者。

Oracle Gateway 门户是 Rome 的面向客户的界面。 [Oracle Gateway](/zh/chan-pin/oracle-gateway.md) ——该系统通过与 Chainlink 兼容的接口公开 Pyth 和 Switchboard 的价格数据源，并由 Rome 运行的 keeper 刷新缓存数据源和订单簿数据源。

使用该门户浏览已注册的数据源，并按链配置消费者： [oracle.testnet.romeprotocol.xyz](https://oracle.testnet.romeprotocol.xyz/).

## 它涵盖什么

* **已注册的数据源** ——各条链上的实时价格数据源，以及它们的来源和新鲜度窗口。
* **消费者配置** ——将合约连接到通过 Chainlink 读取某个数据源 `AggregatorV3Interface`.

有关界面细节、适配器架构、keeper 如何刷新数据源以及当前哪些数据源可用，请参见 [Oracle Gateway 产品页面](/zh/chan-pin/oracle-gateway.md)。已部署的适配器地址在……中具有权威性 [registry](https://github.com/rome-protocol/rome-registry).


---

# 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.rome.builders/zh/rome-shang-de-ying-yong/oracle-gateway.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.