Skip to content
KaziAI.
Plan your rollout
AI STUDIO & THE CAPABILITY ECOSYSTEM

Build around your business.
Make useful work reusable.

Studio turns business-specific operating ideas into definitions for agents, skills, workflows, prompts, approval rules, dashboards, and connectors. Packages and the skills marketplace provide a path to reuse those capabilities.

Explore what you can define
FROM IDEA TO CAPABILITY
  1. 1
    DefineDescribe the business job
  2. 2
    ConnectSelect tools and source context
  3. 3
    ControlSet permissions and review rules
  4. 4
    EvaluateTest the intended result
  5. 5
    ReusePackage the definition

An extensible operating system.

THE BUILDING BLOCKS

The business has its own way of working.
The platform should make room for it.

Agents

Define a role, instructions, expertise, model configuration, and permitted tools for a business-specific specialist.

Skills

Describe a repeatable capability with inputs, steps, and expected outputs that can be evaluated and reused.

Workflows

Connect manual, scheduled, or event triggers to an ordered sequence of agent, tool, condition, and other supported steps.

Prompts

Version instructions and reusable prompt templates with the variables the business task needs.

Approval rules

Define conditions, reviewer roles, and decision boundaries for consequential operations.

Dashboards

Assemble supported metrics, charts, tables, agent status, and insight widgets around business attention.

Connectors

Define the external API, authentication requirements, actions, and schemas needed to connect a business service.

Packages & skills marketplace

Export and import definitions; publish, review, install, and update skill listings through the marketplace services.

A CONCRETE STARTING POINT

A repeatable review.
A definition your team can inspect.

This simplified workflow definition illustrates the Studio structure for a manual invoice review. It names a registered invoice tool and the finance agent, then leaves the business to define the scope, arguments, review rules, and acceptance criteria.

Creating a definition does not prove that it is deployable. Templates may reference tools that are not enabled. Validate the tool registry, step configuration, permissions, reviewer behavior, and source-system result before activation.

Illustrative Studio workflow definition
{
  "name": "Receivables review",
  "trigger": { "type": "manual" },
  "steps": [
    {
      "type": "tool",
      "name": "Read invoice records",
      "config": { "tool": "list_invoices" }
    },
    {
      "type": "agent",
      "name": "Prepare finance review",
      "agent_type": "finance"
    }
  ],
  "variables": ["review_period", "reviewer"]
}
FROM A SINGLE DEFINITION TO AN ECOSYSTEM

Build once.
Review, adapt, and reuse.

The ecosystem direction is a platform that businesses and builders can extend without losing the operating context and control boundaries.

Package the capability

Export and import supported definitions so a team can inspect the instructions, tools, triggers, and assumptions before reuse in another workspace.

Make skills discoverable

The marketplace services support skill publication, listing approval, category browsing, installation, updates, and reviews. This is an extensibility mechanism; it is not a claim of an established third-party marketplace or available commercial inventory.

Connect through explicit interfaces

API, webhooks, and MCP give developers integration boundaries. Authentication, company scope, schemas, versioning, and tool authority remain part of the contract.

Explore the developer guide
PUT THE VISION TO WORK

Begin with a workflow.
Build toward a system.

Choose a real business problem. Connect its context, define the decision owners, and evaluate what useful intelligence looks like for your team.

Plan an implementation