$HEADLESS SYSTEMS
03 / Scorecard / Feature Flags & Config

Flipt

C
Headless Index
82/100
JAIRF
58.8/100
Foundational
Verified
AUG 20, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Flipt earns Band C in the Feature Flags & Config category of The Headless Index, with a thesis-fit score of 82/100 and a JAIRF rating of 58.8/100 (Foundational). Its strongest dimension is headless operation (18/20); its weakest scored dimension is webhooks and events (13/20). Flipt publishes a machine-readable OpenAPI specification, which is what lets an agent discover and operate it without human glue code.

Editorial verdict
Flipt is partially headless and partly UI-led. The Headless Index thesis-fit score of 82/100 puts it mid-table on the index, and JAIRF v1.0.0 puts it at 58.8/100 (Level 1, Foundational). 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 Flipt lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Flipt is protobuf-first and everything else follows: the gRPC service definitions generate both the gRPC API and the REST gateway, giving 51 operations across namespaces, flags, segments, rules and evaluation. Client-side evaluation SDKs share a Rust core compiled to WASM and FFI (flipt-io/flipt-client-sdks covers Go, Python, Java, Ruby, Node, Swift, Dart). Package adoption is small, but the surface is coherent. 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: You can run the whole product yourself and drive it from a terminal. The binary is the CLI (flipt import, export, validate, evaluate, bundle push and pull), v2 stores flag state in a git repository with signed commits and branch environments, and helm-charts covers Kubernetes. The one real gap: the Terraform provider is community-maintained (Lerentis/terraform-provider-flipt), not shipped by Flipt.[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Few vendors this size treat agents as a first-class consumer. Flipt ships flipt-io/mcp-server-flipt, documents it as a product feature (docs.flipt.io/v2/tooling/model-context-protocol), and serves an llms.txt index for doc crawlers. The design point matters: an agent can create a branch environment, change flags there, and propose the result back through source control rather than mutating production directly.[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Events arrive as an audit sink, not a subscription product. Payloads carry a type and action pair (flag/updated, with actor metadata and the flag body), signed as HMAC-SHA256 over the request body in X-Flipt-Webhook-Signature, retried with exponential backoff to a 15s max_backoff_duration, and shapeable through Go templates. There is no subscription API, no published catalogue and no replay. Net assessment: integrators can build agent flows against Flipt, 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 intent16/20
scored

Flipt is protobuf-first and everything else follows: the gRPC service definitions generate both the gRPC API and the REST gateway, giving 51 operations across namespaces, flags, segments, rules and evaluation. Client-side evaluation SDKs share a Rust core compiled to WASM and FFI (flipt-io/flipt-client-sdks covers Go, Python, Java, Ruby, Node, Swift, Dart). Package adoption is small, but the surface is coherent.

signals (6)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • +OpenAPI specPublished, 51 operations
  • GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
  • +SDKs maintained8 (go, java, javascript, php, rust, swift, typescript); top by stars: flipt-io/flipt-client-sdks (28 stars)
  • +SDK recency1 of 8 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-17)
  • ·npm weekly downloads10 across published packages; top: @flipt-io/vercel-adapter @ 10/week
cite (1)
  • ai_review_browser.auth@2026-08-19
Headless operation18/20
scored

You can run the whole product yourself and drive it from a terminal. The binary is the CLI (flipt import, export, validate, evaluate, bundle push and pull), v2 stores flag state in a git repository with signed commits and branch environments, and helm-charts covers Kubernetes. The one real gap: the Terraform provider is community-maintained (Lerentis/terraform-provider-flipt), not shipped by Flipt.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • ·API operations exposed51 operations in OpenAPI spec
  • ·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-08-19
MCP & agent posture18/20
scored

Few vendors this size treat agents as a first-class consumer. Flipt ships flipt-io/mcp-server-flipt, documents it as a product feature (docs.flipt.io/v2/tooling/model-context-protocol), and serves an llms.txt index for doc crawlers. The design point matters: an agent can create a branch environment, change flags there, and propose the result back through source control rather than mutating production directly.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • +Official MCP serverhttps://github.com/flipt-io/mcp-server-flipt (5 stars, last commit 27 days ago)
  • Community MCP serversNone found
  • +Agent-friendly SDKs2 TS/JS SDKs available; top: flipt-io/js-sdk-contrib
cite (1)
  • ai_review_browser.mcp@2026-08-19
Schema observability17/20
scored

The spec is in the repository and fetchable raw: OpenAPI 3.0.3, version 1.47.0, 51 operationIds, generated from the protobuf definitions by protoc-gen-openapi (raw.githubusercontent.com/flipt-io/flipt/main/openapi.yaml). Generation from proto means it never drifts from the server. Two caveats: the declared server is http://localhost:8080, and the document tracks v1 while v2 introduces environments the file does not describe.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • +OpenAPIPublished at https://raw.githubusercontent.com/flipt-io/flipt/main/openapi.yaml (OpenAPI 3.0.3, 51 operations)
  • GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)
cite (1)
  • ai_review_browser.schema@2026-08-19
Webhooks & events13/20
scored

Events arrive as an audit sink, not a subscription product. Payloads carry a type and action pair (flag/updated, with actor metadata and the flag body), signed as HMAC-SHA256 over the request body in X-Flipt-Webhook-Signature, retried with exponential backoff to a 15s max_backoff_duration, and shapeable through Go templates. There is no subscription API, no published catalogue and no replay.

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)
  • ai_review_browser.pages_fetched@2026-08-19
JAIRF · 6 dimensions
FCFoundational Compliance
85/100

Structural validity, standards conformance, and parsability of the OpenAPI specification.

DXJDeveloper Experience & Tooling Compatibility
16.5/100

Documentation clarity, example coverage, response completeness, and ingestion health.

ARAXAI-Readiness & Agent Experience
19.1/100

Semantic clarity, intent expression, datatype specificity, and error standardization.

AUAgent Usability
100/100

Operational composability, complexity comfort, navigation affordances, and safety patterns.

SECSecurity
60/100

Authentication strength, transport security, secret hygiene, and OWASP risk posture.

AIDAI Discoverability
65/100

Descriptive richness, intent phrasing, workflow context, and registry signals.

Band rationale:C band: scores 40-75 range

04 / Embed

Show Flipt'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.

Calibration

How THI compares to external scorers

SourceScoreMeasuresLast checked
Fern Agent Scorenot foundDocumentation completeness and SDK shape (~22 checks)
CLIRank Agent Friendlinessnot foundCLI readiness, docs quality, and overall agent affordances
Cloudflare Is It Agent Ready?blockedCloudflare's manual agent-readiness heuristic per vendor URL
Jentic ScorecardJAIRF-based scorecard requiring a public OpenAPI specification
THI 82 vs external median 0

No external scores available to calibrate against.

FAQ

Flipt and agent readiness

Is Flipt agent-ready?
Flipt scores Band C on The Headless Index and rates Foundational on JAIRF (58.8/100). Its strongest area for agent use is headless operation; its weakest is webhooks and events.
Does Flipt publish an OpenAPI spec?
Yes. Flipt publishes an OpenAPI specification, scored under JAIRF v1.0.0. A published spec is what makes an API discoverable and callable by agents rather than only by developers reading docs.
What is Flipt's Headless Index score?
Flipt scores 82/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.