Request headers
These are headers your application sends to Lectr on each request.X-Lectr-Key
Required. Identifies your organisation and authenticates the request.
Requests with a missing or invalid key are rejected immediately. The upstream
provider never sees them.
X-Lectr-Feature
Optional. Tags the request with the feature that made it.
Enables per-feature cost, latency, and error breakdowns in the dashboard.
Required for feature-based routing rules (coming soon).
See Feature Tagging for the full guide.
X-Lectr-Task
Optional. Declares the type of work the request is doing.
Treated as a high-confidence signal by the recommendation engine.
reasoning tasks are never recommended for model downgrade — hardcoded protection.
See Task Types for the full guide.
X-Lectr-Provider
Optional. Overrides automatic provider detection.
Use this when Lectr misdetects a provider or when a new model isn’t in the
detection registry yet. Always required for Azure since Azure endpoint URLs
are org-specific and can’t be inferred from the model name.
See Multi-Provider Setup for the full guide.
Authorization
Required. Your provider API key — forwarded directly to the upstream provider.
Your provider key is never persisted. Lectr normalises the auth header format
per provider — you always send
Authorization: Bearer, Lectr handles the rest.