# Page Not Found

The URL `documentation-v2/section-2-analyze/dynamic-chart` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Data Plotter](https://docs.tickertrends.io/tickertrends/documentation-v2/4.-features-and-workflows/data-plotter.md)
- [Daily Digest Email](https://docs.tickertrends.io/tickertrends/documentation-v2/4.-features-and-workflows/daily-digest-email.md)
- [5. Pricing & Tiers](https://docs.tickertrends.io/tickertrends/documentation-v2/5.-pricing-and-tiers.md)
- [6. Access & Data Delivery](https://docs.tickertrends.io/tickertrends/documentation-v2/6.-access-and-data-delivery.md)
- [2. Data Coverage & Data Types](https://docs.tickertrends.io/tickertrends/documentation-v2/2.-data-coverage-and-data-types.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://docs.tickertrends.io/tickertrends/documentation-v2/4.-features-and-workflows/data-plotter.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.

### Option 2 — Browse the documentation index

Full index: https://docs.tickertrends.io/tickertrends/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.tickertrends.io/tickertrends/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/tickertrends/documentation-v2/4.-features-and-workflows/data-plotter.md`).

You may also use `Accept: text/markdown` header for content negotiation.