Workspace
A workspace is the top-level container in Skene Cloud. It holds your features, triggers, logs, integrations, and team members. Each workspace connects to one Supabase project.
Members and roles
Manage members from Settings -> Members.
| Role | Permissions |
|---|---|
| Owner | Full access. Manage billing, members, integrations, and features. |
| Member | Create and manage features, view logs, use the Agent. Cannot manage billing or members. |
Inviting members
Click Invite on the Members page, enter an email address, and send the invitation. The invited user receives an email with a link to join the workspace.
Removing members
Click the remove button next to a member's name. This revokes their access immediately. Owners cannot be removed. Transfer ownership first.
API keys
API keys authenticate external integrations and the skene CLI. Manage them from the API Keys page.
Creating a key
Click Create API Key. The key is shown once. Copy it immediately. Keys are prefixed with sk_ws_ and scoped to the workspace.
Using API keys
API keys authenticate requests to the workspace HTTP API:
# CLI authentication
uvx skene login # Interactive login stores the key
uvx skene push # Uses stored key
# Direct API usage
curl -X POST https://www.skene.ai/api/v1/push \
-H "Authorization: Bearer sk_ws_..." \
-H "Content-Type: application/json" \
-d '{"engine_yaml": "..."}'
Keys are accepted in three header formats:
Authorization: Bearer sk_ws_...X-Skene-Token: sk_ws_...X-API-Key: sk_ws_...
Allowed origins
Configure allowed origins for CORS when embedding Skene APIs in client-side applications. Edit the origins list from the API Keys page.
Revoking a key
Click Delete next to a key. This invalidates the key immediately. Any integrations using it will stop working.
Integrations
The Integrations page manages external service connections:
| Integration | Purpose | Docs |
|---|---|---|
| Supabase | Database connection for schema analysis and trigger deployment | Supabase Integration |
| GitHub | Repository linking for engine manifest sync | Configured on the Agent Engine page (/workspace/.../skene-engine) |
Workspace API
The workspace exposes three API endpoints authenticated with API keys:
| Endpoint | Method | Purpose |
|---|---|---|
/api/v1/push | POST | Push CLI artifacts (engine YAML, manifests, registry) |
/api/v1/chat/completions | POST | OpenAI-compatible LLM proxy (streaming and non-streaming) |
/api/v1/cloud/ingest/db-trigger | POST | Receive events from deployed Supabase triggers |
The Push and Chat Completions endpoints use API key auth. The ingest endpoint uses a per-workspace proxy secret (managed automatically during Supabase setup).
Next steps
- Supabase Integration: Connect your database
- Features & Deploy: Start creating growth features
- skene CLI: Login: Authenticate the CLI with your API key
