$HEADLESS SYSTEMS
03 / Scorecard / Commerce

fabric

C
Headless Index
54/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
fabric is partially headless and partly UI-led. The Headless Index thesis-fit score of 54/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 fabric lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. fabric is composable commerce with separate APIs for PIM, OMS, CDP, and the storefront. SDKs in JavaScript. The product is a collection of composable services, each with its own API surface, intended to be assembled into a custom commerce stack.[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 developer.fabric.inc per module. A single canonical OpenAPI URL is not prominently exposed. Schema discoverability varies by module.[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: Each fabric module (Product, Offers, Orders, Cart, Subscriptions, Customer) is API-driven. Configuration sits in the Copilot dashboard. The composable model means integrators select which modules to consume.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party fabric MCP server. The product is enterprise composable; agent integration is community-led.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Webhook subscriptions per module deliver lifecycle events with signing. Catalog reflects the multi-module surface. Net assessment: integrators can build agent flows against fabric, 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 intent14/20
scored

fabric is composable commerce with separate APIs for PIM, OMS, CDP, and the storefront. SDKs in JavaScript. The product is a collection of composable services, each with its own API surface, intended to be assembled into a custom commerce stack.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • OpenAPI specNot found across 34 probe paths
  • GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
  • SDKs maintainedNone detected in vendor org
cite (1)
  • github.sdks@2026-05-19
Headless operation12/20
scored

Each fabric module (Product, Offers, Orders, Cart, Subscriptions, Customer) is API-driven. Configuration sits in the Copilot dashboard. The composable model means integrators select which modules to consume.

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)
  • github.sdks@2026-05-19
MCP & agent posture4/20
scored

No first-party fabric MCP server. The product is enterprise composable; agent integration is community-led.

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)
  • github.sdks@2026-05-19
Schema observability12/20
scored

REST documented at developer.fabric.inc per module. A single canonical OpenAPI URL is not prominently exposed. Schema discoverability varies by module.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • 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)
  • github.sdks@2026-05-19
Webhooks & events12/20
scored

Webhook subscriptions per module deliver lifecycle events with signing. Catalog reflects the multi-module surface.

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)
  • github.sdks@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

Powered by JAIRF v1.0.0 by Jentic

Band rationale:C band: scores 40-75 range

04 / Embed

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