KosmoKrator

productivity

Split CLI for AI Agents

Use the Split CLI from KosmoKrator to call Split tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

7 functions 6 read 1 write Bearer token auth

Split CLI Setup

Split can be configured headlessly with `kosmokrator integrations:configure split`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure split --set access_token="$SPLIT_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor split --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

KeyEnv varTypeRequiredLabel
access_token SPLIT_ACCESS_TOKEN Secret secret yes API Token
workspace_id SPLIT_WORKSPACE_ID Text text no Workspace ID
url SPLIT_URL URL url no API Base URL

Call Split Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call split.split_list_splits '{
  "workspace_id": "example_workspace_id",
  "limit": 1,
  "offset": 1
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:split split_list_splits '{
  "workspace_id": "example_workspace_id",
  "limit": 1,
  "offset": 1
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs split --json
kosmo integrations:docs split.split_list_splits --json
kosmo integrations:schema split.split_list_splits --json
kosmo integrations:search "Split" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Split.

split.split_list_splits

Read read

List feature splits in a Split workspace. Returns split names, descriptions, traffic type, and creation date.

Parameters
workspace_id, limit, offset

Generic CLI call

kosmo integrations:call split.split_list_splits '{"workspace_id":"example_workspace_id","limit":1,"offset":1}' --json

Provider shortcut

kosmo integrations:split split_list_splits '{"workspace_id":"example_workspace_id","limit":1,"offset":1}' --json

split.split_get_split

Read read

Get detailed information about a specific Split feature split, including its definition and traffic allocation.

Parameters
split_name, workspace_id

Generic CLI call

kosmo integrations:call split.split_get_split '{"split_name":"example_split_name","workspace_id":"example_workspace_id"}' --json

Provider shortcut

kosmo integrations:split split_get_split '{"split_name":"example_split_name","workspace_id":"example_workspace_id"}' --json

split.split_create_split

Write write

Create a new feature split in a Split workspace. Specify a name, traffic type, and optional description.

Parameters
name, traffic_type_name, description, workspace_id

Generic CLI call

kosmo integrations:call split.split_create_split '{"name":"example_name","traffic_type_name":"example_traffic_type_name","description":"example_description","workspace_id":"example_workspace_id"}' --json

Provider shortcut

kosmo integrations:split split_create_split '{"name":"example_name","traffic_type_name":"example_traffic_type_name","description":"example_description","workspace_id":"example_workspace_id"}' --json

split.split_list_environments

Read read

List all environments for a Split workspace. Returns environment IDs, names, and their status.

Parameters
workspace_id

Generic CLI call

kosmo integrations:call split.split_list_environments '{"workspace_id":"example_workspace_id"}' --json

Provider shortcut

kosmo integrations:split split_list_environments '{"workspace_id":"example_workspace_id"}' --json

split.split_get_environment

Read read

Get detailed information about a specific Split environment, including its name, type, and status.

Parameters
environment_id, workspace_id

Generic CLI call

kosmo integrations:call split.split_get_environment '{"environment_id":"example_environment_id","workspace_id":"example_workspace_id"}' --json

Provider shortcut

kosmo integrations:split split_get_environment '{"environment_id":"example_environment_id","workspace_id":"example_workspace_id"}' --json

split.split_list_workspaces

Read read

List all Split workspaces. Returns workspace IDs, names, and the number of environments.

Parameters
none

Generic CLI call

kosmo integrations:call split.split_list_workspaces '{}' --json

Provider shortcut

kosmo integrations:split split_list_workspaces '{}' --json

split.split_get_current_user

Read read

Get information about the currently authenticated Split user. Useful for verifying API credentials.

Parameters
none

Generic CLI call

kosmo integrations:call split.split_get_current_user '{}' --json

Provider shortcut

kosmo integrations:split split_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

split.split_list_splits

List feature splits in a Split workspace. Returns split names, descriptions, traffic type, and creation date.

Operation
Read read
Schema command
kosmo integrations:schema split.split_list_splits --json
ParameterTypeRequiredDescription
workspace_id string no The workspace ID (defaults to the configured workspace).
limit integer no Maximum number of splits to return (default: 20, max: 100).
offset integer no Offset for pagination (default: 0).

split.split_get_split

Get detailed information about a specific Split feature split, including its definition and traffic allocation.

Operation
Read read
Schema command
kosmo integrations:schema split.split_get_split --json
ParameterTypeRequiredDescription
split_name string yes The split name (e.g., "new-checkout-flow").
workspace_id string no The workspace ID (defaults to the configured workspace).

split.split_create_split

Create a new feature split in a Split workspace. Specify a name, traffic type, and optional description.

Operation
Write write
Schema command
kosmo integrations:schema split.split_create_split --json
ParameterTypeRequiredDescription
name string yes The split name (e.g., "new-checkout-flow").
traffic_type_name string yes The traffic type name (e.g., "user", "account").
description string no Optional description for the split.
workspace_id string no The workspace ID (defaults to the configured workspace).

split.split_list_environments

List all environments for a Split workspace. Returns environment IDs, names, and their status.

Operation
Read read
Schema command
kosmo integrations:schema split.split_list_environments --json
ParameterTypeRequiredDescription
workspace_id string no The workspace ID (defaults to the configured workspace).

split.split_get_environment

Get detailed information about a specific Split environment, including its name, type, and status.

Operation
Read read
Schema command
kosmo integrations:schema split.split_get_environment --json
ParameterTypeRequiredDescription
environment_id string yes The environment ID.
workspace_id string no The workspace ID (defaults to the configured workspace).

split.split_list_workspaces

List all Split workspaces. Returns workspace IDs, names, and the number of environments.

Operation
Read read
Schema command
kosmo integrations:schema split.split_list_workspaces --json
ParameterTypeRequiredDescription
No parameters.

split.split_get_current_user

Get information about the currently authenticated Split user. Useful for verifying API credentials.

Operation
Read read
Schema command
kosmo integrations:schema split.split_get_current_user --json
ParameterTypeRequiredDescription
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.