Luger v1
luger-v1Fast and cheap
Text processing, short questions and routine integrations where cost comes first.
- Input
- $0.40
- Output
- $1.60
- Cached input
- $0.14
USD per 1 million tokens
Development and research. Authorized security research — connect Luger to your own tools and workflows.
API
One OpenAI-compatible host: https://luger.ai/v1. Models luger-v1 and luger-v2. The same balance as the chat; the API spends paid money only. Top up from $5.
luger remains an alias of luger-v1. Responses use the canonical version ID. Both versions use the same key and balance.
luger-v1Fast and cheap
Text processing, short questions and routine integrations where cost comes first.
USD per 1 million tokens
luger-v2Main: code, tools, images in
Multi-step tasks, code review, long context and images. Tool calls, parallel tools, JSON schema output. Up to 262k output tokens.
USD per 1 million tokens
The example assumes no cache hit. A request includes your message, conversation history and tool results. Reasoning tokens count as output. Each completed call returns its usage and cost.
Same server, same three prompts, streaming, one run each on 2026-10-27. Time to first token and tokens per second are upstream numbers, not a guarantee. v1 answered the JSON task fastest; v2 wrote the code and the proposal several times faster and in more detail.
| Task | v1 · first token | v1 · total | v2 · first token | v2 · total | Output, tokens |
|---|---|---|---|---|---|
| JSON: arithmetic, sorting, three risks | 0.6 s | 1.1 s · 212.6 t/s | 2.0 s | 2.5 s · 280.8 t/s | 113 / 136 |
| Single-file Pomodoro in HTML/JS | 38.8 s | 42.9 s · 284 t/s | 9.1 s | 13.7 s · 807.2 t/s | 1159 / 3747 |
| Five-section research proposal | 0.6 s | 5.4 s · 171.3 t/s | 4.3 s | 6.6 s · 401.8 t/s | 810 / 916 |
Three steps
1 · Sign in and create a key
Cabinet → Create. The secret starts with lgr_ and is shown once.
2 · Point the host at Luger
Base URL https://luger.ai/v1 — no trailing slash, no /chat/completions.
3 · Set a monthly cap
In the cabinet, so a loop cannot empty the balance.
POST /v1/chat/completions
curl https://luger.ai/v1/chat/completions \
-H "Authorization: Bearer $LUGER_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "luger-v1",
"messages": [
{
"role": "user",
"content": "Reply in one word: ready."
}
],
"stream": true
}'The key stays in the browser. The call hits the API and spends balance, same as Cursor.
Chat Completions supports streaming, tool calls and JSON mode. Your application executes tools and validates their results.
Input / 1M
$0.40
Output / 1M
$1.60
Cache read / 1M
$0.140
Millions of tokens. Cache is a share of input.
$19.24
Host https://luger.ai/v1, model luger-v1. Do not append /chat/completions. The key is in the cabinet. Set a monthly cap there so a script cannot spend the whole balance.
GET /v1/balance with the same key returns balance_usd and this month's API spend.
OpenAI API Key: lgr_... Override OpenAI Base URL: https://luger.ai/v1 Model: luger-v1
How is the price calculated?
Input, cache reads, and output are separate. Before a request runs, its maximum cost is reserved; after the reply only the real cost stays charged and the rest returns at once. A request cannot exceed the balance or the key's monthly limit. Each response carries usage.cost in dollars.
How do I top up?
In the cabinet, with crypto. Minimum $5. It lands on the same account.
Is this a separate balance from the chat?
No. One balance covers the chat and the API. The API spends paid money only.
Is the context window a million tokens?
The API context window is 1,048,576 tokens; in-app chat keeps 400,000 characters of history for everyone.