JJijibora Docs
docs.jijibora.online
On this page (5 sections)

API Inventory — Complete Codebase Coverage

<!-- GENERATED by scripts/extract-api-inventory.mjs — do not hand-edit; edit apps//src and re-run. --> Scope: every HTTP route literal under apps//src, plus outbound calls, plus Camel and Kestra surfaces. Status: generated 2026-11-09 from apps//src + apps/agent-bff/openapi/.json — regenerate with node scripts/extract-api-inventory.mjs. How to read this: "spec" = COVERED means a matching operation exists in the OpenAPI specs; "— (no spec)" means the route exists in code but has no spec entry yet. All "— (no spec)" rows are real, callable endpoints — the spec is behind the implementation.

Coverage summary

SurfaceRoute uniquesCovered by specUncovered
agent-bff36554983157
akili-mcp-server202
app-bff51348
appwrite-bff91586
auth-api808
dev-portal927
email-courier-service826
fsm-worker211
gravitus-admin000
jamii-bff211
sovereign-api1651164
sovereign-backend1046
supabase-bff39435
truth-bff2541253
Total (HTTP server routes)42965223774

OpenAPI spec operations in the published OpenAPI specs: 610 (across 18 specs). The generated per-spec renders live in the generated API reference set; this inventory is the implementation truth the specs are measured against.

Spec coverage by service

Per-app files

AppDoc
agent-bffAgent BFF — route inventory — 3655 routes
akili-mcp-serverAkili MCP Server — route inventory — 2 routes
app-bffApp BFF — route inventory — 51 routes
appwrite-bffAppwrite BFF — route inventory — 91 routes
auth-apiAuth API — route inventory — 8 routes
dev-portalDev Portal — route inventory — 9 routes
email-courier-serviceEmail Courier — route inventory — 8 routes
fsm-workerFSM Worker — route inventory — 2 routes
gravitus-adminGravitus Admin — route inventory — 0 routes
jamii-bffJamii BFF — route inventory — 2 routes
sovereign-apiSovereign API — route inventory — 165 routes
sovereign-backendSovereign Backend — route inventory — 10 routes
supabase-bffSupabase BFF — route inventory — 39 routes
truth-bffTruth BFF — route inventory — 254 routes
Outbound callsOutbound integrations — calls to external services — 15 calls to external services

Non-HTTP surfaces

Apache Camel routes (Camel route sources): 63 files — NATS-subject protocol translators (egress.camel. → ingress.camel..response). See the Camel gateway design.

Kestra flows (Kestra workflow sources): 26 files — scheduled/managed workflow timers and DAGs (e.g. claims-sla-timeout).

Methodology and limits

  • Route literals are extracted statically from .get/.post/.put/.patch/.delete/.all/.head/.options( call sites. Dynamically constructed paths (template literals, variables) cannot be enumerated; they appear here as literals where resolvable.
  • Router mounts (app.use of sub-routers) are resolved best-effort from apps/agent-bff/src/index.js; unresolved mount-relative routes keep their literal path and are still listed.
  • Outbound calls (https://... targets) are calls this platform makes to external services (Discord, Slack, Twilio, Telegram, Meta, Anthropic, Google) — see outbound-integrations.md.
  • Coverage is exact after normalising Express :param to OpenAPI {param}. A spec path that differs only by parameter name is intentionally reported uncovered.