> 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/es/apps-en-rome/oracle-gateway.md).

# portal Oracle Gateway

El portal Oracle Gateway: registra fuentes de precios y configura consumidores por cadena.

El portal Oracle Gateway es la interfaz orientada al cliente de Rome para [Oracle Gateway](/es/productos/oracle-gateway.md) — el sistema que expone los feeds de precios de Pyth y Switchboard detrás de interfaces compatibles con Chainlink, con un keeper operado por Rome que actualiza los feeds en caché y de libro.

Usa el portal para explorar los feeds registrados y configurar consumidores por cadena: [oracle.testnet.romeprotocol.xyz](https://oracle.testnet.romeprotocol.xyz/).

## Qué cubre

* **Feeds registrados** — los feeds de precios en vivo en cada cadena, con sus fuentes y ventanas de frescura.
* **Configuración de consumidores** — conectar un contrato para leer un feed a través de Chainlink `AggregatorV3Interface`.

Para conocer los detalles de la interfaz, la arquitectura del adaptador, cómo el keeper actualiza los feeds y qué feeds responden hoy, consulta el [página del producto Oracle Gateway](/es/productos/oracle-gateway.md). Las direcciones de adaptadores desplegados son canónicas en el [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/es/apps-en-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.