> 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/id/aplikasi-di-rome/oracle-gateway.md).

# portal Oracle Gateway

Portal Oracle Gateway — daftarkan price feed dan konfigurasi konsumen per chain.

Portal Oracle Gateway adalah antarmuka yang berhadapan dengan pelanggan untuk [Oracle Gateway](/id/produk/oracle-gateway.md) — sistem yang mengekspos umpan harga Pyth dan Switchboard di balik antarmuka yang kompatibel dengan Chainlink, dengan keeper yang dijalankan oleh Rome menyegarkan cache dan umpan buku.

Gunakan portal ini untuk menelusuri feed yang terdaftar dan mengonfigurasi konsumen per chain: [oracle.testnet.romeprotocol.xyz](https://oracle.testnet.romeprotocol.xyz/).

## Yang dicakup

* **Feed yang terdaftar** — umpan harga yang aktif di setiap chain, beserta sumber dan jendela kebaruannya.
* **Konfigurasi konsumen** — menghubungkan sebuah kontrak untuk membaca feed melalui Chainlink `AggregatorV3Interface`.

Untuk detail antarmuka, arsitektur adapter, bagaimana keeper menyegarkan feed, dan feed mana yang menjawab hari ini, lihat [halaman produk Oracle Gateway](/id/produk/oracle-gateway.md). Alamat adapter yang diterapkan bersifat kanonis di [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/id/aplikasi-di-rome/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.