Head to head · Commerce catalogues · October 2026 research run
BigCommerce API + MCP vs Vendure
Vendure scores 72.3 (BB) on agent readiness against BigCommerce API + MCP's 69.9 (B), and leads in 5 of 7 scored categories. BigCommerce API + MCP leads on security & auth. Both do commerce catalogues.
Best commerce platforms and checkout APIs for AI agents · All 189 commerce comparisons
Which one, for what
Best for Agents working with existing BigCommerce stores, for back-office automation through REST or guest shopping through the MCP.
Ahead on
- Security & auth, 70 against 65
Also in its favour
- No incidents deducted, where Vendure loses 6 points for them
Watch for
The storefront MCP has no back-office tools and documents no tool annotations; back-office tools are only in an invite-only closed beta
Vendure BB
Best for TypeScript teams that want a typed GraphQL commerce server and will host it.
Ahead on
- Reliability, 89 against 77
- Schema & documentation, 91 against 66
- Agent ergonomics, 68 against 62
- Payments & pricing, 75 against 60
Also in its favour
- Agent-ready, a grade of BB or better
- Open source
Watch for
No vendor-hosted API. Vendure Cloud is in a closed beta for paid subscribers
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation Vendure +25
BigCommerce API + MCP 66
Reference pages are built from API specs (a 29 September changelog entry corrected twenty of them), but the public spec repo was archived in December 2023 and its successor, bigcommerce/docs, still asked git for credentials on 2 October, so no current spec file was found (10). llms.txt hub linking a developer index of about 500 Markdown pages, plus a docs MCP server (10). Reference descriptions say what each call does, and the MCP tools are guest shopping steps (12). Typed REST parameters in the reference (11). Examples in the reference, but the developer index has no page on error responses (10). Dated changelog with entries almost daily, v2 and v3 REST paths, and a Deprecations and Sunsets page, though it gives no notice period (13).
Vendure 91
Typed GraphQL Shop and Admin APIs with introspection, and schema-shop.json and schema-admin.json committed to the repo (25). llms.txt at docs.vendure.io, 997 lines on 1 November, including the MCP server guides (10). Guides and GraphQL reference describe each operation, with little on when not to use one (13). Strict GraphQL input types with enums and required markers (14). Expected failures come back as ErrorResult union types with an errorCode and message, explained in the error-handling guide with examples (14). Semver tags and a dated CHANGELOG with security and behaviour-change sections (15).
Payments & pricing Vendure +15
BigCommerce API + MCP 60
No x402, MPP or L402 (0). Plan prices public, Core $39, Growth $105 and Scale $399 a month with GMV caps and 2.0, 1.0 and 0.6 per cent on orders through non-embedded providers, but nothing per call (10). 15-day free trial, and the pricing page says no credit card is needed (20). An agent can shop any store that has switched on the MCP as a guest with no key, but back-office access needs a person to create an API account (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Vendure 75
No x402, MPP or L402 (0). Core is free. Platform plans are now public, Starter €199, Growth €599 and Scale €2,499 a month excl. VAT, Enterprise from €60,000 a year, with no fee on revenue or orders, so plan-only credit (10). Core is free under GPLv3 with no card, and Starter and Growth have a 30-day trial with no card (20). An agent can scaffold a store with npx @vendure/create or query the public read-only demo Shop API without an account (20). 0+10+20+20 = 50. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.
Reliability Vendure +12
BigCommerce API + MCP 77
Atlassian Statuspage at status.bigcommerce.com with API & Webhooks, Checkout & Payment Processing, Storefront and B2B components, a history page and an Atom feed (20). Read on 2 November, the history holds 36 incidents from 4 August, 8 in August, 8 in September and 20 in October. Seven carry a major or critical label, each partial by its own text. Microsoft single sign-on failed for a subset of stores for 29 minutes (25 August), Modern Import/Export catalogue export failed for 65 minutes (14 September), the Contact Center phone system was down (16 September, not the platform), category pages showed inaccurate stock (23 September), QuickBooks Payments stores couldn't take payments for 3 hours 39 minutes (5 October, one provider), some Chrome on Android shoppers on headless storefronts couldn't reach checkout (26 October), and Bolt payments failed for 2 hours 12 minutes after Bolt changed its domain (27 October, one provider). Search returned HTTP 500s across the platform for 66 minutes on 27 October, search only, and Management API add-to-cart requests failed for 59 minutes on 12 October. The 10 July availability major left the window on 8 October, so with only partial incidents the line is 20 (was 10, cause time). Published limits, 450 requests per 30 seconds on Scale and 150 on Growth and Core, refreshed every 30 seconds (15). A 429 carries X-Rate-Limit-Time-Reset-Ms and the docs advise waiting that long, then backing off exponentially. No idempotency keys for writes found (12). No SLA found (0). REST APIs are generally available, and the storefront MCP pages no longer carry a beta label, with the server switched on from the standard Settings, API and MCP page. The invite-only Store Management MCP beta isn't graded (10).
Vendure 89
Graded with the self-hosted package checklist, since there's no generally available hosted API (Vendure Cloud is in a closed beta for paid subscribers, general availability planned for Q1 2027). @vendure/core on npm with Node 20, 22 and 24 stated as tested, per the 1 October check (20). Build and test workflow on master, passing per the 1 October check; GitHub's pages and API refused us on 1 November, and the clone shows the workflow still in place (25). 170 open issues per the 1 October check, not re-read on 1 November. 3.8.1 fixes the 9 September stale-surcharge bug among 33 fixes (17). Dated CHANGELOG per release with security, behaviour-change and BREAKING CHANGE sections, but 3.7.3 and 3.7.4 changed behaviour in patch releases to close security holes and 3.8.0 is a minor release that needs a database migration (12). Version 3.x (15). 20+25+17+12+15 = 89.
Agent ergonomics Vendure +6
BigCommerce API + MCP 62
The B2C storefront MCP reference lists 7 compact, shopping-only tools, and search_products pages with a cursor (23). REST listings take page and limit, with filters such as id:in, type and severity on the store logs endpoint, and the GraphQL Storefront API documents pagination (16). 429 handling is documented, but we found no error-format reference in the docs index (10). No idempotency keys, and the MCP reference documents no tool annotations (0). Guest MCP needs no key. Official API clients for Python, PHP, Ruby and Node, three updated in 2026 and the Python client last in January 2024 (13).
Vendure 68
GraphQL field selection sizes every response (23). List queries take take, skip, filter and sort (20). ErrorResult types such as InsufficientStockError carry a code and message an agent can branch on (18). No idempotency keys or retry guidance found in the GraphQL APIs, and repeating addItemToOrder adds the quantity again (0). The Shop API works anonymously with a session token, but there's no official client SDK in any language (7). The MCP plugin released in 3.8.0 (18 shop and 24 admin tools, each marked readonly, mutating or destructive and mapped to readOnlyHint and destructiveHint) is an optional plugin and isn't scored here, since the listing is graded on the GraphQL APIs. 23+20+18+0+7 = 68.
Security & auth BigCommerce API + MCP +5
BigCommerce API + MCP 70
API accounts issue a token limited by OAuth scopes chosen at creation and revocable by deleting the account, but tokens never expire and can't be rotated in place (24). Read-only scope variants, and the storefront MCP has no back-office tools, so a guest agent can only shop. The invite-only Store Management MCP beta adds OAuth 2.1 with PKCE, per-scope grants that start at none, products and promotions created hidden or disabled, and refunds only after a quote, but it isn't generally available, so it moves no line (16). The MCP returns merchant product content with no prompt-injection guidance found (5). The store logs API (GET /v3/store/systemlogs) keeps storefront events such as order status changes for 365 days, and the control panel keeps staff action logs (a status incident on 8 July names them). No per-call API log found (8). Trust centre lists PCI DSS Level 1 as merchant and service provider, SOC 1, SOC 2 and SOC 3, ISO/IEC 27001:2022 with 27017, 27018 and 27701, and a vulnerability disclosure programme run through Inspectiv. No security.txt (404 on 2 November) (17).
Vendure 65
API keys since 3.6, each tied to roles and channels, bcrypt-hashed, shown once and rotatable, sent in a vendure-api-key header. Since 3.7.4 the API key mutations check the caller holds every permission of the key's roles. No OAuth in the GraphQL APIs; the MCP plugin uses OAuth 2.1 (28). Roles and permissions per channel, Shop API sessions refused on the Admin API since 3.8.0, and the harden plugin caps query complexity, but no confirmation step for destructive mutations (14). Returns merchant- and shopper-entered text with no prompt-injection guidance found (5). The MCP plugin released in 3.8.0 records every tool call in a McpToolCallLog table, always on, read through the dashboard and Admin API with 30 days' retention by default. The listing is graded on the GraphQL APIs, which still have no per-call log beyond order and customer history, so the plugin's log isn't scored here, as the ergonomics note treats the plugin (5). SECURITY.md takes private reports through GitHub and supports only the latest 3.x minor. Advisories are published with each release, 11 in 3.7.3, two in 3.7.4, one in 3.8.0 and three in 3.8.1. No security.txt (404), bounty or certification found (13). 28+14+5+5+13 = 65.
Score by category
| Category | Weight | BigCommerce API + MCP | Vendure | Edge |
|---|---|---|---|---|
| Reliability | 16% | 77 | 89 | Vendure +12 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 66 | 91 | Vendure +25 |
| Agent ergonomics | 13% | 62 | 68 | Vendure +6 |
| Security & auth | 14% | 70 | 65 | BigCommerce API + MCP +5 |
| Payments & pricing | 10% | 60 | 75 | Vendure +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 85 | Vendure +3 |
| Transparency & trust | 7% | 77 | 74 | BigCommerce API + MCP +3 |
| Negative events | ≤15 | 0 | -6 | |
| Total | B 69.9/100 | BB 72.3/100 |
Facts side by side
| Fact | BigCommerce API + MCP | Vendure |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | BigCommerce (Commerce.com) | Vendure (Elevantiq GmbH) |
| Hosted endpoint | https://api.bigcommerce.com | https://readonlydemo.vendure.io/shop-api |
| Transports | HTTP, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | none | GPL-3.0-or-later |
| Tools exposed | 7 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-30 | 2026-10-23 |
| Terms last updated | 2026-06-01 | not read yet |
| Privacy policy last updated | 2026-01-28 | no date given |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | none | 8.5k stars, 30k npm/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | BigCommerce API + MCP | Vendure |
|---|---|---|
| GullBrowser and end-to-end tester | 3/5 Seven tools to a checkout link, then a shopper takes over | 3/5 Six mutations to an order, on a server you bring |
| WardenSecurity auditor | 3/5 Scoped tokens that never expire | 3/5 Eleven advisories in one patch, and keys that stay in their lane |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
BigCommerce API + MCP
Rate limits are published per plan, and every 429 carries X-Rate-Limit-Time-Reset-Ms. Status incidents since August were partial. The storefront MCP lets a guest agent shop with no key but documents no tool annotations, back-office MCP tools are in an invite-only beta, and REST tokens never expire.
Vendure
Full cart, coupon, shipping and payment flow in the GraphQL Shop API, with ErrorResult types an agent can branch on, and an official MCP plugin since 3.8.0. No vendor-hosted API yet. Version 3.8.0 needed a database migration in a minor release, and core sends usage telemetry by default.
Before you call either
BigCommerce API + MCP
- Give the agent a store-level API account with only the scopes the task needs, and delete it when done
- On a 429, wait X-Rate-Limit-Time-Reset-Ms before retrying
- Expect up to 10 minutes after a store owner enables the MCP before the URL answers
- The MCP stops at a checkout URL. Payment happens in the shopper's browser
- Point a coding agent at the docs MCP at https://docs.bigcommerce.com/_mcp/server
- Store Management MCP is invite-only; if granted, call get_refund_quote and confirm with a person before create_refund, which the docs say is never safe to retry
Vendure
- Keep the session token from the first Shop API response and send it on every call. It holds the active order
- Check each mutation result's
__typenameanderrorCode. Expected failures return 200 with an ErrorResult - Don't retry addItemToOrder blindly. Read the active order first, since a repeat adds the quantity again
- For server-side work, enable
api-keyin authOptions.tokenMethod and give the key one role in one channel - Run 3.8.1 or later, and run the 3.8 migration before upgrading. Only the latest 3.x minor gets security fixes
- Set
VENDURE_DISABLE_TELEMETRY=trueon servers that shouldn't report usage to telemetry.vendure.io
Questions
Which is better for AI agents, BigCommerce API + MCP or Vendure?
Vendure scores 72.3 (BB) on agent readiness against BigCommerce API + MCP's 69.9 (B), and leads in 5 of 7 scored categories. BigCommerce API + MCP leads on security & auth.
Do BigCommerce API + MCP and Vendure need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call BigCommerce API + MCP and Vendure without installing anything?
Yes. BigCommerce API + MCP has a hosted endpoint at https://api.bigcommerce.com and Vendure at https://readonlydemo.vendure.io/shop-api.
Are BigCommerce API + MCP and Vendure open source?
No open-source release is listed for BigCommerce API + MCP. Vendure is open source (GPL-3.0-or-later).
Other comparisons with BigCommerce API + MCP or Vendure
- Adobe Commerce (Magento) vs BigCommerce API + MCP
- Adobe Commerce (Magento) vs Vendure
- Agentzon vs BigCommerce API + MCP
- Agentzon vs Vendure
- BigCommerce API + MCP vs Commerce Layer API + MCP
- BigCommerce API + MCP vs commercetools
- BigCommerce API + MCP vs Ecwid by Lightspeed
- BigCommerce API + MCP vs Elastic Path API + MCP
- BigCommerce API + MCP vs Fabric
- BigCommerce API + MCP vs Medusa API + MCP
- BigCommerce API + MCP vs Saleor API + MCP
- BigCommerce API + MCP vs Shopify API + MCP
- BigCommerce API + MCP vs Shopware
- BigCommerce API + MCP vs Snipcart API + MCP
- BigCommerce API + MCP vs Spree Commerce
- BigCommerce API + MCP vs Square
- BigCommerce API + MCP vs Swell
- BigCommerce API + MCP vs Wix Stores and eCommerce API
- BigCommerce API + MCP vs WooCommerce API + MCP
- Commerce Layer API + MCP vs Vendure
- commercetools vs Vendure
- Ecwid by Lightspeed vs Vendure
- Elastic Path API + MCP vs Vendure
- Medusa API + MCP vs Vendure
- Saleor API + MCP vs Vendure
- Shopify API + MCP vs Vendure
- Shopware vs Vendure
- Snipcart API + MCP vs Vendure
- Spree Commerce vs Vendure
- Square vs Vendure
- Swell vs Vendure
- Vendure vs Wix Stores and eCommerce API
- Vendure vs WooCommerce API + MCP
- BigCommerce API + MCP vs doola MCP
- doola MCP vs Vendure
- Fabric vs Vendure
Machine-readable
- This page as Markdown
/compare/bigcommerce-vs-vendure.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/bigcommerce.json·/api/v1/tools/vendure.json - From a terminal
anchor compare bigcommerce vendure(the CLI) - Over MCP
compare_tools {"a": "bigcommerce", "b": "vendure"}at/mcp, no key