Is Kameleoon agent-ready?

Kameleoon 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 webhooks and events.

Does Kameleoon publish an OpenAPI spec?

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

What is Kameleoon's Headless Index score?

Kameleoon scores 42/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

Kameleoon

Headless Index

42/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

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

Editorial verdict

Kameleoon is partially headless and partly UI-led. The Headless Index thesis-fit score of 42/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 Kameleoon lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Kameleoon has four APIs and no API product. The Automation API at api.kameleoon.com uses OAuth 2.0 client credentials or authorization code, and the docs then cap it at twelve requests per minute per account while warning it is not built for volume. 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: On paper the Automation API performs most actions available in the web interface, and tutorials walk through creating experiments, segments and goals and pushing variation JavaScript (POST to api.kameleoon.com/experiments). In practice the twelve-calls-per-minute ceiling makes bulk or agent-driven operation impractical. There is no CLI, no Terraform provider, no config-as-code format and no self-hosted option. The dashboard remains the operating surface.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: The developer docs navigation carries an MCP entry, and the link is real (/mcp/mcp-server on developers.kameleoon.com), but the page returns 404 on fetch. Nothing else corroborates it: no Kameleoon GitHub organisation, no npm package under the @kameleoon scope, no Model Context Protocol registry record. Something may be in progress; today an agent has nothing to install.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Kameleoon publishes no outbound event catalogue, no signing scheme, no retry or replay semantics. The Data API endpoints that look event-shaped run the other direction (ingestion, not notification): POST /visit/events and POST /product/events push conversions into Kameleoon. Downstream systems learn about experiment changes by polling or through vendor integrations. For an agent that needs to react to a rollout, there is nothing to subscribe to. Net assessment: integrators can build agent flows against Kameleoon, but the rough edge to plan around is webhooks and events^[3]. 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 intent10/20

scored

Kameleoon has four APIs and no API product. The Automation API at api.kameleoon.com uses OAuth 2.0 client credentials or authorization code, and the docs then cap it at twelve requests per minute per account while warning it is not built for volume. SDKs ship as compiled packages only (@kameleoon/nodejs-sdk, @kameleoon/react-sdk); there is no public source repository to read.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 0 probe paths
·GraphQL endpointDiscovered at https://www.kameleoon.com/graphql, introspection disabled or scoped
−SDKs maintainedNone detected in vendor org

cite (1)

github.sdks@2026-08-19

Headless operation10/20

scored

On paper the Automation API performs most actions available in the web interface, and tutorials walk through creating experiments, segments and goals and pushing variation JavaScript (POST to api.kameleoon.com/experiments). In practice the twelve-calls-per-minute ceiling makes bulk or agent-driven operation impractical. There is no CLI, no Terraform provider, no config-as-code format and no self-hosted option. The dashboard remains the operating surface.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
−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)

github.sdks@2026-08-19

MCP & agent posture8/20

scored

The developer docs navigation carries an MCP entry, and the link is real (/mcp/mcp-server on developers.kameleoon.com), but the page returns 404 on fetch. Nothing else corroborates it: no Kameleoon GitHub organisation, no npm package under the @kameleoon scope, no Model Context Protocol registry record. Something may be in progress; today an agent has nothing to install.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−Official MCP serverNone found in vendor's GitHub org or the official MCP registry
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability8/20

scored

There is no spec. No OpenAPI document, no introspectable GraphQL endpoint, no schema files in a public repository. Endpoints are described in prose tutorials on developers.kameleoon.com, one at a time, in narrative form (the Data API page lists GET /visit/visitor and POST /visit/events as bullets). An agent has to read documentation pages to construct a client, which is exactly the failure mode.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 0 standard probe paths
·GraphQL introspectionGraphQL endpoint at https://www.kameleoon.com/graphql but introspection is disabled, scoped, or behind authentication

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events6/20

scored

Kameleoon publishes no outbound event catalogue, no signing scheme, no retry or replay semantics. The Data API endpoints that look event-shaped run the other direction (ingestion, not notification): POST /visit/events and POST /product/events push conversions into Kameleoon. Downstream systems learn about experiment changes by polling or through vendor integrations. For an agent that needs to react to a rollout, there is nothing to subscribe to.

signals (2)

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

cite (1)

github.sdks@2026-08-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 Kameleoon'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

Peers in Feature Flags & Config

StatsigC

Headless Index 43/100

EppoC

Headless Index 40/100

SplitC

Headless Index 48/100

See full Feature Flags & Config ranking →

FAQ

Kameleoon and agent readiness

Is Kameleoon agent-ready?: Kameleoon 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 webhooks and events.
Does Kameleoon publish an OpenAPI spec?: No published OpenAPI specification was found when Kameleoon was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Kameleoon's Headless Index score?: Kameleoon scores 42/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.