> 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/see-the-signal-between-sessions-3.md).

# See the signal between sessions

Explore the actual Bitget spot universe, including tokenized US equities. Every quote carries its source, freshness, classification, and stock-session context.

[Research an event ↗](/see-the-signal-between-sessions.md) [Build your company radar](/see-the-signal-between-sessions-7.md)

**24 / 7**\
CONTEXT

AFTER HOURS\
EVENT FLOW

BITGET PUBLIC SPOT API\
**READ ONLY**\
Live pricing requires no account key.

## The tradable universe

Bitget instruments, current tickers, token classification, and stock reference data.

Bitget connected\
Connecting to public market data…

REALITY rTOKENS\
**—** Bitget classified

RWA SPOT PAIRS\
**—** Flagged by instrument metadata

CRYPTO SPOT PAIRS\
**—** USDT quoted

SESSION REFERENCE\
US session calendar warming up\
Bitget Reality market states

All spot assets\
rTokens\
Other RWA\
Crypto

Connecting to Bitget spot instruments and tickers…

Price can move.\
*So can the story.*
-------------------

Policy, earnings, and macro events don’t wait for the opening bell. Tidelight combines verified Bitget market context with evidence-led research so traders can inspect the case before making a decision.

### Show where every number came from.

Quotes and candle history use Bitget public market data. Reality flags, underlying tickers, and trading eligibility use Bitget reference data. Issuer labels and logos are presentation metadata; unsupported logos fall back to an underlying ticker mark. No sample prices are substituted when the feed is unavailable.

[See workspace settings ↗](/see-the-signal-between-sessions-12.md)


---

# 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/see-the-signal-between-sessions-3.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.