Is Split agent-ready?

Split scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.

Does Split publish an OpenAPI spec?

No published OpenAPI specification was found when Split was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.

What is Split's Headless Index score?

Split scores 48/100 on the Headless Index thesis-fit rubric and sits in Band C in the Feature Flags & Config category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Feature Flags & Config

Split

Headless Index

48/100

denominator 80

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Split earns Band C in the Feature Flags & Config category of The Headless Index, with a thesis-fit score of 48/100. Its strongest dimension is API-first design intent (16/20); its weakest scored dimension is MCP and agent posture (0/20). No public OpenAPI specification was found when Split was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Split is partially headless and partly UI-led. The Headless Index thesis-fit score of 48/100 puts it mid-table on the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier are partly machine-consumable: the core flows are reachable through code but several adjacent surfaces still expect a human at a dashboard, and the rest of this verdict explains where Split lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Split (now Harness FF after acquisition; this entry tracks the standalone Split platform). REST API plus SDKs across web, mobile, and server-side languages. The product was experiment-focused feature flags with statistical impact analysis.^[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? REST documented at help.split.io. SDKs are well-maintained. Schema discoverability is solid.^[2] An agent can drive parts of this product, but not all of it: integrators should plan for human-in-the-loop checkpoints where the headless surface stops short. On headless operability: Splits (flags), segments, environments, attributes, and metrics are programmable. The Split CLI plus a Terraform provider give shell and IaC paths.^[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party Split MCP server. The Harness acquisition has not yet extended to MCP integration.^[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. On webhooks and events, the docs crawler did not locate a webhooks reference page or events catalog. Editorial review should confirm whether the vendor publishes events at all, and if so whether signing and replay are documented. Net assessment: integrators can build agent flows against Split, but the rough edge to plan around is MCP posture^[5]. Expect to wrap missing pieces in bespoke glue or accept human-in-the-loop checkpoints. Workable but requires scaffolding.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent16/20

scored

Split (now Harness FF after acquisition; this entry tracks the standalone Split platform). REST API plus SDKs across web, mobile, and server-side languages. The product was experiment-focused feature flags with statistical impact analysis.

signals (5)

+AI review appliedReviewer: Editorial review on 2026-05-20
−OpenAPI specNot found across 34 probe paths
·GraphQL endpointDiscovered at https://www.split.io/graphql, introspection disabled or scoped
+SDKs maintained20 (dotnet, go, java, javascript, kotlin, php, python, ruby, swift, typescript); top by stars: splitio/javascript-client (49 stars)
+npm weekly downloads73.2k across published packages; top: @splitsoftware/splitio-browserjs @ 45.3k/week

cite (1)

ai_review_browser.auth@2026-05-20

Headless operation8/20

scored

Splits (flags), segments, environments, attributes, and metrics are programmable. The Split CLI plus a Terraform provider give shell and IaC paths.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-05-20
−API operations exposedNo OpenAPI spec; operations count unknown
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

ai_review_browser.topics_found@2026-05-20

MCP & agent posture0/20

scored

No first-party Split MCP server. The Harness acquisition has not yet extended to MCP integration.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-05-20
−Official MCP serverNone found in vendor's GitHub org or the official MCP registry
−Community MCP serversNone found
+Agent-friendly SDKs8 TS/JS SDKs available; top: javascript-client (124/week downloads)

cite (3)

mcp.registry_query@2026-05-19
mcp.github_search_query@2026-05-19
github.sdks@2026-05-19

Schema observability14/20

scored

REST documented at help.split.io. SDKs are well-maintained. Schema discoverability is solid.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-05-20
−OpenAPINot discovered across 34 standard probe paths
·GraphQL introspectionGraphQL endpoint at https://www.split.io/graphql but introspection is disabled, scoped, or behind authentication

cite (1)

ai_review_browser.schema@2026-05-20

Webhooks & eventsUnknown

Unknown

Split webhooks deliver flag-change and impression events. Catalog covers feature-flag plus impact-analysis use cases.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-05-20
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

docs.pages_crawled@2026-05-19

JAIRF · 6 dimensions

JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Band rationale:C band: scores 40-75 range

04 / Embed

Show Split's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Calibration

How THI compares to external scorers

Source	Score	Measures	Last checked
Fern Agent Score	not found	Documentation completeness and SDK shape (~22 checks)	—
CLIRank Agent Friendliness	0	CLI readiness, docs quality, and overall agent affordances	—
Cloudflare Is It Agent Ready?	blocked	Cloudflare's manual agent-readiness heuristic per vendor URL	—
Jentic Scorecard	n a	JAIRF-based scorecard requiring a public OpenAPI specification	—

THI 48 vs external median 0, delta +48Methodology delta noted — see verdict

THI display 48 vs external median 0 (delta +48). Deviation > 25 points: editor should review whether THI methodology is over-strict or external scorers are over-generous for this vendor.

Peers in Feature Flags & Config

PostHog Feature FlagsC

Headless Index 50/100

StatsigC

Headless Index 43/100

HypertuneC

Headless Index 54/100

See full Feature Flags & Config ranking →

FAQ

Split and agent readiness

Is Split agent-ready?: Split scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.
Does Split publish an OpenAPI spec?: No published OpenAPI specification was found when Split was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Split's Headless Index score?: Split scores 48/100 on the Headless Index thesis-fit rubric and sits in Band C in the Feature Flags & Config category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.