Write a review

Head to head · Commerce catalogues · October 2026 research run

commercetools vs Fabric

commercetools scores 71.3 (BB) on agent readiness against Fabric's 43.7 (E), and leads in every scored category. Both do commerce catalogues.

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

commercetoolscommercetools GmbH · HTTP API BB71.3/100#135 of 1076 FabricCommerce Fabric, Inc. · HTTP API E43.7/100#949 of 1076

Which one, for what

commercetools BB

Best for Enterprises that already run or plan a composable commerce stack and want agents working across catalogue, pricing, carts and orders under scoped credentials.

Ahead on

  • Reliability, 73 against 23
  • Schema & documentation, 86 against 79
  • Agent ergonomics, 83 against 57
  • Security & auth, 70 against 62
  • Payments & pricing, 20 against 0
  • Maintenance & community, 85 against 15
  • Transparency & trust, 81 against 55

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine

Watch for

No public price. The pricing page describes order-based pricing and sends buyers to sales

Fabric E

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

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Score by category

CategoryWeight this runcommercetoolsFabricEdge
Reliability16%207323commercetools +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28679commercetools +7
Agent ergonomics13%16.28357commercetools +26
Security & auth14%17.57062commercetools +8
Payments & pricing10%12.5200commercetools +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88515commercetools +70
Transparency & trust7%8.88155commercetools +26
Negative events≤1500
TotalBB 71.3/100E 43.7/100

Facts side by side

FactcommercetoolsFabric
KindHTTP APIHTTP API
Vendorcommercetools GmbHCommerce Fabric, Inc.
Hosted endpointhttps://api.{region}.commercetools.com/{projectKey}https://api.fabric.inc/v3
TransportsHTTP, Streamable HTTP, stdioHTTP
AuthOAuthOAuth
PricingPaidPaid
x402nono
LicenceProprietary service under the commercetools Master Service Agreement. The API specifications are public, the SDKs are MIT (TypeScript, PHP) or Apache 2.0 (Java, .NET) and Commerce MCP is MITProprietary SaaS under Fabric's Terms and Conditions (last updated 1 January 2026) and an order form
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-07none
Terms last updatedno date given2026-01-01
Privacy policy last updatedno date given2021-01-14
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 benchmarkingyesyes
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
Popularity221k npm/wknone

Verdicts

commercetools

A public OpenAPI file with 822 operations, per-resource OAuth scopes and a managed MCP server whose tools an administrator selects per agent. Prices are quoted by sales only, and the HTTP API publishes no platform-wide rate limit. A 60-day trial needs no card.

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.

Before you call either

commercetools

  1. Use the auth and API hosts for the project's region, such as auth.europe-west1.gcp.commercetools.com and api.europe-west1.gcp.commercetools.com. There are five regions
  2. Send the resource's current version with every update or delete. On 409 ConcurrentModification, re-read the resource and retry only if the change is still needed
  3. Retry 502 and 503 with exponential backoff from 200 ms, honour Retry-After, and check Content-Type before parsing an error body
  4. For MCP, ask for an API Client scoped to mcp:{projectKey}:{mcpServerKey} and a server limited to the tools the task needs, not all
  5. Keep page size at or under 500 and offset at or under 10,000. Product Search returns at most 100 per request

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

Questions

Which is better for AI agents, commercetools or Fabric?

commercetools scores 71.3 (BB) on agent readiness against Fabric's 43.7 (E), and leads in every scored category.

Do commercetools and Fabric need an API key?

Both use an OAuth sign-in.

Can an agent call commercetools and Fabric without installing anything?

Yes. commercetools has a hosted endpoint at https://api.{region}.commercetools.com/{projectKey} and Fabric at https://api.fabric.inc/v3.

Other comparisons with commercetools or Fabric

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