> 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/pt-br/apps-na-rome/oracle-gateway.md).

# portal Oracle Gateway

O portal Oracle Gateway — registre feeds de preço e configure consumidores por chain.

O portal do Oracle Gateway é a interface voltada ao cliente para a [Oracle Gateway](/pt-br/produtos/oracle-gateway.md) — o sistema que expõe feeds de preço da Pyth e da Switchboard por trás de interfaces compatíveis com a Chainlink, com um keeper operado pela Rome atualizando os feeds em cache e de book.

Use o portal para navegar pelos feeds registrados e configurar consumidores por chain: [oracle.testnet.romeprotocol.xyz](https://oracle.testnet.romeprotocol.xyz/).

## O que ele abrange

* **Feeds registrados** — os feeds de preço ativos em cada chain, com suas fontes e janelas de atualização.
* **Configuração de consumidores** — conectar um contrato para ler um feed por meio da Chainlink `AggregatorV3Interface`.

Para ver os detalhes da interface, a arquitetura do adaptador, como o keeper atualiza os feeds e quais feeds respondem hoje, consulte a [página do produto Oracle Gateway](/pt-br/produtos/oracle-gateway.md). Os endereços dos adaptadores implantados são canônicos na [registro](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/pt-br/apps-na-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.