Head to head · Commerce orders · October 2026 research run

Fabric vs Spree Commerce

Spree Commerce scores 70.4 (BB) 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

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
  • No incidents deducted, where Spree Commerce loses 5 points for them

Watch for

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

Spree Commerce BB

Best for Teams that want to own a Rails commerce backend with marketplace, B2B and multi-region functions and drive it through REST.

Ahead on

  • Reliability, 82 against 23
  • Schema & documentation, 85 against 79
  • Agent ergonomics, 90 against 57
  • Payments & pricing, 55 against 0
  • Maintenance & community, 81 against 15
  • Transparency & trust, 60 against 55

Also in its favour

  • Agent-ready, a grade of BB or better
  • Open source

Watch for

Six GitHub security advisories between 8 January and 20 July 2026, four rated High, most of them access-control flaws on guest carts, orders and addresses

Score by category

CategoryWeight this runFabricSpree CommerceEdge
Reliability16%202382Spree Commerce +59
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27985Spree Commerce +6
Agent ergonomics13%16.25790Spree Commerce +33
Security & auth14%17.56265Spree Commerce +3
Payments & pricing10%12.5055Spree Commerce +55
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81581Spree Commerce +66
Transparency & trust7%8.85560Spree Commerce +5
Negative events≤150-5
TotalE 43.7/100BB 70.4/100

Facts side by side

FactFabricSpree Commerce
KindHTTP APIHTTP API
VendorCommerce Fabric, Inc.Vendo Connect Inc
Hosted endpointhttps://api.fabric.inc/v3no (local only)
TransportsHTTPHTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary SaaS under Fabric's Terms and Conditions (last updated 1 January 2026) and an order formBSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence
Read-only variant documentednoyes
llms.txtyesyes
Last releasenone2026-07-28
Terms last updated2026-01-01no document linked
Privacy policy last updated2021-01-14no document linked
Customer content may train modelsnot found in the text
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingyes
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularitynone16k stars, 1.6k npm/wk

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.

Spree Commerce

A self-hosted BSD 3-Clause platform with public OpenAPI files for the Store and Admin APIs, scoped secret keys, documented rate limits and idempotency keys on cart and checkout calls. GitHub lists six security advisories between January and July 2026, four rated High, and the default docs describe the 6.0 release candidate while 5.6.1 is the stable release.

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

Spree Commerce

  1. Send a publishable key in X-Spree-Api-Key on every Store API call. Add X-Spree-Token with the cart token for guest carts, or a customer JWT as a Bearer token
  2. Send Idempotency-Key with the cart token or a customer JWT on cart, payment and completion calls. A request carrying only the publishable key is never cached
  3. Ask for fields and expand explicitly. Relations are left out by default and limit stops at 100
  4. Use a secret key with the narrowest scopes for the Admin API. read_all gives a read-only key, and the CLI's auto-minted local key is read-only
  5. Read the docs under /docs/v5 for a 5.6 store. The default docs describe 6.0, which renames shipments to fulfilments and splits carts from orders

Questions

Which is better for AI agents, Fabric or Spree Commerce?

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

Do Fabric and Spree Commerce need an API key?

Fabric uses an OAuth sign-in. Spree Commerce takes an API key or an OAuth sign-in.

Can an agent call Fabric and Spree Commerce without installing anything?

Fabric has a hosted endpoint at https://api.fabric.inc/v3. No hosted endpoint is listed for Spree Commerce.

Are Fabric and Spree Commerce open source?

No open-source release is listed for Fabric. Spree Commerce is open source (BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence).

Other comparisons with Fabric or Spree Commerce

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.