> For the complete documentation index, see [llms.txt](https://nfa.gitbook.io/nfa-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nfa.gitbook.io/nfa-docs/interfaces/the-web-app.md).

# The web app

## The web app

The web app is where most people meet NFA. It is a dark, deliberately uncluttered interface built around one job: forecast a market, understand the forecast, and act on it if you choose to.

### The main surfaces

| Surface       | What it is for                                                                                                               |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Forecast**  | Paste a market or pick one from the catalogue, watch the debate run live, and read the result with its full reasoning trace. |
| **Activity**  | Your open forecasts and your resolved record, including your Brier score once you have enough scored calls.                  |
| **Portfolio** | Paper and real positions, live PnL, redeem, funding, and cash-out.                                                           |
| **Airdrop**   | Your daily $NFA allocation and countdown.                                                                                    |
| **Referrals** | Your referral link and USDC earnings.                                                                                        |
| **Credits**   | Your balance and top-ups.                                                                                                    |
| **Developer** | API keys for programmatic and agent access.                                                                                  |

### Designed for honesty

The interface is careful with words, because in forecasting the words carry risk:

* It separates **divergence** (how far the engine sits from the market, before resolution) from **edge** (a realized improvement, only after resolution), and never dresses one up as the other.
* Track-record numbers are shown as **unrated** until there are enough resolved calls to mean something.
* Pre-launch figures are clearly tagged, so nothing reads as a settled result before it is one.

{% hint style="info" %}
The design goal is legibility under density: a lot of information, presented so the important number and its caveat are always visible together. Confidence is shown, never implied.
{% 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 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://nfa.gitbook.io/nfa-docs/interfaces/the-web-app.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.