PLATFORM
Dashboard workflow
Find models, Playground, Observe, Metrics, and billing in your workspace.
Overview
The selected organization controls which requests, credits, and settings you see. Confirm it first when something appears missing. Features and editing permissions depend on your account, role, and organization configuration.
| Area | What to do there |
|---|---|
| Overview | Check your workspace balance and copy a starter API request. |
| API Keys | Create and revoke keys, check last recorded metered use, set expiration, and configure traffic/spending limits. Long names wrap. |
| Playground | Try prompts, thinking settings and V4.1 image attachments before moving them into your application. Generating responses consumes credit. |
| Observe | Filter usage, inspect individual requests, and follow trace relationships where instrumentation supplies them. |
| Account → Metrics | Configure enabled evaluation checks and judge providers where your role permits it. |
| Billing | Add credit, inspect balance and charges, and reconcile organization usage. |
| Organization | Manage shared-workspace details, members, and invitations where your role permits it. |
From experiment to application
Start with a small Playground prompt. Confirm the answer and supported model settings, then translate the conversation to a Chat Completions request. Keep conversation history in your application when continuity is required. Use a distinct API key for each workload you need to attribute independently, and set practical limits.
With recording enabled, give the application a stable, non-sensitive X-Netra-Agent label, add tracing when you need visibility into multi-step runs, and check Observe after a representative request. Investigate usage and quality with a defined time range rather than relying on a single example answer.
The current dashboard focuses on inference and observation. Follow the current model catalog and documented inference endpoints when integrating your application.