FAQ
Frequently asked questions about integrating with LatentKit.
Do I send a model name in requests?
No. LatentKit is route-based. The API key's assigned route selects provider and model execution. Application code sends task payloads only.
Can I use OpenAI SDKs directly?
LatentKit exposes a unified /v1 API and official @latentkit/sdk / latentkit packages. OpenAI-compatible drop-in is supported for many chat workloads by changing base URL and authorization, but route-based fields still apply — do not send model selection when using LatentKit routing.
Where do I get an API key?
Sign in at console.latentkit.com, open API Keys or AI Router, and copy the secret when the key is created.
Can I call LatentKit from the browser?
Store keys server-side. Browser clients should call your backend, which calls LatentKit with LATENTKIT_API_KEY.
What is response_profile?
An optional hint (fast, balanced, deep) for speed vs depth when the assigned route allows request overrides.
Is there a public API playground?
Not in this docs site. Use the logged-in console AI Router and Developers sections to run real workspace-scoped test requests.
How do I know which provider handled a request?
Application code should not choose providers directly. Check response metadata and console request logs to inspect the route attempt that succeeded. Operators can change provider/model routing in the console without redeploying your app.
Where is the full endpoint list?
This V1 docs site covers core integration paths. Additional /v1/* endpoints follow the same auth and routing model described in REST API overview. Full endpoint-by-endpoint reference is expanding in later releases.
How do vibe coding prompts work?
Open Build with AI (Vibe Coding), pick your AI tool and stack (Next.js, Laravel, FastAPI, etc.), and copy a safety-aware integration prompt. No live key injection — set secrets in your environment after copying.