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

# Quickstart

> Authenticate and ask an executive your first question in five minutes.

This guide takes you from zero to your first governed AI response.

## Prerequisites

<Steps>
  <Step title="An Operark account">
    Sign up at [app.operark.com](https://app.operark.com) and create an
    organization.
  </Step>

  <Step title="An API key">
    In the dashboard, go to **Settings → API Keys** and create a key. Copy it
    immediately — it is shown only once.
  </Step>
</Steps>

<Warning>
  Treat your API key like a password. It carries the full access of your
  organization. Never commit it to source control or expose it in a browser.
</Warning>

## 1. Set your key

```bash theme={null}
export OPERARK_API_KEY="YOUR_API_KEY"
export OPERARK_BASE_URL="https://api.operark.com"
```

## 2. List the available executives

Every organization has the same 15 runtime agents. List them to confirm your
key works:

```bash theme={null}
curl "$OPERARK_BASE_URL/api/v1/executives" \
  -H "Authorization: Bearer $OPERARK_API_KEY"
```

## 3. Ask an executive a question

Ask the CFO (`AI_CFO`, "Nova") a finance question:

```bash theme={null}
curl -X POST "$OPERARK_BASE_URL/api/v1/executives/AI_CFO/ask" \
  -H "Authorization: Bearer $OPERARK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "What should we watch in next quarter cash flow?"
  }'
```

The response includes the executive's answer plus governance metadata — the
session id, any tools used, and the decision lineage when applicable.

## 4. Request a decision

`ask` is advisory. When you need a recorded, governed decision, use `decide`:

```bash theme={null}
curl -X POST "$OPERARK_BASE_URL/api/v1/executives/AI_CRO/decide" \
  -H "Authorization: Bearer $OPERARK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "Approve a new vendor with SOC 2 Type II but no ISO 27001?"
  }'
```

Decisions are written to the audit trail and may route through approval or a
Sentinel (CRO) veto depending on your governance configuration.

## Next steps

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/authentication">
    Key types, scopes, and rotation.
  </Card>

  <Card title="The agents" icon="users" href="/concepts/agents">
    Who the 15 runtime agents are and what they own.
  </Card>

  <Card title="Governance" icon="scale-balanced" href="/concepts/governance">
    Approvals, the audit trail, and the veto model.
  </Card>

  <Card title="SDKs" icon="cube" href="/sdks/typescript">
    TypeScript, Python, and Go clients.
  </Card>
</CardGroup>