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
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
| Category | Weight this run | Fabric | Spree Commerce | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 23 | 82 | Spree Commerce +59 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 79 | 85 | Spree Commerce +6 |
| Agent ergonomics | 13%16.2 | 57 | 90 | Spree Commerce +33 |
| Security & auth | 14%17.5 | 62 | 65 | Spree Commerce +3 |
| Payments & pricing | 10%12.5 | 0 | 55 | Spree Commerce +55 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 15 | 81 | Spree Commerce +66 |
| Transparency & trust | 7%8.8 | 55 | 60 | Spree Commerce +5 |
| Negative events | ≤15 | 0 | -5 | |
| Total | E 43.7/100 | BB 70.4/100 |
Facts side by side
| Fact | Fabric | Spree Commerce |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Commerce Fabric, Inc. | Vendo Connect Inc |
| Hosted endpoint | https://api.fabric.inc/v3 | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary SaaS under Fabric's Terms and Conditions (last updated 1 January 2026) and an order form | BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | none | 2026-07-28 |
| Terms last updated | 2026-01-01 | no document linked |
| Privacy policy last updated | 2021-01-14 | no document linked |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | not found in the text | |
| Terms restrict benchmarking | yes | |
| Terms or service can change without notice | not found in the text | |
| Arbitration or class-action waiver | not found in the text | |
| Popularity | none | 16k 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
- 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
Spree Commerce
- Send a publishable key in
X-Spree-Api-Keyon every Store API call. AddX-Spree-Tokenwith the cart token for guest carts, or a customer JWT as a Bearer token - Send
Idempotency-Keywith the cart token or a customer JWT on cart, payment and completion calls. A request carrying only the publishable key is never cached - Ask for
fieldsandexpandexplicitly. Relations are left out by default andlimitstops at 100 - Use a secret key with the narrowest scopes for the Admin API.
read_allgives a read-only key, and the CLI's auto-minted local key is read-only - Read the docs under
/docs/v5for 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
- Adobe Commerce (Magento) vs Fabric
- Adobe Commerce (Magento) vs Spree Commerce
- Agentzon vs Fabric
- Agentzon vs Spree Commerce
- BigCommerce API + MCP vs Fabric
- BigCommerce API + MCP vs Spree Commerce
- Commerce Layer API + MCP vs Fabric
- Commerce Layer API + MCP vs Spree Commerce
- commercetools vs Fabric
- commercetools vs Spree Commerce
- Ecwid by Lightspeed vs Fabric
- Ecwid by Lightspeed vs Spree Commerce
- Elastic Path API + MCP vs Fabric
- Elastic Path API + MCP vs Spree Commerce
- Medusa API + MCP vs Spree Commerce
- Saleor API + MCP vs Spree Commerce
- Shopify API + MCP vs Spree Commerce
- Shopware vs Spree Commerce
- Snipcart API + MCP vs Spree Commerce
- Spree Commerce vs Square
- Spree Commerce vs Swell
- Spree Commerce vs Vendure
- Spree Commerce vs Wix Stores and eCommerce API
- Spree Commerce vs WooCommerce API + MCP
- Fabric vs Medusa API + MCP
- Fabric vs Saleor API + MCP
- Fabric vs Shopify API + MCP
- Fabric vs Shopware
- Fabric vs Snipcart API + MCP
- Fabric vs Square
- Fabric vs Swell
- Fabric vs Vendure
- Fabric vs Wix Stores and eCommerce API
- Fabric vs WooCommerce API + MCP
Machine-readable
- This page as Markdown
/compare/fabric-vs-spree-commerce.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/fabric.json·/api/v1/tools/spree-commerce.json - From a terminal
anchor compare fabric spree-commerce(the CLI) - Over MCP
compare_tools {"a": "fabric", "b": "spree-commerce"}at/mcp, no key