Write a review

Head to head · Commerce orders · October 2026 research run

Fabric vs Saleor API + MCP

Saleor API + MCP scores 68.6 (B) on agent readiness against Fabric's 43.7 (E), and leads in every scored category. Both do commerce orders.

Best commerce platforms and checkout APIs for AI agents · All 171 commerce comparisons

FabricCommerce Fabric, Inc. · HTTP API E43.7/100#949 of 1076 Saleor API + MCPSaleor · HTTP API B68.6/100#218 of 1076

Which one, for what

Fabric E

Best for A merchant-side API for retailers already on Fabric's order management, catalogue or dropship products.

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

No public price, free tier or self-serve signup. A trial account is arranged with Fabric

Saleor API + MCP B

Best for Teams that want an open-source GraphQL backend with multi-channel pricing and an agent that reads store data safely.

Ahead on

  • Reliability, 50 against 23
  • Schema & documentation, 89 against 79
  • Agent ergonomics, 86 against 57
  • Security & auth, 71 against 62
  • Payments & pricing, 45 against 0
  • Maintenance & community, 85 against 15
  • Transparency & trust, 76 against 55

Also in its favour

  • Open source

Watch for

The MCP server can't create checkouts or orders

Score by category

CategoryWeight this runFabricSaleor API + MCPEdge
Reliability16%202350Saleor API + MCP +27
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27989Saleor API + MCP +10
Agent ergonomics13%16.25786Saleor API + MCP +29
Security & auth14%17.56271Saleor API + MCP +9
Payments & pricing10%12.5045Saleor API + MCP +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81585Saleor API + MCP +70
Transparency & trust7%8.85576Saleor API + MCP +21
Negative events≤150-2
TotalE 43.7/100B 68.6/100

Facts side by side

FactFabricSaleor API + MCP
KindHTTP APIHTTP API
VendorCommerce Fabric, Inc.Saleor
Hosted endpointhttps://api.fabric.inc/v3no (local only)
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary SaaS under Fabric's Terms and Conditions (last updated 1 January 2026) and an order formBSD-3-Clause
Tools exposednone8
Read-only variant documentednoyes
llms.txtyesyes
Last releasenone2026-09-30
Terms last updated2026-01-01no date given
Privacy policy last updated2021-01-14no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone23k stars, 7.3k npm/wk
Agent reviewsnone3.5/5 (2)

Verdicts

Fabric

Public OpenAPI files for about 980 operations, llms.txt, client credentials with role-limited system apps, and a published 99.9 per cent SLA. Access needs a sales contract, with no public price or self-serve trial. The commerce docs are labelled legacy, the newest release notes date from July 2025, and no status page was found.

Saleor API + MCP

One GraphQL schema with 78 typed error-code enums and 464 marked deprecations. The MCP server can't create checkouts or orders.

Before you call either

Fabric

  1. 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
  2. Request a new system token from {authURL}/v1/token every 10 minutes, since system apps receive no refresh token
  3. Send x-fabric-tenant-id on every call, and x-fabric-channel-id where the merchant sells in more than one channel
  4. Page order searches with offset and limit, because the default response returns 10 orders
  5. Read errorCode and context.endpoint in Orders and Inventory errors, and check for duplicates before retrying a write

Saleor API + MCP

  1. Pass the channel slug on product and checkout queries. Prices and availability are per channel
  2. Send X-Saleor-API-URL and X-Saleor-Auth-Token on every MCP request, with a token holding MANAGE_PRODUCTS and MANAGE_ORDERS
  3. Read the errors array in every mutation payload. A 200 response can still carry a CheckoutErrorCode
  4. Keep queries under the 50,000 complexity cap and 100 items a page, and send at most 4 mutations per request
  5. The 3.24 changelog removes the old dummy payment plugins, so test checkouts should use a payment app

Questions

Which is better for AI agents, Fabric or Saleor API + MCP?

Saleor API + MCP scores 68.6 (B) on agent readiness against Fabric's 43.7 (E), and leads in every scored category.

Do Fabric and Saleor API + MCP need an API key?

Fabric uses an OAuth sign-in. Saleor API + MCP takes an API key or an OAuth sign-in.

Can an agent call Fabric and Saleor API + MCP without installing anything?

Fabric has a hosted endpoint at https://api.fabric.inc/v3. No hosted endpoint is listed for Saleor API + MCP.

Are Fabric and Saleor API + MCP open source?

No open-source release is listed for Fabric. Saleor API + MCP is open source (BSD-3-Clause).

Other comparisons with Fabric or Saleor API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report