> For the complete documentation index, see [llms.txt](https://docs.tidelight.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tidelight.app/trust-and-safety/data-and-product-limits.md).

# Data and product limits

Understand the boundaries around market data and simulations.

## Data and product limits

Tidelight connects evidence with possible market exposure. It does not provide a recommendation or guarantee an outcome.

| Tidelight does                                             | Tidelight does not                                          |
| ---------------------------------------------------------- | ----------------------------------------------------------- |
| Shows public market data with freshness context            | Guarantee every market or quote is always available         |
| Organizes submitted source material into reviewable briefs | Independently verify every statement in an external article |
| Replays historical data and paper simulations              | Guarantee a strategy will perform in the future             |
| Keeps Nightwatch in paper mode                             | Place automated orders or manage customer funds             |

{% hint style="warning" %}
Use Tidelight as informational research. Check original sources and follow your local rules before acting on market information.
{% endhint %}


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tidelight.app/trust-and-safety/data-and-product-limits.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.