Can I use Helicone as a CLI?

Yes. KosmoKrator exposes a Helicone CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Helicone through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Helicone tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Helicone credentials stored?

Helicone credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Helicone MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

analytics

Helicone CLI for AI Agents

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

Helicone CLI Setup

Helicone can be configured headlessly with `kosmokrator integrations:configure helicone`.

Install, configure, and verify

# 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 helicone --set api_key="$HELICONE_API_KEY" --enable --read allow --write ask --json
kosmokrator integrations:doctor helicone --json
kosmokrator integrations:status --json

Credentials

Authentication type: API key api_key. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`api_key`	`HELICONE_API_KEY`	Secret `secret`	yes	API Key
`api_url`	`HELICONE_API_URL`	URL `url`	no	Observability API URL
`gateway_url`	`HELICONE_GATEWAY_URL`	URL `url`	no	AI Gateway URL

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call helicone.helicone_query_requests '{}' --json

Provider shortcut

kosmo integrations:helicone helicone_query_requests '{}' --json

Discovery

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

Discovery commands

kosmo integrations:docs helicone --json
kosmo integrations:docs helicone.helicone_query_requests --json
kosmo integrations:schema helicone.helicone_query_requests --json
kosmo integrations:search "Helicone" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`helicone.helicone_query_requests`

Query Helicone request analytics with the ClickHouse endpoint.

Read read

Parameters: none

Generic call

kosmo integrations:call helicone.helicone_query_requests '{}' --json

Shortcut

kosmo integrations:helicone helicone_query_requests '{}' --json

`helicone.helicone_query_requests_by_ids`

Fetch request rows by explicit Helicone request IDs.

Read read

Parameters: none

Generic call

kosmo integrations:call helicone.helicone_query_requests_by_ids '{}' --json

Shortcut

kosmo integrations:helicone helicone_query_requests_by_ids '{}' --json

`helicone.helicone_get_request`

Retrieve a single Helicone request by ID.

Read read

Parameters: none

Generic call

kosmo integrations:call helicone.helicone_get_request '{}' --json

Shortcut

kosmo integrations:helicone helicone_get_request '{}' --json

`helicone.helicone_submit_feedback`

Submit positive or negative user feedback for a request.

Write write

Parameters: none

Generic call

kosmo integrations:call helicone.helicone_submit_feedback '{}' --json

Shortcut

kosmo integrations:helicone helicone_submit_feedback '{}' --json

`helicone.helicone_query_user_metrics`

Query Helicone user metrics.

Read read

Parameters: none

Generic call

kosmo integrations:call helicone.helicone_query_user_metrics '{}' --json

Shortcut

kosmo integrations:helicone helicone_query_user_metrics '{}' --json

`helicone.helicone_query_user_metrics_overview`

Query Helicone user metrics overview.

Read read

Parameters: none

Generic call

kosmo integrations:call helicone.helicone_query_user_metrics_overview '{}' --json

Shortcut

kosmo integrations:helicone helicone_query_user_metrics_overview '{}' --json

`helicone.helicone_list_gateway_models`

List AI Gateway models.

Read read

Parameters: none

Generic call

kosmo integrations:call helicone.helicone_list_gateway_models '{}' --json

Shortcut

kosmo integrations:helicone helicone_list_gateway_models '{}' --json

`helicone.helicone_gateway_chat_completions`

Create an OpenAI-compatible AI Gateway chat completion.

Write write

Parameters: none

Generic call

kosmo integrations:call helicone.helicone_gateway_chat_completions '{}' --json

Shortcut

kosmo integrations:helicone helicone_gateway_chat_completions '{}' --json

`helicone.helicone_gateway_responses`

Create an OpenAI-compatible AI Gateway Responses API response.

Write write

Parameters: none

Generic call

kosmo integrations:call helicone.helicone_gateway_responses '{}' --json

Shortcut

kosmo integrations:helicone helicone_gateway_responses '{}' --json

Function Schemas

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

helicone.helicone_query_requests 0 parameters

Schema command

kosmo integrations:schema helicone.helicone_query_requests --json

Parameter	Type	Required	Description
No parameters.

helicone.helicone_query_requests_by_ids 0 parameters

Schema command

kosmo integrations:schema helicone.helicone_query_requests_by_ids --json

Parameter	Type	Required	Description
No parameters.

helicone.helicone_get_request 0 parameters

Schema command

kosmo integrations:schema helicone.helicone_get_request --json

Parameter	Type	Required	Description
No parameters.

helicone.helicone_submit_feedback 0 parameters

Schema command

kosmo integrations:schema helicone.helicone_submit_feedback --json

Parameter	Type	Required	Description
No parameters.

helicone.helicone_query_user_metrics 0 parameters

Schema command

kosmo integrations:schema helicone.helicone_query_user_metrics --json

Parameter	Type	Required	Description
No parameters.

helicone.helicone_query_user_metrics_overview 0 parameters

Schema command

kosmo integrations:schema helicone.helicone_query_user_metrics_overview --json

Parameter	Type	Required	Description
No parameters.

helicone.helicone_list_gateway_models 0 parameters

Schema command

kosmo integrations:schema helicone.helicone_list_gateway_models --json

Parameter	Type	Required	Description
No parameters.

helicone.helicone_gateway_chat_completions 0 parameters

Schema command

kosmo integrations:schema helicone.helicone_gateway_chat_completions --json

Parameter	Type	Required	Description
No parameters.

helicone.helicone_gateway_responses 0 parameters

Schema command

kosmo integrations:schema helicone.helicone_gateway_responses --json

Parameter	Type	Required	Description
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.