Skip to content

Layerr Documentation

Self-hosted orchestration intelligence for AI coding agents

Layerr is a self-hosted orchestration runtime that sits between your AI coding agents and every LLM provider. It is not a router, it is an intelligence layer that classifies intent, analyses workloads, selects strategies, scores providers, and continuously learns from outcomes.

LayerPurposeDocumentation
1Intent ClassificationWhat is the request asking for?
2Workload AnalysisWhat language, stack, complexity?
3Workspace ProfilesPer-workspace configs, budgets, policies
4Strategy EngineCost, speed, quality, balanced
5Provider ScoringScore and rank every candidate
6Execution EngineSend, stream, retry, fallback
7ExplainabilityWhy was this model chosen?
8Replay & ComparisonRecord, replay, compare traces
9Adaptive LearningLearn from outcomes and improve
10Quality EvaluationBenchmark, calibrate, score quality
11Provider EconomicsTrack costs, simulate alternatives
12Entitlements & SecuritySecrets, rotation, isolation, guardrails
  • 1,090 source files
  • 135 API routes
  • 715 auto-detected communities
  • 21,978 symbols
  • 35,702 relationships
  • 300 execution processes
  • 12 intelligence layers
SectionWhat You’ll Find
OverviewHigh-level architecture, routing, economics, evaluation, replay
Intelligence LayerDeep-dive into every intelligence layer
API ReferenceComplete API documentation for all 135 routes
DomainsDomain-specific deep-dives: providers, routing, tenant isolation
Terminal window
curl -X POST http://localhost:3000/v1/chat/completions \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "layerr-auto",
"messages": [{"role": "user", "content": "Write a React counter component"}]
}'
Terminal window
curl -X POST http://localhost:3000/api/workspaces \
-H "Authorization: Bearer YOUR_ADMIN_KEY" \
-H "Content-Type: application/json" \
-d '{
"slug": "my-app",
"name": "My Application",
"strategy": "quality",
"budget": {"monthly": 100}
}'

Documentation generated from live codebase analysis via GitNexus. Last updated: May 30, 2026.