# Common Errors

In this section you will find an explanation of the exceptions used by the Opium Protocol to ensure the consistency of its internal data models and business logic.

While developing a financial product on top of the Opium Protocol, it is possible to encounter one of the exceptions described in this section in case the code does not comply with the Opium Protocol's internal specifications. 

As not all exceptions are quite self-explanatory, the intent of the present documentation is to provide a more helpful descriptions of the errors that a developer might encounter.

{% content-ref url="/pages/-MlR-uAScJ1ZZdppmebZ" %}
[OracleAggregator Errors](/for-developers/protocol/common-errors/oracleaggregator.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MlQzfkNSBupE\_n-Q2Ak" %}
[Core Errors](/for-developers/protocol/common-errors/core.md)
{% endcontent-ref %}


---

# 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.opium.network/for-developers/protocol/common-errors.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.