GenCMS is iGears' model-agnostic AI workspace and runtime direction for building assistants, document extraction, content and internal agent solutions on an organisation's own data.

It is for developers and organisations that need custom or privately deployed AI with explicit tenant, data and permission boundaries.

Account and tenant administration, workspace records, scoped API keys and Guard scanning are available. Composer can run through a tenant's region-locked AIHK or AICA gateway after its AI key is ready.

Request managed workspace access or ask iGears to scope a 30-day MVP. Project services are fixed-price, with the scope, fee and acceptance checks stated in a quotation.

API

Scoped APIs are live; unified execution is still planned.

Workspace API keys work for tenant-scoped record reads and writes, Guard scans and Composer runs. Skill execution, Memory retrieval, Workflow runs and Agent triggers are not deployed.

Manage API keys Read API availability

Keys are created, listed and revoked from a signed-in workspace, and the secret is shown once. The available endpoints are listed below; billing, unified credits and a unified Skill, Memory or Agent execution API remain planned.

Concept illustration of a future unified GenCMS execution interface connecting models and runtime modules

Available endpoints

Use these deployed routes today.

GET	/api/v1/workspace	Read workspace counts, policy and recent activity metadata
GET · POST	/api/v1/workspace/skills	List or create Skill install records
GET · POST	/api/v1/workspace/memory	List or create Memory collection records
GET · POST	/api/v1/workspace/drafts/{kind}	List or create Agent, Workflow or App drafts
GET	/api/v1/workspace/activity	Read saved workspace activity metadata
GET · PATCH	/api/v1/workspace/settings	Read or update workspace policy
POST	/api/v1/guard/scan	Scan a public GitHub repository or supplied text
POST	/api/v1/run	Run Composer through the tenant's assigned AIHK or AICA gateway

read-workspace.sh

# Available with a key carrying workspace:read
curl https://gen-cms.com/api/v1/workspace \
  -H "Authorization: Bearer $GENCMS_API_KEY"

scan-pasted-content.sh

# Available with a key carrying guard:scan
curl https://gen-cms.com/api/v1/guard/scan \
  -H "Authorization: Bearer $GENCMS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "quick",
    "content": "name: example-skill\npermissions: []"
  }'

Execution roadmap

These endpoint shapes are proposed, not deployed.

They document product direction only and must not be used as a current integration contract.

POST	/v1/skills/{slug}/run	Execute an installed Skill
POST	/v1/memory/{collection}/query	Retrieve indexed context and citations
POST	/v1/workflows/{id}/run	Execute a Workflow draft
POST	/v1/agents/{id}/trigger	Trigger an Agent draft

No unified chat endpoint, Skill runtime, Memory query, Workflow execution, Agent trigger, run billing, streaming contract or usage-credit header is implemented by these proposed routes.

Key scopes

Give each integration only the access it needs.

workspace:read

Read tenant-scoped workspace records, settings and activity metadata.

workspace:write

Create, update or remove supported workspace records and settings.

guard:scan

Run Guard over a public GitHub repository or supplied text.

composer:run

Run chat through the AIHK or AICA gateway assigned to the active tenant.