The control plane for
production AI traffic.
One baseURL change. Instant visibility into cost, latency, and failures — by feature, by model, by provider. Route traffic at runtime without touching your code.
Overview
Control Surface
Operational Metrics
Last 24h ▾12.4
1,789 total
0.8%
14 failures
1.24s
Within target
$0.004
$0.10 total
Provider Execution
| Provider | Requests | Avg Latency | Success | Status |
|---|---|---|---|---|
| OpenAI | 1,234 | 890ms | 99.2% | Healthy |
| Anthropic | 412 | 1.1s | 98.8% | Healthy |
| Groq | 143 | 234ms | 100% | Healthy |
The problem
AI traffic is invisible by default
Most teams ship AI features and lose track of them immediately. There is no central view of what is running, what it costs, or where it is failing.
Costs that appear without warning
AI costs compound across models and features with no central view. By the time you notice a spike, it has already happened.
Traffic you cannot see or control
Which feature is sending the most tokens? Which model is failing silently? Without observability, these questions go unanswered.
Providers with no fallback path
A provider outage or latency spike becomes a feature outage. Teams patch it manually, every time.
Routing decisions buried in application code
Every model swap or feature-level override is a code change and a deployment. There is no runtime control.
Capabilities
One proxy. Complete control.
Lectr sits in front of your AI providers and gives you visibility, cost attribution, and routing control — without changing how your application works.
See every request in real time
Full request log with model, latency, token usage, cost estimate, and status across every AI call. Understand traffic distribution by provider and feature at a glance.
Req/min · P95 latency · error rate · cost/hr · token usage
Break down spend by feature and model
Cost attributed to each feature, model, and provider. Set spend caps — when a threshold is hit, Lectr falls back to a cheaper model automatically.
Spend caps · alerts · model-level breakdown · CSV export
Route traffic without application rewrites
Define routing rules in the dashboard. Send cost-sensitive features to smaller models, route latency-critical paths to faster providers. Changes take effect immediately — no redeploy required.
Conditions: feature tag · task type · provider · model · priority
Surface problems before they become incidents
Automatic detection of unusual request volume, error rates, latency spikes, and cost anomalies. Review and investigate with a full timeline of what changed and when.
Automated detection · dismiss workflow · baseline learning
Set limits that protect against runaway spend
Define per-org and per-feature budget policies with soft and hard caps. Set P95 latency targets. Rate limits are enforced via Redis, shared across all proxy instances — no single point of failure.
Hard caps · soft caps · latency targets · rate limiting · per-org enforcement
How it works
Ship in minutes. Not months.
Lectr is designed for teams that move fast. Getting started is a one-line change. Everything else builds from there.
Your App
openai.chat()proxy.lectr.ai/v1
observe · route · control
+ Gemini, Azure
Point your app at Lectr
Swap the base URL in your OpenAI client. Add your org key header. That is the entire integration — no SDK changes, no rewrites.
Tag requests by feature
Add an optional X-Lectr-Feature header to attribute traffic. Cost and latency are broken down per feature from day one.
See everything. Control everything.
Every request is logged. Set routing rules and budget limits from the dashboard — changes apply immediately, no redeploy.
Integration
One line to get started
Change the base URL. Add your org key. That is the entire integration. Your existing code keeps working exactly as before.
from openai import OpenAI
client = OpenAI(
api_key="sk-your-key",
)
resp = client.chat.completions.create(
model="gpt-4o-mini",
messages=[...],
)from openai import OpenAI
client = OpenAI(
base_url="https://proxy.lectr.ai/v1",
api_key="sk-your-key",
default_headers={
"X-Lectr-Key": "lc_your-org-key",
"X-Lectr-Feature": "chat" # optional
}
)Privacy guarantees
Start controlling your AI traffic
Full visibility over your AI traffic. Routing and budget controls from the dashboard — no redeploy required.