Playground
Test real workspace requests in the console before wiring production code.
The public docs site does not run live API requests because real calls require a workspace API key, billing context, and route assignment. Use Playground in the logged-in console for real execution.
Which console tool to use
| Tool | Best for |
|---|---|
| Playground | Chat, image, and embeddings test requests through a selected API key, on the same runtime path as production traffic |
| API Keys | Creating keys and assigning routes; a key's Credentials tab rotates, revokes, or adds secrets |
| Routes / AI Providers | Which route entries are eligible for an endpoint, provider connection health, and enabled models |
| Usage | Debugging request ids, failures, latency, and spend from Recent requests |
Recommended first test
- Open console.latentkit.com. A new workspace starts with guided setup, which ends by creating your first API key.
- Go to Playground.
- Select the API key your application will use.
- Confirm the key has a published route assigned — see the key's Route tab in API Keys.
- Run a plain chat test first, then image generation or embeddings if your app uses them. Playground runs are non-streaming; test streaming and tool calls from your backend.
- Copy the matching example from the Quickstart or the REST API overview into your backend.
Why start in the console?
The console validates the integration prerequisites that code examples cannot see:
- The key is active and unrevoked.
- The key has a published route.
- The route has eligible models for the endpoint capability.
- Provider access is connected and healthy.
- Credits, plan limits, or BYOK credentials can execute the request.
If a console test fails, fix route/provider/billing state first. If the console test succeeds but your app fails, compare headers, environment variables, and request body shape.
Production checklist
- Store
LATENTKIT_API_KEYin server-side secrets. - Log
X-LK-Request-IDfor failed responses. - Keep browser clients calling your backend, not LatentKit directly.
- Avoid sending provider/model selection in request bodies.