LLM Gateway overview
Updated on 3 November 2026.
The LLM Gateway sits between your applications and your LLM providers. Your application continues to use its existing SDK. Change the base URL and the API key to route requests through the gateway, apply configured controls, and record usage, cost and latency.
Key concepts
Provider credentials stay in the gateway. Developers only ever see the Quilr key.
The LLM Gateway page
Go to Settings > AI Gateway > LLM Gateway. The page has two tabs: Applications and Management API (see Management APIs).
Below the cards, the Providers & models strip lists your platform providers and opens Provider configuration.
Click any number on a card to filter the app list. Below the cards, search by app, key, provider, model, creator or tag, and filter by attention, status or provider.
The app card
Each app in Configured Apps has a card.
Analytics and insights
Overall analytics opens a full page with Overview, Agents & tools, Performance & errors, Security, Attachments, and Users tabs. Choose the application scope and reporting period, then select a chart, signal or app for its supporting details.
See Analytics and insights for each tab, comparisons, estimates and drilldowns.
The app workspace
The app card's Inspect and Configure actions open operational views for that application. For example, Logs opens Activity > Requests, while Providers opens the matching Settings section. Use the application picker to change scope; Settings needs exactly one app.
Settings sections
When the Policy Engine is on, sections marked with its icon (Routing, Security Guardrails, Guardian Agent, Attachments, Rate and Token Limits, Token Saving, Identity Aware, Prompt Store) follow published policies instead of these settings. Providers, keys and the other sections are still managed here.
Self-service usage
Self-service usage reports who can view each app, request changes, edit settings directly, view keys, or view all logs, along with their usage. Tabs: Users, Applications, Change history.
See Self-Service to set it up.
Next steps
- Quick Start: create an app and send a first request.
- Analytics and insights: review model usage, performance, protection and callers.
- Applications and Keys: add keys, set expiry, roll back changes.
- Provider Support: every provider type, endpoint and credential field.
- Integration Guide: regional URLs and SDK examples.