AI features
Where models sit in Glimrel
Four named jobs on LLM traffic. Each card is a feature: what it does, who it is for, and the route. Glimrel routes, traces, and grades model calls. It does not train those models, and it does not ship agents.
AI feature · Multi-model routing
One host across the families you already call
For platform teams wiring OpenAI, Anthropic, Gemini, Llama, Nova, or Groq
Keep the OpenAI-shaped client. Change the base URL and the key. Fallbacks, caches, and spend caps attach to that key. Planned access paths: Bedrock, Anthropic, OpenAI direct, Groq, Hugging Face.
SDK → Glimrel gateway → provider fallback → POST /v1/chat/completions
AI feature · Nested LLM traces
Tools, retrieval, and retries as spans
For engineers debugging agent and RAG traffic
Every completion, tool call, and retry is a span you can search. Customer, prompt version, and cost sit on the tree. This is observability for LLM traffic — not a chatbot.
Request → nested spans → GET /v1/traces/{id}
AI feature · LLM-as-judge evals
The CI grader scores a live sample
For quality leads who refuse silent drift
LLM judge, code check, or human. The same scorer that already sits in CI runs on a sample of production spans. Prompt versions that drop faithfulness get held.
Sample prod → same grader as CI → POST /v1/evals/runs
AI feature · Agent traffic plane
LangChain and Assistants sit on the gateway
For teams that already ship agents
Glimrel is the plane under agent frameworks (LangChain, OpenAI Assistants, homebrew). It does not choose tools or act as an agent. Spend caps halt traffic at the limit you set.
Agent SDK → one Glimrel key → route, trace, grade
Model families on the route sheet: Claude 3.7 Sonnet, GPT-4o / GPT-4o mini, Gemini 2.5, Llama 3 70B, Amazon Nova, Groq. Glimrel does not train those models. MVP stage — no invented customers or uptime claims on this page.