In the Krypton app
1
Open Clark
Start a new chat from wherever Clark is exposed in the app.
2
Ask one clear question
Broad or specific is fine—Clark will ask follow-ups if something is missing.
3
Use the thread
Refine with follow-ups, change format, or switch topic; context stays in the conversation until you start fresh.
4
Approve anything that moves funds
If the answer involves Krypton Pay, read the summary and confirm only when you intend to proceed.
In your own product
Use Clark when you already have (or are building) Krypton-backed users and want an assistant layer.1
Complete core Krypton flows first
Users need a normal Krypton identity and auth path. Follow the Krypton quickstart for login, username, KYC where required, and payments if your app uses them.
2
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).3
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.
Next steps
Clark introduction
User journey and what Clark is for.
Clark API
Curated endpoints for query, conversations, and memories.
Krypton quickstart
Accounts, KYC, and payments—the other component.