Skip to main content
The workspace is the tenant boundary. Every authenticated operation resolves a workspace from your credential and enforces it server-side — you cannot select another tenant by sending a different workspace_id. Start with GET /api/v1/me to see the workspaces your credential can reach and the default workspace. Most requests can then omit workspace_id.

​
Wire shape

A workspace entry returned by GET /api/v1/me: The /me response also includes data.default_workspace_id and the credential’s capabilities. It never returns key material.

​
All operations on this resource

​
Where the IDs come from

Operations that require an explicit workspace_id in the body or query: POST /api/v1/operating-processes (and its transitions), POST /api/v1/handoffs (and its transitions), POST /api/v1/discovery-runs, GET /api/v1/events/stream, GET /api/v1/projections/*, GET /api/v1/episodes, and GET/POST /api/v1/decisions. Work-item and initiative operations resolve it automatically.

​
MCP equivalents

orgx_bootstrap resolves the current workspace for a session. Workspace creation and management remain signed-in app actions.