Get started

Getting started

Sign in, inspect an assigned workspace and run a real Guard scan.

Availability note — these docs describe both working and planned product areas. Account authentication, administrator-managed AIHK/AICA tenant regions and keys, signed-in Composer runs and public Guard scans are connected. Skills, Memory, Agents, Workflows, Apps, billing, the public SDK/CLI and the unified API are previews unless a section explicitly says otherwise.

The deployed developer surface provides session-authenticated workspace records, a real static Guard scanner and Composer chat through a tenant’s ready region-locked AIHK or AICA key. Marketplace Skill execution is not deployed.

1. Get workspace access

An administrator creates tenants and assigns member accounts. Public signup is closed unless the operator explicitly enables it; newly signed-up members remain unassigned until an administrator places them in a tenant. Signed-in administrators use a separate admin workspace scope.

2. Choose how you want to start

Scan with Guard

Analyse pasted source or an exact public GitHub repository with the deployed rules engine.

Store workspace state

Manage Skill-install records, Memory content, drafts, settings and activity after signing in.

Manage your account

Update profile, password and active sessions from the account workspace.

Read the API reference

Use only the routes listed as currently implemented.

3. Run Guard without an account

terminal
curl https://gen-cms.com/api/v1/guard/scan \
  -H "Content-Type: application/json" \
  -d '{ "target": "https://github.com/owner/public-repository", "mode": "quick" }'

Guard returns an observed-risk report from the shipped static rules engine. Remote collection is limited to public github.com repositories; for any other source, send the relevant content directly instead of asking the server to fetch it.

4. Read an authenticated workspace

terminal
curl -c gencms.cookies https://gen-cms.com/api/v1/auth/signin \
  -H "Origin: https://gen-cms.com" \
  -H "Content-Type: application/json" \
  -d '{ "email": "[email protected]", "password": "your-password" }'

curl -b gencms.cookies https://gen-cms.com/api/v1/workspace \
  -H "Origin: https://gen-cms.com"

Create, list and revoke workspace keys with the gc_session cookie. A generated key can then authorize workspace reads/writes, Guard scans or Composer runs when it carries the matching workspace:read, workspace:write, guard:scan or composer:run scope. GenCMS SDK and CLI packages are not shipped.

Next →Core concepts