Admin and Tenants¶
Release binding: v0.1.0-enterprise-ready · AMI ami-010806d4d3445660e · 2026-05-19
Administration splits across two surfaces: the gate's own routes (tenant lifecycle, usage) authenticated with the bootstrap admin key, and engine admin routes (/v1/admin/*) proxied through the gate.
Tenant model¶
A tenant is an operator-defined profile, not a billing plan:
| Field | Default | Meaning |
|---|---|---|
tenant_id |
required | Stable identifier |
namespaces |
required | Namespace ACL for the tenant's key |
tier |
starter |
Operator-defined label; carries no pricing meaning |
rate_limit_requests |
100 | Requests per window for this tenant |
rate_limit_window_s |
60 | Window length in seconds |
quota_cus_monthly |
0 | Monthly CU quota; 0 means unlimited |
A tenant created without a quota is unlimited. Setting quota_cus_monthly makes the gate return 503 with a descriptive body once the monthly total is exceeded; counters reset on the first of the month (UTC). See Metering.
Gate onboarding routes¶
| Route | Purpose |
|---|---|
POST /gate/onboard/create |
Create a tenant; the response carries the tenant key, shown once |
POST /gate/onboard/rotate-key |
Rotate a tenant key; the old key stops working immediately |
POST /gate/onboard/add-namespace |
Extend a tenant's namespace ACL |
POST /gate/onboard/update-tier |
Update the tenant's label and quota_cus_monthly |
POST /gate/onboard/deactivate |
Deactivate a tenant |
Gate admin routes¶
| Route | Purpose |
|---|---|
GET /gate/admin/tenants |
List tenants |
GET /gate/admin/usage |
Usage totals across tenants |
GET /gate/admin/usage/{tenant_id} |
Usage for one tenant |
POST /gate/admin/reload |
Reload gate configuration |
Exact corpus registry¶
The EXACT path serves from a registered raw corpus per namespace.
| Route | Purpose |
|---|---|
POST /v1/admin/corpus/register |
Register a raw corpus for a namespace |
GET /v1/admin/corpus |
List registered corpora |
DELETE /v1/admin/corpus/{namespace} |
Unregister a namespace's corpus |
POST /v1/admin/ingest/from_exact_corpus builds the serving index in place from a registered corpus, with row_start support for sharded runs.
Diagnostics and maintenance¶
| Route | Purpose |
|---|---|
GET /v1/admin/diagnostics |
Engine diagnostics |
GET /v1/stats |
Store and index statistics |
POST /v1/admin/compact |
Reclaim tombstoned space |
POST /v1/admin/classify |
Run classification for a namespace (see Retrieval Classes) |
Intelligence and telemetry¶
Read-only telemetry for operators and the Console:
GET /v1/intelligence/dashboard, /accuracy, /alerts, /billing, /calibration, /rescue.
The /v1/intelligence/billing route reports CU accounting state; it is a metering view, not an invoice.