LegalAI

Workspace

  • Dashboard
  • Upload
  • Documents
  • AI Assistant

Analysis

  • Review Queue
  • Knowledge Graph
  • Evaluation

Platform

  • Model Router
  • Analytics
  • Admin

Resources

  • Documentation
  • Architecture
  • Research
  • About
  • Settings
  • Back to website
GitHub
Sign in

Administration

Users, routing policy overrides, the Class-C egress log, feature flags, and backend health. Write actions require an admin role.

OverviewUsersModelsEgress LogFeature Flags

API

checking…

Model Router

0/0 providers reachable

Knowledge graph

no health endpoint — checked per request

Policy

v—

Provider reachability

API keys

API keys are issued by a backend script, not an endpoint — there is no create-key API to call from here.

python scripts/create_api_key.py "My Org" "my-key-name" [role]

The raw key is printed once. Only its SHA-256 hash is stored. Send it as Authorization: Bearer lai_… on every request when AUTH_REQUIRED=true. Per-user login (the sess_ token) is managed under the Users tab.

Routing policy

The policy lives in app/policies/routing.yaml (version-controlled). Each task maps to an ordered candidate chain; a Class-C provider is appended only when external providers are enabled and the sensitivity tier is in class_c_allowed_tiers.

external providers off

Per-task Class-C kill switches are on the Models tab.