> For the complete documentation index, see [llms.txt](https://docs.midasmarkets.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.midasmarkets.xyz/platform/analysis.md).

# Analysis

Analysis pages turn assets, perps, and headlines into structured market context with summaries, strategy sections, charts, related assets, and Wire evidence.

* **Asset analysis** — Crypto assets and supported markets can have dedicated pages with summaries, charts, related assets, and trade controls.
* **Headline analysis** — Major headlines can resolve to analysis pages with the market relevance, likely beneficiaries, risks, and strategy context.
* **On-demand analysis** — Midas can generate or refresh analysis when recent stored analysis is missing or stale.

## Analysis surfaces

Midas analysis appears on asset detail pages, perp pages, headline analysis routes, and Ask Midas responses. The goal is to make market context legible before the user reaches the order ticket.

## Stored and on-demand analysis

Some analyses are precomputed for speed. Others are generated on demand when a user asks for a fresh view of an asset, perp, or headline.

## Evidence and signals

Analysis is most useful when it is connected to evidence: price data, Wire items, market signals, related assets, recent trades, and portfolio exposure.


---

# 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://docs.midasmarkets.xyz/platform/analysis.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.
