$HEADLESS SYSTEMS
03 / Scorecard / Feature Flags & Config

FeatBit

B
Headless Index
79/100
JAIRF
N/A
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

FeatBit earns Band B in the Feature Flags & Config category of The Headless Index, with a thesis-fit score of 79/100. Its strongest dimension is schema observability (17/20); its weakest scored dimension is API-first design intent (15/20). No public OpenAPI specification was found when FeatBit was scored, which limits how far an agent can go without human integration work.

Editorial verdict
FeatBit is solidly built for programmatic consumption. The Headless Index thesis-fit score of 79/100 lands it in the upper-middle 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 most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where FeatBit lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. The REST API is documented as a full alternative to the UI, and FeatBit says so plainly: anything available in the flags list can be done over HTTP, authenticated by a personal or service access token in the Authorization header. An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: Self-hosting is the default posture, not a tier: docker compose, Helm, and a Terraform module for AWS get you a running stack, and an official provider covers the resources afterwards (registry.terraform.io/providers/featbit/featbit). The relay proxy and FeatBit Agent handle edge evaluation. Docs even include coding-agent workflows for creating and cleaning up flags. Experiment analysis still lives in the dashboard.[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: An MCP server does exist in-org (github.com/featbit/featbit-mcp), and the documentation carries pages on creating and retiring flags with coding agents, which is more intent than most self-hosted flag projects show. It is also thin: one star, last touched in June 2026, no MCP registry entry, and no tool catalogue in the docs to tell an agent what it can call.[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Eighteen named events, and they are granular in the way agents need: feature_flag.toggled, feature_flag.targeting_rules_changed, feature_flag.off_variation_changed, segment.rules_changed, plus create, archive, restore and delete for both objects. Deliveries carry a secret-derived signature and a delivery id header (X-FeatBit-Delivery), time out at 10 seconds, and retry three times at 2s intervals. Payloads are Handlebars templates. No replay endpoint. Net assessment: FeatBit can be operated by agents for the majority of practical workflows. The closest thing to a gap is API-first posture[3], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.
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 intent15/20
scored

The REST API is documented as a full alternative to the UI, and FeatBit says so plainly: anything available in the flags list can be done over HTTP, authenticated by a personal or service access token in the Authorization header. SDK coverage is broad for a project this small (@featbit/node-server-sdk, @featbit/react-client-sdk, fb-python-sdk, Go, .NET, Java, Rust), with OpenFeature providers alongside.

signals (6)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • −OpenAPI specNot found across 34 probe paths
  • −GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
  • +SDKs maintained17 (dotnet, go, java, javascript, kotlin, python, ruby, rust, typescript); top by stars: featbit/featbit-dotnet-sdk (19 stars)
  • +SDK recency10 of 17 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-17)
  • +npm weekly downloads15.9k across published packages; top: @featbit/node-server-sdk @ 5.8k/week
cite (1)
  • github.sdks@2026-08-19
Headless operation16/20
scored

Self-hosting is the default posture, not a tier: docker compose, Helm, and a Terraform module for AWS get you a running stack, and an official provider covers the resources afterwards (registry.terraform.io/providers/featbit/featbit). The relay proxy and FeatBit Agent handle edge evaluation. Docs even include coding-agent workflows for creating and cleaning up flags. Experiment analysis still lives in the dashboard.

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)
  • ai_review_browser.topics_found@2026-08-19
MCP & agent posture15/20
scored

An MCP server does exist in-org (github.com/featbit/featbit-mcp), and the documentation carries pages on creating and retiring flags with coding agents, which is more intent than most self-hosted flag projects show. It is also thin: one star, last touched in June 2026, no MCP registry entry, and no tool catalogue in the docs to tell an agent what it can call.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • +Official MCP serverhttps://github.com/featbit/featbit-mcp (1 stars, last commit 63 days ago)
  • −Community MCP serversNone found
  • +Agent-friendly SDKs6 TS/JS SDKs available; top: featbit-js-client-sdk (228/week downloads)
cite (1)
  • ai_review_browser.mcp@2026-08-19
Schema observability17/20
scored

The crawler missed this, so state it plainly: FeatBit serves a live OpenAPI 3.0.4 document (app-api.featbit.co/swagger/v1/swagger.json), roughly 630KB, titled FeatBit Backend Api, rendered through Redoc at /docs/index.html. Self-hosted instances expose the same path, so an agent points at its own server and generates a client. That is the right pattern for a self-hosted product.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • −OpenAPINot discovered across 34 standard probe paths
  • −GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)
cite (1)
  • ai_review_browser.pages_fetched@2026-08-19
Webhooks & events16/20
scored

Eighteen named events, and they are granular in the way agents need: feature_flag.toggled, feature_flag.targeting_rules_changed, feature_flag.off_variation_changed, segment.rules_changed, plus create, archive, restore and delete for both objects. Deliveries carry a secret-derived signature and a delivery id header (X-FeatBit-Delivery), time out at 10 seconds, and retry three times at 2s intervals. Payloads are Handlebars templates. No replay endpoint.

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
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:A band: JAIRF=N/A HeadlessIndex=79; JAIRF N/A ceiling applied: max band B when OpenAPI not available

04 / Embed

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

FeatBit mini badge preview
Get embed code
Peers in Feature Flags & Config
FliptC
Headless Index 82/100
SchematicB
Headless Index 84/100
LaunchDarklyB
Headless Index 84/100
See full Feature Flags & Config ranking →
FAQ

FeatBit and agent readiness

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