# Fix list: Fabric From Anchor Terminal's listing at https://www.anchorterminal.com/tools/fabric, the October 2026 research run, assessed 14 October 2026. Grade E, 43.7 out of 100. This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public. For a coding agent working on Fabric: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published. ## 1. Reliability, 23 out of 100, up to 15.4 more on the total Why it scored 23: No status page was found. status.fabric.inc does not resolve and neither the site nor the docs link one (0 of 20). With no readable incident history, the line takes the 5-point default (5 of 30). No rate-limit figures were found in the docs or the 69 OpenAPI files (0 of 15). Some specs list 429 responses, but no Retry-After header, backoff guidance or idempotency keys were found for writes (3 of 15). The SLA, last updated 1 January 2026, commits to 99.9 per cent monthly availability with credits from 5 to 40 per cent (10 of 10). The v3 APIs are in production use, but the docs home page labels them legacy and Product Agent is beta, so half marks (5 of 10). Total 23. The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability): Hosted APIs, MCP servers, models and platforms. - 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own). - 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so. - 15, rate limits documented with numbers. - 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved. - 10, an SLA published for any paid tier. - 10, the surface agents use is generally available, not beta or preview. Local packages, SDKs, frameworks and stdio MCP servers. - 20, installs from an official package with supported runtimes stated. - 25, a public CI and test suite, passing on the default branch. - 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered). - 15, semver discipline and breaking changes called out in a changelog. - 15, version 1.0 or later, or declared stable. Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors. ## 2. Payments & pricing, 0 out of 100, up to 12.5 more on the total Why it scored 0: No x402, MPP or L402 on any endpoint (0 of 40). No public prices. fabric.inc/pricing returns 404 and the sites link to a demo request (0 of 20). The docs say to reach out for a trial account, so no free tier or trial is available without sales contact (0 of 20). A person signs an order form and an admin creates the app credentials in Copilot (0 of 20). Total 0. The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments): The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/). - 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which. - 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login. - 20, a free tier or trial that doesn't need a card. - 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API). Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied. Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol. ## 3. Maintenance & community, 15 out of 100, up to 7.4 more on the total Why it scored 15: No dated API release since the July 2025 release notes. The Product Agent OpenAPI file returned a Last-Modified header of 9 June 2026, 127 days before this check, which is the newest dated change found (10 of 30). No dated release notes or changelog entries in the last 90 days (0 of 20). Support runs through a ticket portal at support.fabric.inc, which was not tested, and the public changelog has stopped (5 of 15). No official SDKs and no MCP server for the commerce APIs. The docs MCP server only searches documentation (0 of 15). No public repository, package or CI to inspect (0 of 10). Total 15. The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance): - 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older. - 20, at least three releases or dated changelog entries in the last 90 days. - 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15. - 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models). - 10, package health, current dependencies and CI. Models are read for deprecation notice periods and model churn rather than release counts. ## 4. Agent ergonomics, 57 out of 100, up to 7 more on the total Why it scored 57: Responses are sized with offset and limit, with no field selection found (15 of 25). Order search takes filters for type, status and date range in the body, with offset and limit paging (18 of 20). Orders and Inventory errors carry a type, a stable errorCode, a message and the service and endpoint, while other services do not yet use the framework (14 of 20). No idempotency keys or safe-retry guidance were found for writes. Order, shipment and allocation documents carry a version number, and SERVICE-4006 reports a concurrent modification (5 of 20). Every call needs a bearer token and a tenant header, the defaults are sensible, and no official SDK was found (5 of 15). Total 57. The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics): - 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries). - 20, pagination, filtering and output-size controls. - 20, actionable, documented error responses, codes and messages an agent can recover from. - 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations. - 15, sensible defaults, few required parameters, and official SDKs in at least two languages. Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs. ## 5. Security & auth, 62 out of 100, up to 6.7 more on the total Why it scored 62: OpenID Connect client credentials for system apps with one role each, 10-minute tokens and no refresh token, and the authorisation code flow with PKCE for shopper apps. Apps are created and managed by a merchant admin in Copilot. Roles are coarse rather than per-endpoint scopes (25 of 30). Least privilege is possible with the Viewer and Developer Viewer roles and editors limited to one module, but no confirmation step for destructive calls was found (14 of 20). The APIs return the merchant's own catalogue, order and customer data rather than outside content (10 of 15). The data security page says access logs and system changes are recorded, but no operator-facing API audit log was found, beyond a webhook event log in the v2 orders API (5 of 15). SOC 2 Type I and Type II and PCI DSS SAQ-A are listed in the docs. No security.txt, disclosure policy or bug bounty was found (8 of 20). Total 62. The checklist (https://www.anchorterminal.com/benchmark/#checklist-security): - 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option. - 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions. - 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10. - 0 to 15, audit logs or per-call visibility for the operator. - 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public. Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing. ## 6. Transparency & trust, 55 out of 100, up to 3.9 more on the total Made of editorial 35, provenance 74. Why it scored 55: Closed service with published terms (Terms and Conditions of 1 January 2026, SLA, website terms of use) (15 of 30). Data handling statements disagree in places. The terms delete customer content 90 days after termination, while the security page says data is kept for one month after the contract ends. The privacy policy dates from 14 January 2021, and the Data Processing Addendum it relies on returned 404. The terms say inputs may go to third-party language models and that Fabric may keep de-identified derived data (10 of 30). Deprecated v2 endpoints are marked in the reference and beta services carry 30 days' notice of discontinuation, but the legacy label on the v3 docs carries no dates (5 of 20). Hosting on AWS and third-party language models are disclosed, with no subprocessor list or data locations (5 of 20). Total 35. The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency): - 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms. - 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors). - 0 to 20, a deprecation policy or notices with dates. - 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted). The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two. Provenance checks not met in full (half of this category, computed from checked facts): - Domain age: fabric.inc, registered 2019-08-08 (7 years) (11 of 15) - Terms of service: read, states 7 of the 7 things a reader expects, and has 1 clause that costs points (8 of 10) - Status page: not found (0 of 10) - security.txt: not found (0 of 10) ## 7. Schema & documentation, 79 out of 100, up to 3.4 more on the total Why it scored 79: 69 public OpenAPI 3.0 files listed in llms.txt, about 980 operations (25 of 25). llms.txt, and every docs page served as Markdown at its path plus .md (10 of 10). Operation descriptions state purpose and filters, such as the order search explaining that filters go in the body and that 10 orders return by default, but few say when not to use an endpoint (12 of 20). Typed schemas with required fields and more than 1,000 enum declarations across the files (12 of 15). Request and response examples throughout, and standardised error codes with a published code list, implemented only for Orders and Inventory (12 of 15). Versions are in the path (v1, v2, v3) and release notes are dated, but the newest are from July 2025 and the Product Agent release notes link returned 404 (8 of 15). Total 79. The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema): APIs and MCP servers. - 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool). - 10, llms.txt or Markdown docs served for agents. - 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference. - 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs. - 0 to 15, examples and documented error responses. - 15, versioning and a public changelog. Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference. ## What we couldn't check What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it. - unchecked: whether the v3 order management, catalogue, pricing and cart APIs are still sold to new customers. The site markets only Merchandising Studio and Dropship, and the docs call v3 and v2 legacy products. - unchecked: the Data Processing Addendum at https://fabric.inc/data-processing-addendum and the API licence at https://fabric.inc/api-license, both 404 on 14 October 2026. - unchecked: rate limits. No figures were found in the docs or the OpenAPI files. - unchecked: Product Agent release notes. The link from the docs home page returned 404. - unchecked: support response times through support.fabric.inc, which was not tested. - The founder's list suggested the commerce category, which fits the order, catalogue and cart APIs. Product Agent itself is closer to product-data enrichment for AI search and is in beta. - The site footer says Fabric, Inc., while the terms, privacy policy and terms of use name Commerce Fabric, Inc. The listing uses Commerce Fabric, Inc. ## Weaknesses - No public price, free tier or self-serve signup. A trial account is arranged with Fabric - The v3 and v2 commerce docs are labelled legacy, and the newest dated release notes are from July 2025 - No status page, rate-limit figures, Retry-After guidance or idempotency keys were found - No official SDKs and no MCP server for the commerce APIs. The docs MCP server only searches documentation ## What costs an agent a turn today The notes we give agents before they call it. Each one is a workaround an agent shouldn't need. - Get the tenant ID and a System App client ID and secret from the merchant's Copilot admin, with the narrowest role the task needs - Request a new system token from {authURL}/v1/token every 10 minutes, since system apps receive no refresh token - Send x-fabric-tenant-id on every call, and x-fabric-channel-id where the merchant sells in more than one channel - Page order searches with offset and limit, because the default response returns 10 orders - Read errorCode and context.endpoint in Orders and Inventory errors, and check for duplicates before retrying a write ## When it's done Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.