---
title: What to read next
description: "Where the Platform documentation goes after your first benchmark: concepts, how-to guides, the CLI and the MCP surface."
---

You ran a benchmark on real hardware and read the result. The rest of the documentation, in a useful reading order:

- **[Concepts](../concepts/index.md)**: one page per object, for the moment you need the whole picture of one thing rather than the next step. [Benchmark](../concepts/benchmark.mdx) and [Job](../concepts/job.mdx) explain what happened during the tutorial; [Runtime licenses](../concepts/runtime-licenses.mdx) separates the two artifacts that both get called a license.
- **[How-to guides](../how-to/index.md)**: problem-shaped recipes. [Write a job definition](../how-to/write-a-job-definition.md) is where you go to add a benchmark the deployment does not carry yet, and [Manage members and API keys](../how-to/manage-members-and-api-keys.md) is the one every team needs on day two.
- **[Using the CLI](../cli/index.md)**: the platform from a terminal, from [the first command](../cli/get-started.md) to every `clika-cli` command with its arguments and flags. The CLI is how a benchmark run becomes a step in CI, since `clika-cli benchmarks watch` exits non-zero when a leg fails.
- **[Using with AI (MCP)](../mcp/index.md)**: hands the platform to an AI assistant such as Claude Desktop, Claude Code or Codex, as a set of tools it can call.
- **[ClikaRT](/clikart)**: the inference runtime the platform issues credentials for, and the library you link when you ship the model you measured. [Download the ClikaRT SDK](../how-to/download-the-clikart-sdk.md) is how a licensed deployment hands its members the runtime's release archives.
- **[Modelverse](/modelverse)**: the CLIKA model library, for packaged models that run on ClikaRT as they are.

Two things worth doing early with a real team:

1. **Name your runs.** The results view is built for comparison, and a run named for the question it answers is worth ten named "Untitled Benchmark".
2. **Give integrations their own API key.** A key carries a subset of its owner's permissions, so a CI job can dispatch benchmarks without holding an account's full access. [Manage members and API keys](../how-to/manage-members-and-api-keys.md) covers it.