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

# The console

The console is the main interface to Flox. Open it and you can read the entire log for free — no wallet, no account, no signup.

## What you see

**Asset tabs** across the top — every token in the watchlist. Selecting one loads its most recent assessment from the log.

**The assessment card** shows the verdict, the position size, the six core metrics (supply pressure, depth, net issuance, event count, concentration, locked supply), the engine's reasons, and the analyst narrative with its forecast.

**Venue depth** breaks down liquidity per pool, so a thin book hiding inside a healthy total is still visible.

**The side rail** carries the live signals: chain integrity, the verdict mix and refusal rate, the forecast scorecard, and a feed of recent calls. It refreshes automatically.

## Reading is free, assessing is metered

Reading the log costs nothing — the whole argument for Flox is that anyone can audit the record, so charging to read it would be a contradiction.

Running a *new* assessment writes to the chain and costs a credit. That path requires a connected wallet with a credit balance. See [Buying credits](/using-flox/credits.md).

## Running an assessment

1. Connect a wallet. The app adds Robinhood Chain automatically if your wallet doesn't have it.
2. Make sure you have credits (deposit if not).
3. Pick an asset and press **Run new assessment**.
4. Your wallet signs a request. The server recovers your address, checks your on-chain balance, and runs the assessment.
5. The result appears and is committed to the log with a hash you can verify.


---

# 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.tryflox.xyz/using-flox/console.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.