Workspaces

Workspaces organize API keys, combos, files and activity. Provider keys are shared across the workspaces in your personal or organization account. Playgrounds use the account selected in the header for provider keys, balance, files and chat history. Workspace spending caps and rules apply to workspace requests, not playgrounds. Account limits still apply. Personal and organization accounts remain separate. Account Logs includes playground and workspace requests, with filters, request details and CSV export. Workspace Logs only shows that workspace’s requests. Request content is available when content logging is enabled and the content has not expired.

Select a workspace

For workspace requests, signed-in users use X-Workspace-ID; omitting it selects the default. Account-scoped session requests use X-Account-ID with personal or an organization ID. Playgrounds set this for the selected account. Do not send both headers. API keys always use their own workspace and cannot use X-Account-ID. A conflicting workspace header returns 403 workspace_access_denied. Foreign workspaces return 404 workspace_not_found; malformed IDs return 400 invalid_workspace.

Manage workspaces

Manage workspaces with GET /api/workspaces, POST /api/workspaces with { "name": "Production" }, and PATCH /api/workspaces/:id with name or isArchived. These require an owner session. Archiving preserves resources and history while blocking new requests with 403 workspace_archived. Restore it to resume. The default cannot be archived.

Workspace spending limits

Set a spending cap with GET or PUT /api/workspaces/:id/budget, using the same micro-USD and reset format as account/key limits. All applicable caps must pass. Resetting a cap does not add credits. Billing and Transactions stay account-wide; RelayOn capacity and public model statistics stay shared. Combo slugs remain unique within an account.