> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conquoreum.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Minting your first API key

> How to mint, scope, and manage the cqk_ key your MCP or bridge authenticates with.

Every Reality Harness client — the MCP, the board-sync bridge, anything else — authenticates with a scoped `cqk_` API key. You mint it once, copy it immediately (Conquoreum shows it to you exactly one time and stores only a hash), and use it in your client's configuration.

## The guided path: the setup wizard

<Steps>
  <Step title="Sign in">
    Go to [app.conquoreum.com/deck/setup](https://app.conquoreum.com/deck/setup) and sign in with the same account you use on the Conquoreum iOS app.
  </Step>

  <Step title="Choose scopes">
    The wizard defaults to `devprogress:read` + `devprogress:write` — everything Level 1 needs. Add `rhp:outcome` here (or later, from the Key Console) if you already know you want Level 2.
  </Step>

  <Step title="Copy the key">
    The key is rendered once, in full. Copy it now — Conquoreum cannot show it to you again. If you lose it before pasting it anywhere, mint a new one; the old one still works until you revoke it.
  </Step>

  <Step title="Paste the generated config">
    The wizard hands you ready-to-paste Claude Desktop / Claude Code configuration with your key and the correct endpoint already filled in.
  </Step>
</Steps>

## Minting additional keys or scopes: the Key Console

Once you have one key, [app.conquoreum.com/deck/keys](https://app.conquoreum.com/deck/keys) is where you manage all of them — mint a new key with a different scope combination (e.g. adding `obsidian:sync` for Level 3), see prefix/label/scopes/created/last-used for every key, and revoke one you no longer trust. See [Rotating and revoking a key](/api-keys/rotating-and-revoking) for the full walkthrough.

## Minting from the iOS app

If you'd rather not use the web wizard, the Conquoreum iOS app offers the same capability under **Profile → Connected Apps → Add Reality Harness / Vision Harness** — pick your scope, and the app shows you the same one-time `cqk_` secret.

<Warning>
  Whichever path you use: never commit the key, never log it, and never paste it anywhere but your MCP client's own configuration (a local `.env` file or your client's `env` config block). If a key leaks, revoke it immediately from the Key Console.
</Warning>