Skip to main content

Key terms

The developer documentation uses the same vocabulary as the platform and the help centre. When a term below appears in an API field name it is written in code style; in prose it is written as shown here.

Zones​

TermMeaning
Work RoomWhere people use agents and knowledge: chat, conversations, agents, apps, automations, artifacts.
StudioWhere builders create agents, prompts, skills and models.
Control RoomWhere administrators govern and operate the platform.
CatalogWhere users discover pre-built agents, skills and apps.

Roles and grants​

TermMeaning
MemberBase role. Uses the Work Room and the Catalog.
BuilderAdds Studio. Builds and publishes agents and knowledge.
AdminHolds everything in the tenant except deciding who else holds admin roles.
Super AdminManages roles and the tenant itself.
GrantOne slice of Admin handed to a role that is not Admin.

Agents and knowledge​

TermMeaning
AgentA published assistant with its own instructions, knowledge, tools and model.
Knowledge sourceA connected system or an upload whose content agents answer from; the unit Studio and the Control Room manage.
IngestionReading, chunking and indexing content from a source.
ArtifactA file an agent produced, kept in the Work Room.
AutomationA workflow run on a schedule or trigger that can pause for approval.

API​

TermMeaning
API keyA tenant-scoped credential that starts with kapi_ and is sent as a bearer token.
Public API gatewayThe single entry point for the public REST API.
ScopeA permission carried by an API key, chosen when the key is created; a route needs the scope shown on its reference page.
Endpoint groupOne of the ten areas the reference and the Developer Hub sort endpoints into.
Rate limitThe per-minute and per-day request allowance of a key, reported in the X-RateLimit-* headers.
MCPModel Context Protocol, an open standard for exposing tools and resources to AI hosts.
Katonic MCP ServerThe platform's own MCP server, at /mcp on your tenant host, which turns public API calls into tools.
Katonic CLIThe katonic-admin command for operators: air-gap bundles and platform updates, not public API calls.

Terms that changed​

Names that a reader may still hold from an earlier release, an older script or a tenant that has not been remapped. The old names are shown in code style because they are strings that may still sit in a configuration file or a realm, not words to write in prose.

You may haveWrite, and use, this now
Workroom, WorkRoomWork Room
MarketplaceCatalog
Viewer roleMember
Operator roleBuilder, plus the Operator grant
Release Manager roleBuilder, plus the Release Approver grant
Analytics Viewer, Audit Log Viewer, Agent Governance grantsAuditor grant
Guardrails Admin, Security Admin grantsSecurity grant
Infra Operator, Inference Optimizer grantsOperator grant
Model Risk Viewer grantModel Risk Approver grant
Flywheel Engineer, Tools Admin grantsThe Builder role itself; tool policy moved to Admin
pip install katonicAn older SDK from a previous generation of the product, unrelated to today's CLI. See Katonic CLI
katonic-sdk 6.xThe legacy MLOps SDK under the same package name. Today's Python SDK is 7.x: pip install "katonic-sdk>=7". See The Python SDK

A retired role name still resolves: the platform expands it to the current roles it now means, so an account carrying one keeps working until a Super Admin uses Move retired roles in the Control Room. Write the current name in anything new.

Two spellings reach the same field on the sessions routes: agentId and agent_id, chatId and chat_id. Both are accepted; the reference shows the spelling the route declares.

Describes the platform as of .

Was this page helpful?