$HEADLESS SYSTEMS
03 / Scorecard / Feature Flags & Config

Featurevisor

D
Headless Index
35/100
JAIRF
N/A
Verified
MAY 21, 2026
Methodology v1 · JAIRF v1.0.0

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

Editorial verdict
Featurevisor remains a dashboard-first product with a limited programmatic surface. The Headless Index thesis-fit score of 35/100 sits in the lower band of 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 ship enough API to be useful but not enough to be operated end to end by agents without a human in the loop, and the rest of this verdict explains where Featurevisor lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Featurevisor is open-source feature flags managed entirely in Git via YAML or JSON. CLI-driven authoring with code-review-based flag changes. SDKs in JavaScript, Node, and Python.[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? YAML and JSON flag definitions are themselves machine-readable. Schema discoverability is reference-class for GitOps-driven flag management.[2] An agent cannot drive this product end to end today: the headless surface covers basic CRUD but tapers out before reaching the workflows that matter most. On headless operability: Flags, segments, attributes, and tests are defined in Git. The featurevisor CLI is the canonical authoring tool. There is no dashboard; the product positioning is GitOps-native feature flags.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party Featurevisor MCP server. The GitOps positioning means flag changes go through the SCM rather than through an agent-callable API.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Webhooks are emitted from the SCM (GitHub Actions, etc.) rather than from Featurevisor directly. The platform's event model is Git-centric. Net assessment: Featurevisor is not a strong target for agent-driven workflows today. The weakest link is MCP posture[5], and the broader surface gives agents too little to operate against. Pick it only when the rest of your stack already mandates it. Use only when locked in.
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 intent5/20
scored

Featurevisor is open-source feature flags managed entirely in Git via YAML or JSON. CLI-driven authoring with code-review-based flag changes. SDKs in JavaScript, Node, and Python.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • OpenAPI specNot found across 17 probe paths
  • ·GraphQL endpointDiscovered at https://featurevisor.com/graphql, introspection disabled or scoped
  • +SDKs maintained9 (go, java, kotlin, php, ruby, swift); top by stars: featurevisor/featurevisor-swift (3 stars)
cite (3)
  • openapi.probes_tried@2026-05-19
  • graphql.url@2026-05-19
  • github.sdks@2026-05-19
Headless operation8/20
scored

Flags, segments, attributes, and tests are defined in Git. The featurevisor CLI is the canonical authoring tool. There is no dashboard; the product positioning is GitOps-native feature flags.

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 posture4/20
scored

No first-party Featurevisor MCP server. The GitOps positioning means flag changes go through the SCM rather than through an agent-callable API.

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 SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)
cite (1)
  • ai_review_browser.pages_fetched@2026-05-20
Schema observability14/20
scored

YAML and JSON flag definitions are themselves machine-readable. Schema discoverability is reference-class for GitOps-driven flag management.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • OpenAPINot discovered across 17 standard probe paths
  • ·GraphQL introspectionGraphQL endpoint at https://featurevisor.com/graphql but introspection is disabled, scoped, or behind authentication
cite (1)
  • ai_review_browser.schema@2026-05-20
Webhooks & events4/20
scored

Webhooks are emitted from the SCM (GitHub Actions, etc.) rather than from Featurevisor directly. The platform's event model is Git-centric.

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)
  • ai_review_browser.pages_fetched@2026-05-20
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

Powered by JAIRF v1.0.0 by Jentic

Band rationale:D band triggered: HeadlessIndex=35

04 / Embed

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