API reference for Clark
If you are wiring Clark into your own app, use the Clark API section for request and response shapes.
What Clark helps with
Clark is built around how people use Krypton—not around internal systems. In practice you can:- Research and compare assets and market context.
- Dig into data such as prices, indicators, and historical series when your question needs it.
- Explore scenarios like strategy or portfolio ideas, including backtests when that fits the question.
- Stay informed on regulatory and policy context relevant to crypto and trading.
- Act through Krypton Pay when your flow includes balances, swaps, or transfers—Clark will pause for your confirmation before anything sensitive happens.
A typical journey
Open the conversation
You start from the Krypton app or an integration that exposes Clark. Your first message might be broad (“What’s moving in DeFi this week?”) or specific (“Compare these two tokens”).
Refine with follow-ups
Clark keeps the thread coherent. You can narrow the topic, change timeframe, or ask for a different format—summary, bullets, or step-by-step—without restating everything.
Let Clark remember what matters
Within a session, context carries forward so follow-up questions make sense. Over time, Clark can reflect stable preferences (for example how you like answers formatted or which areas you care about) so new sessions still feel familiar.
Confirm when money is involved
If a request touches payments or wallet actions, Clark explains what would happen and waits for your explicit go-ahead before proceeding. Nothing moves without that step.
What you do not need to worry about
- Picking “the right tool.” You describe intent; Clark handles the rest.
- Session IDs and memory APIs unless you are building an integration—in the app, that is handled for you.
- Raw market plumbing unless you want it—Clark is meant to answer in plain language first.
Clark quickstart
Practical steps to get value from Clark in the app, or to connect it in your product.