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

# Quickstart

> Start using Clark in the Krypton app, or connect Clark in your own product after Krypton integration.

Clark is its own surface area: you can think of **Krypton integration** (accounts, KYC, payments) and **Clark** (assistant) as two components. This quickstart focuses on getting productive with Clark; it does not replace the main [Quickstart](/quickstart) for wallets and payments.

## In the Krypton app

<Steps>
  <Step title="Open Clark">
    Start a new chat from wherever Clark is exposed in the app.
  </Step>

  <Step title="Ask one clear question">
    Broad or specific is fine—Clark will ask follow-ups if something is missing.
  </Step>

  <Step title="Use the thread">
    Refine with follow-ups, change format, or switch topic; context stays in the conversation until you start fresh.
  </Step>

  <Step title="Approve anything that moves funds">
    If the answer involves Krypton Pay, read the summary and confirm only when you intend to proceed.
  </Step>
</Steps>

## In your own product

Use Clark when you already have (or are building) Krypton-backed users and want an assistant layer.

<Steps>
  <Step title="Complete core Krypton flows first">
    Users need a normal Krypton identity and auth path. Follow the [Krypton quickstart](/quickstart) for login, username, KYC where required, and payments if your app uses them.
  </Step>

  <Step title="Call the Clark API">
    Send questions with stable `user_id` and `session_id` so Clark can keep context and list conversations correctly. Request and response shapes live under **API reference → Clark API** (for example query, conversations, and memories).
  </Step>

  <Step title="Handle payment confirmations in the UI">
    When a response indicates that user approval is required before a wallet action, surface that in your client and only continue after the user confirms—same idea as in the Krypton app.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Clark introduction" icon="book-open" href="/clark/introduction">
    User journey and what Clark is for.
  </Card>

  <Card title="Clark API" icon="bot" href="/api-reference/introduction">
    Curated endpoints for query, conversations, and memories.
  </Card>

  <Card title="Krypton quickstart" icon="wallet" href="/quickstart">
    Accounts, KYC, and payments—the other component.
  </Card>
</CardGroup>