> 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/ko/rome/oracle-gateway.md).

# Oracle Gateway 포털

Oracle Gateway 포털 — 체인별로 가격 피드를 등록하고 소비자를 설정하세요.

Oracle Gateway 포털은 Rome의 고객용 인터페이스입니다 [Oracle Gateway](/ko/products/oracle-gateway.md) — Chainlink 호환 인터페이스 뒤에서 Pyth와 Switchboard 가격 피드를 제공하고, Rome이 운영하는 keeper가 캐시된 피드와 book 피드를 새로 고치는 시스템입니다.

포털을 사용해 등록된 피드를 둘러보고 체인별로 소비자를 구성하세요: [oracle.testnet.romeprotocol.xyz](https://oracle.testnet.romeprotocol.xyz/).

## 포함 내용

* **등록된 피드** — 각 체인에 있는 실시간 가격 피드로, 출처와 최신성 기간이 포함됩니다.
* **소비자 구성** — 컨트랙트가 Chainlink를 통해 피드를 읽도록 연결하는 작업 `AggregatorV3Interface`.

인터페이스 세부 사항, 어댑터 아키텍처, keeper가 피드를 새로 고치는 방식과 오늘 어떤 피드가 응답하는지에 대해서는 다음을 참조하세요. [Oracle Gateway 제품 페이지](/ko/products/oracle-gateway.md). 배포된 어댑터 주소는 다음에서 기준입니다 [레지스트리](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/ko/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.