Wix Stores and eCommerce API

# Fix list: Wix Stores and eCommerce API

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/wix, the October 2026 research run, assessed 8 October 2026. Grade C, 61.4 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Wix Stores and eCommerce API: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Reliability, 48 out of 100, up to 10.4 more on the total

Why it scored 48: Atlassian Statuspage at status.wix.com with 119 components, Stores and Payments among them, and an incident feed (20). From 10 July to 8 October 2026 the feed holds 10 incidents. Three are marked critical: 1 August, 3 hours 17 minutes across nearly every component including Store Management, Checkout and APIs, 24 July, 47 minutes on sign-in, site loading and checkout, and 15 September, 42 minutes in Europe, with a postmortem. Three marked major lasted 12 to 26 minutes, the latest on 1 October on Store Management, Storefront and Checkout. One outage over an hour plus two shorter critical ones (7). No numeric limit for REST calls was found. The docs publish per-minute quotas only for site data requests and tell callers to space some writes one second apart (3). The 429 guidance is to wait a minute and retry, updates are guarded by revision numbers that return 409, and idempotency keys exist on a few methods only (8). The trust centre FAQ states a service level objective and a 99.99 per cent figure for 2021, with no SLA found (0). The REST APIs are released, and Cart V2 shipped on 5 August 2026 without a preview label (10).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 2. Payments & pricing, 30 out of 100, up to 8.8 more on the total

Why it scored 30: No x402, MPP or L402 found (0). Plan prices are public on wix.com/plans but shown in the reader's currency, with nothing per call (10). A free plan, marked no credit card required, with eCommerce on Core and above (20). A person signs up in a browser and creates the API key in the API Keys Manager (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 3. Security & auth, 61 out of 100, up to 6.8 more on the total

Why it scored 61: API keys carry permission scopes and a list of sites they may target, and stay valid until revoked or rotated in the dashboard. App tokens come from OAuth client credentials and last 4 hours. The MCP uses OAuth with dynamic client registration, advertises only `offline_access` as a scope and still accepts the `plain` PKCE method (26). Read and admin scopes are separate (`SCOPE.STORES.PRODUCT_READ` and `SCOPE.STORES.PRODUCT_READ_ADMIN`), but no read-only mode or confirmation step for the MCP was found (11). The API returns merchant and customer content, and no prompt-injection guidance was found. The `@wix/mcp` package limits call URLs to five Wix hostnames (4). No audit log or per-call log for API keys was found in the developer docs. Responses carry `x-wix-request-id` (2). The security page lists SOC 2 Type 2, PCI DSS Level 1 and several ISO certificates and a bug bounty at bugbounty@wix.com. `/security.txt` has a contact but no Expires field, and `/.well-known/security.txt` returns 404 (18).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 4. Agent ergonomics, 68 out of 100, up to 5.2 more on the total

Why it scored 68: The MCP lists 18 tools, all on by default, with no toolsets or read-only subset documented. Most calls need a docs lookup first, and the Query Products page alone is 327 KB of Markdown (15). Cursor and offset paging, a query language with filters and sorting, and a `fields` parameter for projection. Query Products returns at most 100 a page (18). Errors use one format with application codes and per-field violations, though system errors are empty by design (16). Revision numbers guard updates, idempotency keys cover a few methods, and the `@wix/mcp` package sets annotations, with `destructiveHint` true on `CallWixSiteAPI` (12). Every site call needs a site ID header, and the only official SDK is JavaScript (7).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 5. Schema & documentation, 76 out of 100, up to 3.9 more on the total

Why it scored 76: No public OpenAPI file was found. The contract is the Markdown reference, which the MCP tools `ReadFullDocsMethodSchema` and `SearchWixAPISpec` also serve, and the MCP tools have typed inputs (12). `llms.txt`, `llms-full.txt` and a `.md` twin of every docs page (10). Method pages state purpose and limits, for example that Query Products supports a narrow set of filters and that Search Products is the route for name lookups (15). REST fields carry types, enums and minimum and maximum values, but the MCP's `CallWixSiteAPI` takes a free-form URL, method and body (11). Each method page has a curl example and a list of HTTP and application error codes, and a general errors article documents the error format (13). Versions are per module, and dev.wix.com/changelog is dated (15).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 6. Transparency & trust, 77 out of 100, up to 2 more on the total

Made of editorial 69, provenance 84.

Why it scored 77: Closed platform under the Wix Terms of Use. `@wix/sdk` and `@wix/stores` are MIT and wix/skills is MIT (15). Privacy policy effective 18 June 2026 and a data processing addendum effective 1 December 2025. Retention is stated as the time reasonably necessary, with no fixed periods found (20). The versioning article says deprecated APIs are marked, logged in the changelog and not removed, and Developer Preview lasts at most 6 months (16). A sub-processor list names Wix entities and third parties with locations, and the security page names AWS, Google Cloud and Equinix as hosts (18).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Terms of service: published, but our reader couldn't read it (7 of 10)
- Privacy policy: published, but our reader couldn't read it (7 of 10)
- security.txt: not found (0 of 10)

## 7. Maintenance & community, 83 out of 100, up to 1.5 more on the total

Why it scored 83: Changelog entries on 8 October 2026, and `@wix/mcp` 1.0.92 published the same day (30). 101 dated changelog entries between 6 July and 8 October 2026 (20). Public changelog, a support site, and the public wix/skills repository with commits on 8 October 2026 (12). The MCP server is in the official registry as `com.wix/mcp`, version 1.0.2 of 22 December 2025, and `@wix/sdk` 1.21.17 is current (15). `@wix/mcp` had 30 releases in 90 days. The server's source and CI are not public, and the package states no licence (6).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- unchecked: US dollar plan prices. wix.com/plans served rupee prices to our reader (Light 250, Core 500, Business 900 and Business Elite 1,800 rupees a month before a 50 per cent offer). A request with `currency=USD` returned unfilled markup showing 17, 29, 39 and 159, which we did not treat as confirmed.
- unchecked: the live MCP tool list and schemas. `mcp.wix.com/mcp` answers 401 without a token, so the 18 tools are from the docs and the annotations from the `@wix/mcp` 1.0.92 package.
- unchecked: GitHub stars, and the full text of the terms of use and privacy policy, whose collapsed sections were not in the HTML we received.
- No numeric REST rate limit, no OpenAPI file, no SLA and no API audit log were found in the reviewed documentation.
- Whether a free site can call the Stores APIs before a paid plan is bought was not established.
- The `@wix/mcp` package builds tool text with a block of instructions addressed to the model, telling it to call `WixREADME` first. Recorded as a fact, with no deduction.
- The lead's docs URL still resolves, but the MCP article now lives under dev.wix.com/docs/api-reference/articles/ai-tools/wix-mcp. The MCP has no Stores tools of its own. It reaches Stores through the general `CallWixSiteAPI` and `ExecuteWixAPI` tools.
- Wix WebMCP, for agents in a visitor's browser, was announced in the changelog on 8 October 2026 and is not graded here.

## Weaknesses

- No numeric rate limit for the REST API was found in the reviewed documentation. The 429 guidance is to wait a minute and retry
- No public OpenAPI file was found. Schemas are read from the Markdown reference or through the MCP schema tools
- status.wix.com shows 10 incidents from 10 July to 8 October 2026, three marked critical, the longest 3 hours 17 minutes on 1 August
- The MCP's `CallWixSiteAPI` takes a free-form URL, method and body, and no read-only mode or confirmation step is documented
- The only official SDK is JavaScript, and plan prices on wix.com/plans are shown in the reader's local currency

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Send the API key in `Authorization` with `wix-site-id` for site calls or `wix-account-id` for account calls, never both
- Fetch the product first and pass `product.revision` on every Catalogue V3 update, or the call fails with 409
- Use Cart V2 for new work. The older eCommerce Cart and Checkout APIs were deprecated on 5 August 2026
- Request `cursorPaging.limit` of at most 100 on Query Products and use Search Products for lookups by name
- Over MCP, read the method page with `ReadFullDocsArticle` before `CallWixSiteAPI`. Responses are cut at 50,000 characters by default

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.