> For the complete documentation index, see [llms.txt](https://docs.layerlens.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.layerlens.ai/2.-get-started/choose-your-path.md).

# Choose your path

| If you...                                            | Start here                                                                                                                        |
| ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| ...want to know which model is best at X             | [Stratix Public](/2.-get-started/public.md)                                                                                       |
| ...want to compare two models head-to-head           | [Stratix Public — Compare two models](/2.-get-started/compare-two-models.md)                                                      |
| ...want to run a private evaluation on your own data | [Stratix Premium — Sign up](/2.-get-started/sign-up.md) → [First evaluation](/2.-get-started/first-evaluation.md)                 |
| ...want to build an LLM judge                        | [Stratix Premium — First judge](/2.-get-started/first-judge.md)                                                                   |
| ...want to upload a trace and score it               | [Stratix Premium — First trace](/2.-get-started/first-trace.md)                                                                   |
| ...want to integrate evaluations into code or CI/CD  | [SDK quickstart](/2.-get-started/sdk.md)                                                                                          |
| ...are setting up for a team                         | [Stratix Premium — Sign up](/2.-get-started/sign-up.md) and [Personalized onboarding](/2.-get-started/personalized-onboarding.md) |
| ...just want to test your AI quickly                 | [Stratix Public — Test your AI](/2.-get-started/test-your-ai.md)                                                                  |

## All three at once

Many teams use all three surfaces. A typical first day looks like:

1. **Public** — research the catalog, shortlist candidate models.
2. **Premium** — sign up, run a private evaluation against your data on the shortlist.
3. **SDK** — wire the winning evaluation into your code or CI gate.

You can switch between Public and Premium with the **Switch toggle** in the Premium top bar.

## Common pitfalls

* **Skipping the Public catalog and going straight to Premium.** You'll waste ECU running candidates that public scores would have ruled out.
* **Building a judge before you have a labeled set.** Judges only work as well as the labels you tune them against. Even 30 labels makes a meaningful difference.
* **Wiring CI gates before you've run the eval interactively.** Start in the Premium UI; promote to CI once you trust the result.

## Where to next

* [Stratix Public quickstart](/2.-get-started/public.md)
* [Stratix Premium quickstart](/2.-get-started/premium.md)
* [SDK quickstart](/2.-get-started/sdk.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 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.layerlens.ai/2.-get-started/choose-your-path.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.