# Page Not Found

The URL `traderchallenge/getting-started/traderchallenge-onboarding` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [The Challenge Dashboard](https://docs.tradersyard.com/traderchallenge/quick-start-guides/the-challenge-dashboard.md)
- [Connect your Challenge to AgenaTrader (Desktop)](https://docs.tradersyard.com/traderchallenge/quick-start-guides/connect-your-challenge-to-agenatrader-desktop.md)
- [Connect your Challenge or Tournament to the WebTrader](https://docs.tradersyard.com/traderchallenge/quick-start-guides/connect-your-challenge-or-tournament-to-the-webtrader.md)
- [Account Scaling](https://docs.tradersyard.com/traderchallenge/account-scaling.md)
- [Welcome to the Yard](https://docs.tradersyard.com/traderchallenge/welcome-to-the-yard.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://docs.tradersyard.com/traderchallenge/quick-start-guides/the-challenge-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://docs.tradersyard.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://docs.tradersyard.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/traderchallenge/quick-start-guides/the-challenge-dashboard.md`).

You may also use `Accept: text/markdown` header for content negotiation.