Developer & CI · wired today

Split, wired into your agent workforce

Build, review and release state is where agents earn their keep. The Split connector is one of 205 executable connectors and gives agents 7 read-only tools, with the credential held in the vault and every call receipted.

Connecting Split takes one credential

You provide API key from your Split account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Where to get it: Split's own API documentation ↗ covers creating and scoping the credential.

What agents can run against Split

list_workspaces

List Split workspaces the Admin API key can see; every other read needs a workspace ID from here

list_environments

List the environments in one Split workspace (which are production, and their IDs for flag-definition reads)

list_feature_flags

List the feature flags in one Split workspace with their traffic type, tags and creation time

get_feature_flag

Get one Split feature flag by name (workspace-level metadata, not its per-environment rollout)

get_feature_flag_definition

Get the rollout of one Split feature flag in one environment: kill switch, treatments, default rule and traffic allocation

list_segments

List the segments in one Split workspace and environment with their traffic type

list_traffic_types

List the traffic types defined in one Split workspace (user, account and any custom types)

Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.

How proven is this?

This connector was blind shape-proven against the real Split API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.

Split integration FAQ

What can Quox agents do with Split?

Agents can run 7 read-only tools against Split: list workspaces, list environments, list feature flags, get feature flag, get feature flag definition and more. Every call is receipted in the evidence trail.

What does the Split integration need?

You provide API key from your Split account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Do agents see my Split credentials?

No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.

How proven is the Split connector?