Getting Started
Dashboard User Guide
How to use each dashboard section, choose modes, and keep costs predictable.
9 minUpdated 2026-02-15
Summary
How to use each dashboard section, choose modes, and keep costs predictable.
4 deep-dive sections0 code samples
Quick Start
- Create account and generate your first API key.
- Run first request in API Explorer.
- Use Chat mode for first production prompt.
- Track charges and latency in Usage.
Dashboard map
Primary product surfaces
Chat
Run prompts with mode controls
Usage
Charged credits, tokens, replay
Credits
Wallet top-up + auto top-up
Settings
BYOK and privacy policies
Mode behavior
| Mode | Default charge | When to use |
|---|---|---|
| Chat | 1 credit | Default day-to-day prompting |
| Compare | 3 credits | Choose best model on the same prompt |
| Blend | 4 credits | Merge strengths of multiple models |
| Judge | 5 credits | Structured ranking and winner selection |
| Mesh | 1 credit | Failover path for reliability |
Suggested daily workflow
- Start in Chat with
AutoandBalancedgoal. - For critical prompts, run Compare before standardizing.
- Use Blend/Judge only for high-value outputs.
- Add Mesh chain for reliability-sensitive flows.
- Check Usage daily and Replay weekly.
How to read Usage page correctly
- Charged credits: what user wallet is billed.
- Latency: request performance for user experience.
- Tokens: workload profile for model selection decisions.
Trust and clarity
Use charged credits as the customer-facing billing source of truth. Keep provider-cost terms out of end-user billing copy.
Docs Assistant
ChatKit-style guided help
Product-scoped assistant for LLMWise docs and API usage. It does not answer unrelated topics.
Sign in to ask implementation questions and get runnable snippets.
Sign in to use assistantPrevious
Quick Start Guide
Next
Authentication and API Keys