Workspaces
A workspace API key is scoped to one workspace. Use
GET /v1/workspace for metadata plus embedded usage, or GET /v1/workspace/usage for usage only. Grant balances and billing overrides are applied server-side — responses only include used, limit, and remaining per service. Create keys in the dashboard (Workspace → Workspace keys).The Workspace object
- workspaceIdstring
- Stable workspace identifier (wsp_…).
- namestring
- Display name.
- descriptionstring
- Optional description (may be an empty string).
- planstring
- Billing plan: free or enterprise.
- usageobject
- Monthly usage per billable service (see Usage object).
Usage object
- planstring
- Billing plan for this workspace.
- resetsAtstring
- UTC ISO instant when monthly allowances reset.
- servicesarray
- One entry per billable service.
- services[].servicestring
- transcription, indexer, ai_search, clip_generation, thumbnail, metadata, or summarization.
- services[].usednumber
- Credits consumed this billing period.
- services[].limitnumber | null
- Monthly cap. null = unlimited (enterprise).
- services[].remainingnumber | null
- Credits still available (includes any bonus capacity; not itemized). null when unlimited.
Retrieve workspace
GET
/v1/workspaceReturns workspace metadata and the embedded
usage object for quota checks before jobs or catalog searches.Requires permission
workspace:read
Authenticate with
Authorization: Bearer sk_wsp_…. No X-Workspace-Id header. Project API keys cannot call this route.Retrieve workspace usage
GET
/v1/workspace/usageReturns only the
usage object — same shape as the usage field on GET /v1/workspace. Use when you do not need workspace name or description.Requires permission
workspace:read