AI access, designed to move faster.
Buy a key, connect your tools and track usage from one secure account.
Access
evolved
Multi-model access
Use one gateway with compatible clients and the models available to your key.
Usage control
Check quota, token totals, request count, RPM and available models when reported.
Secure delivery
Purchased keys, order history and verified wallet activity stay inside your account.
Configure your order
Prices, bonuses and availability come directly from the store configuration.
Check API Key
View usage, quota, models, requests and expiration.
•••Token quota
0.0%—
Token breakdown
Models available to this key
Usage by model
| Model | Type | Requests | Failures | Input | Output | Cache | Total |
|---|
Request history
Gateway reference
Connect your tools to kriss.laalaa.me.
Connect to the gateway
https://kriss.laalaa.me/v1https://api.laalaa.meAuthentication
Send your API key with either supported header.
Authorization: Bearer YOUR_API_KEY
x-api-key: YOUR_API_KEY
First request
OpenAI-style request example. Confirm the route and model with your customer key before using it in an application.
curl https://kriss.laalaa.me/v1/chat/completions \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"MODEL_ID","messages":[{"role":"user","content":"Hello"}]}'
Endpoints
| Method | Endpoint | Purpose |
|---|---|---|
| GET | /v1/models | Available models |
| POST | /v1/chat/completions | OpenAI chat completions |
| POST | /v1/responses | OpenAI Responses API |
| POST | /v1/messages | Anthropic messages |
| POST | /v1/images/generations | Image generation |
| GET | /v1/usage | Key quota and usage |
Inspect a key
Usage
curl https://kriss.laalaa.me/v1/usage \
-H "Authorization: Bearer YOUR_API_KEY"Models
curl https://kriss.laalaa.me/v1/models \
-H "Authorization: Bearer YOUR_API_KEY"The usage response includes status, quota, consumed tokens, remaining tokens, request count and key dates. Available models depend on the server assigned to the key.
Compatible Applications & Integrations
Integration availability depends on the model, endpoint, and features supported by the API. Some applications require additional configuration. A listing does not mean the integration has been tested.
Customer API configuration
- Base URL
https://kriss.laalaa.me/v1- API key
YOUR_LAALAA_API_KEY- Model
YOUR_SUPPORTED_MODEL_ID- Connection
- Custom OpenAI-compatible provider, plugin, or HTTP request. Claude Code uses its preserved Anthropic guide.
Keep keys in private credentials or environment variables. Never publish them in frontend source or shared examples. Browser clients may store keys locally; use a trusted client.
Compatibility labels
Custom API: documented configurable endpoint; Laalaa test required. Via extension / plugin: additional software required. Via HTTP request: generic HTTP connection. Advanced setup: adapter or version-specific configuration. Requires verification: complete setup not confirmed. No entry is claimed independently verified with Laalaa.
Request examples are illustrative until tested with a customer key. This review could not verify the customer gateway's routes; streaming, tool calls, images and embeddings are not guaranteed.
Existing setup guides
Claude Code
export ANTHROPIC_BASE_URL="https://api.laalaa.me"
export ANTHROPIC_AUTH_TOKEN="YOUR_API_KEY"
claudeCodex CLI — legacy chat configuration
Kept for existing installations. Current Codex requires wire_api = "responses"; see its catalog guide before using this older chat configuration.
model = "MODEL_ID"
model_provider = "laalaa"
[model_providers.laalaa]
base_url = "https://api.laalaa.me/v1"
env_key = "LAALAA_API_KEY"
wire_api = "chat"Cursor and Cline
- Provider: OpenAI compatible
- Base URL:
https://api.laalaa.me/v1 - Model: an ID returned by
GET /v1/models
OpenAI Python SDK
from openai import OpenAI
client = OpenAI(
base_url="https://kriss.laalaa.me/v1",
api_key="YOUR_API_KEY"
)HTTP status guide
| Status | Meaning |
|---|---|
400 | Invalid request |
401 | Invalid or missing key |
402 | Quota exhausted |
404 | Model unavailable to this key |
429 | Rate limit reached |
5xx | Gateway or upstream error |
Configured access
Orders, keys and wallet
Only records belonging to your account appear here.
Date created & API key
| Date created | API key |
|---|
Connect your accounts
Generate a code and send it to your Telegram bot to connect the same account.
Purchase history
| Order | Created | Server | Tokens | Total | Payment | Status |
|---|
Verified balance & transactions
Account notifications
Get order or setup help
Include your order ID when contacting support. Never send your full API key or payment secret.
Order help
For pending manual payments, wait for independent settlement verification. Screenshots alone are not proof of payment.
Technical help
Use the checker first, then include the model ID, endpoint and sanitized error message in your support request.
Account safety
We will never ask for your password or payment credentials. Customer API keys should only be entered in the secure checker.
Support history
Marketplace operations
Configure pricing, bonuses and sales readiness without editing code.
Server options
Syncs the documented reseller server-options endpoint. The vendor token remains server-side.
Packages and bonuses
| Package | Tokens | Bonus | Validity | RPM | Price | Status | Action |
|---|
Account overview
| Customer | Orders | Paid total | Last seen |
|---|