Gateway route map
This page summarises the mountAPI surface in cmd/atlas-gateway/main.go.
Regenerate or extend it when adding routes so the reference stays honest.
IAM proxy
Section titled “IAM proxy”When ATLAS_IAM_HOST is set, the gateway mounts a reverse proxy so the SPA can call IAM at same-origin /iam/* (see mountIAMReverseProxy in main.go). Typical paths: /iam/v1/me/bootstrap, /iam/v1/invites/....
Core workbench
Section titled “Core workbench”| Method | Path | Notes |
|---|---|---|
POST | /api/atlas/contact | Landing / marketing contact form (JSON); persists to contact_submissions |
GET/POST | /api/atlas/resolve | Resolver |
POST | /api/atlas/traverse | Keystone traverse |
GET | /api/atlas/artifacts, /guidance, /documents, /corpus | Corpus reads |
GET | /api/atlas/plan/versions | Planner versions |
GET | /api/atlas/planner/llm-status | Planner LLM health snapshot |
POST | /api/atlas/plan | Plan creation |
POST | /api/atlas/answer/stream | Synthesised answer SSE |
Operations
Section titled “Operations”| Method | Path | Notes |
|---|---|---|
GET | /api/atlas/corpus/status | Corpus phase + collectors |
GET | /api/atlas/graph/status | Graph outbox |
POST | /api/atlas/corpus/extract | Extraction pass |
POST | /api/atlas/corpus/recrawl | Alias → extract |
POST | /api/atlas/graph/rebuild | Requeue + drain |
Cases & lifecycle
Section titled “Cases & lifecycle”Case CRUD, evidence, bundles, estimates, plan lifecycle, and webhooks are mounted in the same router group — see the source file for the full list.