Introduction

LatentKit gives your application one API surface for chat, completions, embeddings, images, vision, audio, video, and more. You send task-shaped requests; the API key's assigned route selects the provider and model at runtime.

What you get

• One base URL: https://ai.latentkit.com
• One authorization model: Authorization: Bearer <api-key>
• Route-based routing: change providers in the console without redeploying app code
• Automatic failover across providers with one response back to your app
• Official JavaScript 0.2.2, Python 0.2.1, and PHP 0.1.0-beta.3 SDKs for the /v1 API
• Official CLI 0.1.0 for browser login, runtime tests, logs, traces, routes, keys, and CI checks
• Official WordPress, Drupal, Laravel, and Vercel AI SDK integrations with explicit release and review status

Start here

1. Quickstart — create a key and send your first request
2. CLI — sign in from a terminal, test requests, inspect logs, and automate checks
3. JavaScript SDK, Python SDK, or PHP SDK beta — call LatentKit from app code
4. WordPress, Drupal, Laravel, or the Vercel AI SDK provider — connect an existing platform
5. Core concepts — routes, keys, capabilities, and the request lifecycle
6. Models & providers — what the catalog supports per modality
7. Providers and Playground — verify route/provider readiness in the console
8. Build with AI — generate safe prompts for Cursor, Windsurf, Claude, and other AI tools

Current SDK and integration releases

Everything the API supports

Console companion

After sign-in, the LatentKit console includes workspace-aware developer tools: selected API key, route status, and copyable examples. The CLI can use browser login for account-scoped inspection from your terminal. Public documentation lives here; the console and CLI add live workspace context.