Service readiness.
Readiness reflects the checks below. This page also describes the configured service. For machines, use the status, readiness, and architecture JSON endpoints.
The hosted app runs as a long-lived Python service instead of a serverless function.
App metadata and workspace Engram schemas live in Postgres.
Health and service status endpoints expose basic uptime and public counts.
Usage, audit, ingest runs, and export routes help operators inspect behavior.
/api/health, /api/service/status, and /api/service/readiness.bounded readiness checks
runtime target
workspace storage
capability entries
Readiness checks
The readiness route is bounded so a broken database connection cannot hang an operator dashboard forever.
Database
The check completed inside the service readiness budget.
Runtime Cache
0 warm runtimes from a max of 16.
Security Config
The check completed inside the service readiness budget.
Public Surface
5 public service contract routes are wired.
Operational endpoints
Useful URLs for operators and uptime checks.
| Endpoint | Purpose | Auth |
|---|---|---|
/api/health | Minimal public health check. | None |
/api/service/status | Public service metadata and feature count. | None |
/api/service/readiness | Bounded database, runtime cache, security, and surface checks. | None |
/api/service/architecture | Runtime, storage, model, limit, security, and route contract. | None |
/api/service/deploy-plan | Release script, preflight checks, remote shape, and live checks. | None |
/api/workspaces/{slug}/usage | Workspace API activity and route counts. | Workspace key |
/api/workspaces/{slug}/observability | Workspace latency, failures, slow routes, cache, and ingest health. | Workspace key |
/api/workspaces/{slug}/audit | Workspace audit history. | Workspace key |
/openapi.json | Machine-readable API contract. | None |