Environments & Endpoints
Environments
| Environment | Base domain | Credential class | Purpose |
|---|---|---|---|
| Development | dev.apex.reisiger.org |
apex_test_… keys, development machine-to-machine clients |
Build and integration testing |
| Production | apex.reisiger.org |
apex_live_… keys, production machine-to-machine clients |
Live traffic |
| Staging | staging.apex.reisiger.org |
— | Planned; not yet provisioned |
Cloud base URLs follow one pattern: https://{product}.{base domain}. All cloud traffic is HTTPS. Never mix credential classes across environments — see Authentication.
Your token endpoint is not derived from these domains: it is issued in your credential bundle (token_url). Always read it from configuration.
Product endpoints
| Product | Development base URL | Local / companion port | Notes |
|---|---|---|---|
| Zenith | https://zenith.dev.apex.reisiger.org |
9100 | Available |
| Forge portal | https://forge.dev.apex.reisiger.org |
9140 | Available |
| Forge support service | operator-arranged | 9142 | Preview — local/companion deployments today |
| Forge LLM gateway | https://forge.dev.apex.reisiger.org |
— | Planned — contract pinned, not yet served |
| Vector | https://vector.dev.apex.reisiger.org |
9120 | Available |
| Prism | https://prism.dev.apex.reisiger.org |
9150 | Available |
| Echo | https://echo.dev.apex.reisiger.org |
9160 | Available |
| Document Operations | issued by your platform operator | 9190 | Available (cloud base URL operator-issued) |
| Pulse | https://pulse.dev.apex.reisiger.org |
9141 | Preview |
| Quantum | local only | 9130 | Preview — no cloud deployment yet |
"Local / companion port" applies only when your platform operator arranges a local or companion deployment of APEX services alongside your stack; most integrations use the cloud URLs exclusively.
Production availability
Production is enabled product-by-product per tenant as part of go-live, and not every product listed above is served in production for every tenant. Confirm your production base URLs and enabled products with your platform contact before cutover — do not assume development parity.
Health checks
Every product serves a minimal liveness endpoint: GET /health (Forge portal: GET /api/health). Use it for smoke tests and uptime monitors.
Health is not an entitlement check. A healthy product can still refuse your tenant (404 — not configured; 403 — not entitled). The definitive "am I onboarded" probe is a real tenant-scoped call, e.g. Zenith GET /api/v1/{tenant}/config as shown in the Quickstart.
Discovery
Each product also serves GET /forge-contract.json — its machine-readable composition contract (identity, endpoints, events, tools). Pin it in CI to catch surface drift early; see Integration Conventions.