> 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/use-tidelight/start-here.md).

# Start here

Turn a question and a source into a clear research trail.

## Start here

Tidelight helps you follow the stories moving tokenized markets.

Use it to connect an event with its evidence, possible exposure, and alternative outcomes. You stay in control of every decision.

{% stepper %}
{% step %}

### Explore the market map

Open **Markets** to browse public quotes, asset details, classifications, and available candle history. Check quote freshness before relying on a price.
{% endstep %}

{% step %}

### Frame a research question

Open **Research desk**. Start with a company, a question, and a public source that supports your investigation.
{% endstep %}

{% step %}

### Review the trail

Read the evidence, exposures, catalysts, counter-evidence, and invalidation conditions. Save the brief if you want to revisit it.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Tidelight is a research companion. It provides information, not financial advice or trade recommendations.
{% endhint %}

### Choose your view

**Mini** provides a plain-language answer with its supporting evidence. **Pro** exposes the underlying claims, source dates, confidence, exposures, and scenario notes.

Both views use the same evidence trail.


---

# 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/use-tidelight/start-here.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.