Standalone API

Xoro API is now a dedicated service boundary

This app is the first standalone Xoro service. It now owns Xoro session, workspace, credential, site, artifact, release, deployment, and domain routes directly, while Silk-dependent legacy flows still forward into the compatibility layer until the adapter boundary is extracted.

Current mode

Hybrid extraction: direct ownership for auth and hosted website control-plane routes, plus compat proxy for Silk legacy flows.

Compat target

Not configured

Primary routes

/api/v1/me, /api/v1/workspaces, /api/v1/api-keys, and /api/v1/agent-tokens are owned directly here
/api/v1/sites, /api/v1/artifacts, /api/v1/releases, /api/v1/deployments, and /api/v1/domains now run on the standalone runtime
/api/v1/* and /api/xoro/* still proxy any not-yet-extracted Xoro routes, especially Silk-bound legacy flows
/api/health for service health and target visibility