What is LatentKit?
LatentKit is a route-based AI gateway for teams that want one integration surface and operator-controlled provider selection.
LatentKit sits between your application and AI providers. Your code sends standard task payloads; operators configure which providers and models each API key uses through published routes.
Route-based by design
Application requests do not choose a provider or model. Instead:
- You create an API key in the console.
- The key is assigned a published route (policy).
- Your app sends chat, embedding, or image payloads to
/v1/*. - LatentKit resolves the route and executes against eligible providers.
This keeps application code stable while operators tune cost, latency, and failover in the console.
BYOK and Platform Access
Routes can use bring-your-own-key (BYOK) provider connections or Platform Access managed credentials billed through LatentKit credits. The integration shape is identical — only billing and credential ownership differ.
First mental model
Think of LatentKit as three layers:
| Layer | Managed in | What it does |
|---|---|---|
| Application code | Your app | Sends task payloads like messages, input, or prompt |
| API key | Console | Authenticates the app and points to a published route |
| Route | Console | Chooses eligible provider/model attempts, failover, and response depth |
If the route changes, your application code usually does not.
Who this is for
- Product teams shipping AI features without hard-coding provider SDKs per model
- Platform teams that need centralized routing, usage tracking, and key management
- Developers using AI coding tools who want a secure backend integration pattern