# Oracle Router

The Oracle Router is a critical component within the Agentic Data Coordination Service (ADCS), responsible for directing data requests to the appropriate oracles based on user specifications and data requirements. It plays a pivotal role in ensuring that data retrieval is efficient, accurate, and aligned with the needs of the application.

## Functionality

When the Coordinator Contract receives a request from a Consumer Contract, it performs a detailed analysis of the request. This includes understanding the type of data required and evaluating specific parameters or filters defined by the user, such as data source preferences, required data freshness, or acceptable latency.

Based on this analysis, the Coordinator routes the request to the Oracle Router, which dynamically selects the most suitable oracles for fulfilling the request. Selection criteria may include:

* Data Specialization: Oracles that specialize in the specific type of data needed.
* Performance Metrics: Oracles with proven reliability, low latency, and high accuracy.
* Cost Efficiency: Oracles that offer competitive pricing for their services.
* Reputation Scores: Oracles with high trust and reputation within the ADCS network.

By intelligently directing requests, the Oracle Router enhances scalability and reliability. It distributes requests among multiple oracles, preventing overloading any single oracle and optimizing resource utilization within the network. This approach also improves response times by leveraging the fastest available oracles and mitigates the impact of potential oracle failures or slowdowns.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.rivalz.ai/adcs-ai-oracles/design-components/on-chain-components/oracle-router.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
