# Spree Commerce > Spree Commerce is an open-source commerce platform on Ruby on Rails, maintained by Vendo Connect Inc. A self-hosted store runs a Store API for catalogue, cart and checkout, and an Admin API for back-office work. - Canonical: https://www.anchorterminal.com/tools/spree-commerce - Markdown: https://www.anchorterminal.com/tools/spree-commerce.md (~7,100 tokens) - Slim: https://www.anchorterminal.com/tools/spree-commerce.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/spree-commerce.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 ## Overview **Grade BB · 70.4/100 · rank #155 of 950 · #6 in Commerce & checkout · agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Vendo Connect Inc (https://spreecommerce.org) | | Kind | HTTP API | | Category | Commerce & checkout (https://www.anchorterminal.com/categories/commerce) | | Transport | HTTP | | Auth | OAuth or key · Store API calls need a publishable key (`pk_`) in the `X-Spree-Api-Key` header, plus a customer JWT as a Bearer token or a cart token in `X-Spree-Token` for guests. Admin API calls take a secret key (`sk_`) with `read_*` and `write_*` scopes per resource, or an admin JWT. Keys are created by the store's operator in the dashboard or with `spree api-key create`, with no vendor approval. | | Pricing | Freemium (Freemium) · Free to self-host under BSD 3-Clause, with no platform or transaction fee. The Enterprise Edition is custom pricing through sales. A free hosted Sandbox lets an agent's owner try the Admin API without a contract, for evaluation with test data only (https://spreecommerce.org/enterprise/, checked 2026-10-09). | | x402 | No · No x402, MPP or L402 in the docs, the OpenAPI files or the repository (checked 2026-10-09). Payments go through provider integrations such as Stripe, Adyen and PayPal. | | Licence | BSD-3-Clause for the backend, MIT for the npm packages. Enterprise Edition code is under a separate commercial licence | | Packages | npm: `@spree/sdk`; npm: `@spree/cli`; npm: `@spree/admin-sdk`; rubygems: `spree` | | Source | https://github.com/spree/spree | | Docs | https://spreecommerce.org/docs | | llms.txt | https://spreecommerce.org/docs/llms.txt | | Last release | 2026-07-28 | | GitHub stars | 15,750 (as of 2026-10-09) | | npm downloads / week | 1,576 | | Free tier | The Community Edition is free to self-host. The hosted Sandbox is free and for evaluation with test data only | | APIs | Store API at `/api/v3/store` (81 paths, 99 operations on main, 63 paths and 77 operations at 5.6.1), Admin API at `/api/v3/admin` (259 paths, 417 operations, since 5.5) and a Seller API in 6.0, all OpenAPI 3.0.3 | | Auth and scopes | Publishable keys (`pk_`) for the Store API, optionally bound to a sales channel. Secret keys (`sk_`) with `read_*` and `write_*` scopes per resource, or admin JWTs, for the Admin API | | Rate limits | Defaults of 300 requests a minute per API key, 5 logins, 3 registrations and 10 token refreshes a minute per IP. `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `Retry-After` headers. Configurable by the operator | | Cart and checkout | Carts, items, discount codes, gift cards, store credits, payment sessions and `POST /carts/{id}/complete`, which returns an order. Guest carts use a cart token | | Idempotency | `Idempotency-Key` on eight cart, checkout and payment calls, cached 24 hours and replayed with `Idempotent-Replayed: true`. Not cached for callers with only a publishable key | | Errors | One `error` object with `code`, `message` and per-field `details`. 34 codes, among them `insufficient_stock`, `cart_cannot_complete` and `rate_limit_exceeded` | | Webhooks | Signed with HMAC-SHA256 in `X-Spree-Webhook-Signature` with a timestamp, retried with growing delays, and re-sendable from a delivery log | | SDKs and CLI | `@spree/sdk` 1.2.1 (Store), `@spree/admin-sdk` 0.1.0 on npm with 1.0.0-rc.1 in the repository, `@spree/seller-sdk`, and `@spree/cli` 3.2.2 with `spree api get/post/patch/delete`. TypeScript only | | MCP server | Official and hosted at https://spreecommerce.org/docs/mcp with no authentication. Two tools, docs search and page read. No store data | | Open source | BSD 3-Clause backend on Ruby on Rails 8.1, MIT npm packages. Postgres, MySQL or SQLite. Official Docker images | | Enterprise Edition | Custom pricing. Adds multi-tenancy, approval workflows, Shopify and WooCommerce seller sync, audit trail, encryption at rest, long-term support releases and SLA support | | Capabilities | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | | Tags | open-source, self-hosted, local, openapi, llms-txt, mcp, typescript, ruby, webhooks, freemium | | JSON | https://www.anchorterminal.com/api/v1/tools/spree-commerce.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 82 | 16.4 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 85 | 13.8 | | Agent ergonomics | 13% | 16.2 | 90 | 14.6 | | Security & auth | 14% | 17.5 | 65 | 11.4 | | Payments & pricing | 10% | 12.5 | 55 | 6.9 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 81 | 7.1 | | Transparency & trust (editorial 75, provenance 45) | 7% | 8.8 | 60 | 5.2 | | Negative events | up to −15 | up to −15 | 2026-07-20: six security advisories were published for `spree_api` and related gems between 8 January and 20 July 2026, four rated High, among them guest address and order disclosure without authentication (GHSA-87fh-rc96-6fr6, GHSA-p6pv-q7rc-g4h9, 5 February) and a guest cart takeover on `PATCH /api/v3/store/carts/:id/associate` (GHSA-4825-p4xm-pcf2, 20 July, fixed in 5.4.4 and 5.5.4). All are published with patched versions, so the deduction is reduced (https://github.com/spree/spree/security/advisories). | -5 | | **Total** | | | | **70.4 → BB** | ### Why each score - Reliability 82: Graded as software the owner runs. Installs with `npx create-spree-app@latest` or the `spree` gem, with Node, Docker, Ruby 3.2 or later and Rails 8.1 stated (20). A public Tests workflow runs on Postgres and MySQL, and most of the 25 latest runs listed on 9 October 2026 completed successfully, with two failures on pull-request branches (22). 95 open issues against 1,798 commits since 10 July 2026, many of them roadmap items. Reply times were not read (18). The release policy is a shifted semantic versioning in which minor releases may break, with an upgrade guide per minor and `CHANGELOG.md` pointing to GitHub releases (9). 5.6.1 is stable, but the default docs describe the 6.0 release candidate and `@spree/admin-sdk` is 0.1.0 on npm (13). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 85: OpenAPI 3.0.3 files for the Store API (81 paths, 99 operations) and Admin API (259 paths, 417 operations) are public (25). llms.txt and a Markdown copy of each page (10). Every Admin operation and 91 of 99 Store operations carry a description, which says what the call does and rarely when not to use it (13). Typed parameters with required fields and 48 enums in the Store file, though `fields`, `expand` and Ransack `q[...]` filters are free strings (11). Error codes are tabled with JSON examples, and the Store file documents 401, 404 and 422 responses but not 429 (13). The path carries `/api/v3`, docs are split into v5.x and v6.x, and a dated changelog has an RSS feed, but the default version documents a release candidate (13). - Agent ergonomics 90: `fields` trims a response, `expand` adds relations that are left out by default, and `limit` caps a page (23). `page`, `limit` up to 100, `sort` and Ransack filters on list calls, with a `meta` block of counts (20). Errors carry a machine-readable `code`, a `message` and per-field `details`, with 34 documented codes (19). `Idempotency-Key` on eight cart, checkout and payment calls with a 24-hour cache, optimistic locking on carts, and SDK retries with backoff. Guest cart creation is not covered (18). Few required parameters and three TypeScript SDKs plus a CLI, with no official client in a second language (10). - Security & auth 65: Publishable keys for the Store API and secret keys with `read_*` and `write_*` scopes per resource for the Admin API, shown once, revocable, with last-used dates. Keys travel in headers and have no expiry (28). `read_all` gives a read-only key, the CLI mints only read-only keys by itself, and a key cannot create a key with wider scopes. No confirmation step for destructive calls was found (15). The API returns merchant and shopper text, and no prompt-injection guidance was found in the reviewed documentation (5). The audit trail is Enterprise only. The open-source edition has last-used dates on keys and a webhook delivery log (5). `SECURITY.md` with a security mailbox, a 72-hour acknowledgement target, advisories published on GitHub, Dependabot and a weekly audit workflow. No bounty, no security.txt and no certification (12). - Payments & pricing 55: Read with the self-hosted rule. No x402, MPP or L402 (0). The Community Edition is free and its scope is public, while the Enterprise Edition is listed as custom pricing (15). Nothing to pay and no card for the open-source edition (20). An agent can install a store with `npx create-spree-app@latest`, which has an option for every prompt and prints the API keys, and the CLI mints a read-only key in a local project (20). The hosted Sandbox is free but needs a browser sign-up and is for evaluation only. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 81: The stable server release is 5.6.1 of 28 July 2026, 73 days before the check (20). `@spree/cli` 3.2.2 and the 6.0.0.rc1 tag are dated 8 October 2026 and are not counted for recency. More than three releases in 90 days, among them 5.6.0, 5.6.1, 5.5.4, 5.4.4 and five 6.0 pre-releases (20). 95 open issues and 86 open pull requests, the newest issues opened on 8 and 9 October, and 1,798 commits since 10 July. Reply times were not read (17). Current official TypeScript SDKs and CLI on npm (15). Dependabot weekly for gems and Actions, a weekly `pnpm audit` workflow and CI on every pull request (9). - Transparency & trust 60: BSD 3-Clause for the backend, MIT for the npm packages and CC BY 4.0 for the docs. Enterprise Edition code is under a separate commercial licence and is not in the repository (28). The software runs on the operator's servers, so store data stays with the operator. Vendo's only privacy notice covers its websites and the hosted Sandbox, with lead data kept up to 24 months and recipients named by category only (20). The release policy pairs breaking changes with deprecation notices in the previous release and lists supported versions with end dates, but the two published copies of that list disagree (12). No telemetry was found in the CLI or installer source, and an open issue titled Telemetry and Update Check plans it (15). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (21 items): https://www.anchorterminal.com/fixes/spree-commerce.md (JSON https://www.anchorterminal.com/fixes/spree-commerce.json) ### What we couldn't check - unchecked: spree.sh and console.spree.sh were not read, because the Sandbox terms forbid scraping without Vendo's consent. Sandbox limits and the sign-up flow are known only from the terms and the CLI docs - unchecked: reply times on GitHub issues and pull requests - unchecked: the patched versions of four of the six 2026 advisories. Two advisory pages were read in full - unchecked: the tool definitions of the docs MCP server at https://spreecommerce.org/docs/mcp. The docs say it has two tools, search and read - Docs pages other than those fetched as Markdown were read from the repository's `docs` folder at commit 4ca24b8, which is the source of the published site - No terms or privacy document governs the self-hosted software. The only published terms and privacy notice cover the hosted Sandbox, so both provenance fields are left out and the BSD 3-Clause licence stands in - Which supported-version table is current. `SECURITY.md` gives 5.x until 26 March 2027 and 4.10 until 6 September 2026, and the docs give 5.0 until 26 March 2028 and 4.10 until 6 September 2027 - The 5.5 to 5.6 upgrade guide refers to a 5.6.2 release, and no 5.6.2 tag or gem was found ### Sources - Sandbox terms and conditions: (seen 2026-10-09) - Sandbox privacy notice: (seen 2026-10-09) - docs llms.txt: (seen 2026-10-09) - API keys and scopes: (seen 2026-10-09) - Enterprise Edition security overview: (seen 2026-10-09) - editions and Enterprise pricing: (seen 2026-10-09) - repository at commit 4ca24b8 (docs, OpenAPI files, `SECURITY.md`, `LICENSE`, workflows, tags): (seen 2026-10-09) - Store API rate limits: (seen 2026-10-09) - Store API idempotency: (seen 2026-10-09) - Store API errors: (seen 2026-10-09) - Admin API authentication and scopes: (seen 2026-10-09) - docs MCP server: (seen 2026-10-09) - upgrade and release policy: (seen 2026-10-09) - security advisories: (seen 2026-10-09) - releases: (seen 2026-10-09) - open issues: (seen 2026-10-09) - Tests workflow runs: (seen 2026-10-09) - `@spree/cli` release dates: (seen 2026-10-09) - `@spree/sdk` weekly downloads: (seen 2026-10-09) - `spree` gem version and date: (seen 2026-10-09) - domain registration: (seen 2026-10-09) ## Who's behind it (provenance 45/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Vendo Connect Inc | 20/20 | | Domain age | spreecommerce.org, registered 2009-04-03 (17 years) | 15/15 | | Endpoint on the vendor's domain | is not on spreecommerce.org | 0/15 | | Terms of service | not found | 0/10 | | Privacy policy | not found | 0/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The Sandbox terms name VENDO CONNECT INC, a Delaware corporation (file number 7005612), 3500 S DuPont Highway, Dover, Delaware 19901, as the company behind the Spree Commerce project. The `LICENSE` file also names Vendo Sp. z o.o. as a copyright holder. The API runs on the operator's own server, so there is no vendor endpoint and no vendor status page. No terms or privacy document governs the self-hosted software, and the BSD 3-Clause licence stands in. The published terms (https://spreecommerce.org/terms-of-service/) and privacy notice (https://spreecommerce.org/privacy-policy-sandbox/), both dated 10 July 2026, cover only the hosted Sandbox and Vendo's websites. https://spreecommerce.org/.well-known/security.txt returns 404. `SECURITY.md` in the repository gives a security mailbox for reports. RDAP for spreecommerce.org gives a registration date of 2009-04-03 and GoDaddy.com, LLC as registrar. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service**. We found no terms of service published for this product, so there is nothing to read and the check scores 0. **Privacy policy**. We found no privacy policy published for this product, so there is nothing to read and the check scores 0. ## Live (updated 2026-10-09 17:21 UTC) - github `spree/spree` v5.6.1, released 2026-07-28 - npm `@spree/admin-sdk` 0.1.0 - npm `@spree/cli` 3.2.2 - npm `@spree/sdk` 1.2.1 - Always current: https://www.anchorterminal.com/api/v1/live/spree-commerce.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Community Edition, self-hosted | free | per month (plan) | BSD 3-Clause, the operator pays for its own servers | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - OpenAPI 3.0.3 files for the Store API (81 paths, 99 operations) and Admin API (259 paths, 417 operations), plus llms.txt and a Markdown copy of every docs page - Secret keys carry `read_*` and `write_*` scopes per resource, are shown once and can be revoked, and a key cannot create a key with wider scopes - `Idempotency-Key` on eight cart, checkout and payment calls, cached for 24 hours, with `Retry-After` on 429 responses - Rate limits are published with numbers, 300 requests a minute per API key by default, and the operator can change them - BSD 3-Clause backend and MIT TypeScript packages, with marketplace and B2B functions in the open-source edition ## Weaknesses - 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 - The default docs and the main-branch OpenAPI files describe 6.0, a release candidate dated 8 October 2026. The stable release is 5.6.1 of 28 July 2026 - The audit trail is in the paid Enterprise Edition only, and Enterprise prices are not published - Supported-version end dates differ between `SECURITY.md` (5.x until 26 March 2027) and the docs security policy (5.0 until 26 March 2028) - The official MCP server searches and reads the docs only. Store and admin MCP servers are open roadmap issues ## Before you call it (notes for agents) 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 ## Connect Install: ```bash npx create-spree-app@latest my-store ``` First request: ```bash curl -X GET 'http://localhost:3000/api/v3/store/products' -H 'X-Spree-Api-Key: pk_xxx' ``` Claude Code: ```bash claude mcp add --transport http spree-docs https://spreecommerce.org/docs/mcp ``` MCP client configuration: ```json { "mcpServers": { "spree-docs": { "url": "https://spreecommerce.org/docs/mcp" } } } ``` Through letme (picks today, calling later): https://letme.dev/spree-commerce. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Shopify API + MCP | BB | 75 | 58 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | no | https://www.anchorterminal.com/tools/shopify.md | | WooCommerce API + MCP | BB | 72.9 | 97 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | no | https://www.anchorterminal.com/tools/woocommerce.md | | Shopware | BB | 71.4 | 129 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | no | https://www.anchorterminal.com/tools/shopware.md | | commercetools | BB | 71.3 | 133 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | no | https://www.anchorterminal.com/tools/commercetools.md | | Vendure | BB | 70.9 | 140 | commerce.products, commerce.cart, commerce.checkout, commerce.orders, commerce.headless | no | https://www.anchorterminal.com/tools/vendure.md | | Square | B | 69.2 | 195 | commerce.products, commerce.orders, commerce.checkout, commerce.cart, commerce.headless | no | https://www.anchorterminal.com/tools/square.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Store API and Admin API OpenAPI 3.0.3 files are linked from llms.txt, with every docs page also served as Markdown (source: ) - Secret keys take `read_*` and `write_*` scopes per resource, and a key holding `write_api_keys` can only create keys with scopes it already holds (source: ) - `Idempotency-Key` is supported on eight cart, checkout and payment calls with a 24-hour cache (source: ) - GitHub lists six security advisories between 8 January and 20 July 2026, four rated High (source: ) - v6.0.0.rc1 was tagged on 8 October 2026 and the default docs describe 6.0. The stable release is 5.6.1 of 28 July 2026 (source: ) - The official MCP server searches and reads the documentation and needs no authentication (source: ) - The Sandbox terms of 10 July 2026 call the hosted Sandbox an evaluation vehicle for fictitious test data and forbid scraping and load testing without consent (source: ) - #6 of 17 in Best commerce platforms and checkout APIs for AI agents: https://www.anchorterminal.com/best/commerce/index.md - All 136 commerce comparisons: https://www.anchorterminal.com/compare/commerce/index.md ## Compare - [Adobe Commerce (Magento) vs Spree Commerce](https://www.anchorterminal.com/compare/adobe-commerce-vs-spree-commerce.md): B 63.9 vs BB 70.4 - [BigCommerce API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/bigcommerce-vs-spree-commerce.md): B 64.3 vs BB 70.4 - [Commerce Layer API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/commerce-layer-vs-spree-commerce.md): B 63.7 vs BB 70.4 - [commercetools vs Spree Commerce](https://www.anchorterminal.com/compare/commercetools-vs-spree-commerce.md): BB 71.3 vs BB 70.4 - [Ecwid by Lightspeed vs Spree Commerce](https://www.anchorterminal.com/compare/ecwid-vs-spree-commerce.md): B 63.2 vs BB 70.4 - [Elastic Path API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/elastic-path-vs-spree-commerce.md): D 50.1 vs BB 70.4 - [Medusa API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/medusa-vs-spree-commerce.md): B 63.5 vs BB 70.4 - [Saleor API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/saleor-vs-spree-commerce.md): B 68.6 vs BB 70.4 - [Shopify API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/shopify-vs-spree-commerce.md): BB 75 vs BB 70.4 - [Shopware vs Spree Commerce](https://www.anchorterminal.com/compare/shopware-vs-spree-commerce.md): BB 71.4 vs BB 70.4 - [Snipcart API + MCP vs Spree Commerce](https://www.anchorterminal.com/compare/snipcart-vs-spree-commerce.md): E 40.8 vs BB 70.4 - [Spree Commerce vs Square](https://www.anchorterminal.com/compare/spree-commerce-vs-square.md): BB 70.4 vs B 69.2 - [Spree Commerce vs Swell](https://www.anchorterminal.com/compare/spree-commerce-vs-swell.md): BB 70.4 vs C 55 - [Spree Commerce vs Vendure](https://www.anchorterminal.com/compare/spree-commerce-vs-vendure.md): BB 70.4 vs BB 70.9 - [Spree Commerce vs Wix Stores and eCommerce API](https://www.anchorterminal.com/compare/spree-commerce-vs-wix.md): BB 70.4 vs C 61.4 - [Spree Commerce vs WooCommerce API + MCP](https://www.anchorterminal.com/compare/spree-commerce-vs-woocommerce.md): BB 70.4 vs BB 72.9 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on spreecommerce.org or one of its subdomains, or the README of github.com/spree/spree. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "spree-commerce", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Spree Commerce on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Spree Commerce on Anchor Terminal](https://www.anchorterminal.com/badges/spree-commerce.svg)](https://www.anchorterminal.com/tools/spree-commerce) ``` Plain link: ```html Spree Commerce on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Spree Commerce is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/spree-commerce-dark.png - Light: https://www.anchorterminal.com/assets/share/spree-commerce-light.png