> For the complete documentation index, see [llms.txt](https://uliquid-1.gitbook.io/uliquid-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uliquid-1.gitbook.io/uliquid-docs/user-guide/market-intelligence.md).

# Market Intelligence

Read source-backed market context, provider health, and saved analyses.

Market Intelligence provides source-backed market context without creating a trade, prediction, or bot action. It is designed to help you review macro, crypto, regulation, security, and market events alongside your own analysis.

{% hint style="warning" %}
Market Intelligence is not financial advice. A summary, sentiment label, or risk label is not an instruction to buy, sell, open, close, or change leverage.
{% endhint %}

## Use a Market Summary

1. Open **Market Intelligence**.
2. Select the required horizon: intraday, 24 hours, or 7 days.
3. Review the overall risk and sentiment together with highlights and upcoming risks.
4. Open source references for important claims.
5. Refresh the page if the market situation has changed or the displayed data is stale.

## Read Data Quality

The page shows provider states and can mark a result as degraded. A degraded result can have unavailable, delayed, or incomplete sources.

* Read warnings and uncertainties before using a result.
* Do not fill gaps with assumptions.
* Cross-check material market events with primary sources.
* Treat an unavailable provider as less context, not as a neutral signal.

## Saved Analyses

Saved analyses keep a historical report with its selected horizon, generation time, source references, and recorded provider context. They are useful for comparison and review, but they do not update automatically into a current report.

When reopening an older analysis, check its generation time and whether it was marked degraded. Generate a fresh analysis before making a time-sensitive decision.

## Relationship to Predictions

Market Intelligence is a standalone research flow. A Prediction can explicitly include market context, but the two are not the same:

| Market Intelligence                            | Prediction                                                            |
| ---------------------------------------------- | --------------------------------------------------------------------- |
| Explains current context and cited sources.    | Produces a structured setup for review.                               |
| Creates no trading signal or execution action. | Can prefill the Trading Desk; you still review and confirm any order. |
| Keeps saved research reports.                  | Uses its own prediction workflow and controls.                        |

## Availability

Feature availability is plan-aware. If the page is locked or an advanced option is unavailable, open **Settings → Subscription** to see the current requirement. Access never bypasses provider health, security checks, or trading risk controls.


---

# 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 dynamically by asking a question.

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

```
GET https://uliquid-1.gitbook.io/uliquid-docs/user-guide/market-intelligence.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.