Environments

DUST runs as three deployed services. Most integrations only need the DUST API; AuthD is reached through the API’s /api/auth/* paths.

Service	URL	Purpose
DICE web app	https://dice4.dustid.io	First-party web UI for DUST workflows.
DUST API	https://apid.dustid.io	Core API. Scalar reference at /api/docs.
AuthD	https://authd.dustid.io	Accounts, Organizations, sessions, OIDC, Service Accounts.

API paths

The DUST API exposes the platform under these roots:

Path	Use
/api/auth/token	Exchange an AuthD API key for a bearer token.
/api/auth/jwks	Fetch AuthD JWKS through the DUST API.
/api/v1/*	Core DUST API operations.
/api/openapi.json	Generated OpenAPI spec served by the API.
/api/docs	Interactive Scalar reference.

See the API Reference for the full generated endpoint catalog, and Conventions for the request context headers every call carries.

Health endpoints

The DUST API serves standard health probes at the server root (not under /api):

Path	Check	Failure behavior
/livez	Liveness — the process is up.	Always 200 while the server runs.
/readyz	Readiness — includes a database round-trip.	503 if the database check fails or exceeds its 2-second timeout.
/healthz	Alias for the readiness check.	Same as /readyz.

All three return { "status": "ok", "timestamp": "…" } when healthy; the readiness checks return { "status": "error", … } with a 503 when not. Point uptime monitors at /readyz (or /healthz).