Wix scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is MCP and agent posture; its weakest is schema observability.

Does Wix publish an OpenAPI spec?

No published OpenAPI specification was found when Wix was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.

What is Wix's Headless Index score?

Wix scores 68/100 on the Headless Index thesis-fit rubric and sits in Band B in the Commerce category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Commerce

Wix

Headless Index

68/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Wix earns Band B in the Commerce category of The Headless Index, with a thesis-fit score of 68/100. Its strongest dimension is MCP and agent posture (17/20); its weakest scored dimension is schema observability (8/20). No public OpenAPI specification was found when Wix was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Wix is solidly built for programmatic consumption. The Headless Index thesis-fit score of 68/100 lands it in the upper-middle of the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where Wix lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Wix runs a very large REST estate on www.wixapis.com with proto-derived service naming (wix.ecom.v1, wix.contacts.v5.Contacts), wrapped by a modular JavaScript SDK where each domain is its own package (@wix/sdk, @wix/ecom, @wix/stores). The tooling is real and versioned. The framing is not: this API sits beneath a site builder, and the builder is still the product. An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: Wix Headless makes catalogue, cart, checkout and bookings fully programmable, and the CLI plus templates give a real code path (@wix/cli, github.com/wix/headless-templates). Site structure, page design and theme remain editor-only by construction, which is fine for a headless deployment and blocking for anyone trying to automate a hosted Wix site end to end.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: The best MCP posture in this batch by a wide margin. Wix runs a hosted remote server over HTTP (https://mcp.wix.com/mcp), documented in its own repository (github.com/wix/wix-mcp) and in the SDK docs with sample prompts. It searches Wix documentation, generates platform code and makes authenticated API calls against real sites. Registry distribution is the only thing missing.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Every service namespace carries its own events, named in the same proto style as the APIs (wix.ecom.v1 order events, wix.contacts.v5.Contacts), and subscriptions are configured per app rather than per site. Payloads arrive signed and must be verified before use. The catalogue is broad but scattered across service pages, with no single machine-readable index of event types. Net assessment: Wix can be operated by agents for the majority of practical workflows. The closest thing to a gap is schema observability^[3], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent16/20

scored

Wix runs a very large REST estate on www.wixapis.com with proto-derived service naming (wix.ecom.v1, wix.contacts.v5.Contacts), wrapped by a modular JavaScript SDK where each domain is its own package (@wix/sdk, @wix/ecom, @wix/stores). The tooling is real and versioned. The framing is not: this API sits beneath a site builder, and the builder is still the product.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 34 probe paths
−GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
−SDKs maintainedNone detected in vendor org

cite (1)

github.sdks@2026-08-19

Headless operation14/20

scored

Wix Headless makes catalogue, cart, checkout and bookings fully programmable, and the CLI plus templates give a real code path (@wix/cli, github.com/wix/headless-templates). Site structure, page design and theme remain editor-only by construction, which is fine for a headless deployment and blocking for anyone trying to automate a hosted Wix site end to end.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
−API operations exposedNo OpenAPI spec; operations count unknown
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

ai_review_browser.topics_found@2026-08-19

MCP & agent posture17/20

scored

The best MCP posture in this batch by a wide margin. Wix runs a hosted remote server over HTTP (https://mcp.wix.com/mcp), documented in its own repository (github.com/wix/wix-mcp) and in the SDK docs with sample prompts. It searches Wix documentation, generates platform code and makes authenticated API calls against real sites. Registry distribution is the only thing missing.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+Official MCP serverhttps://github.com/wix/wix-mcp (16 stars, last commit 28 days ago)
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability8/20

scored

This is the hole. Wix documents hundreds of services, but dev.wix.com renders its reference client-side and publishes no fetchable OpenAPI or proto descriptor; a plain curl of the webhooks page returns almost no readable content. An agent cannot build a client cold. It has to read the SDK typings from npm (@wix/ecom) and infer the wire format.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 34 standard probe paths
−GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)

cite (1)

ai_review_browser.pages_fetched@2026-08-19

Webhooks & events13/20

scored

Every service namespace carries its own events, named in the same proto style as the APIs (wix.ecom.v1 order events, wix.contacts.v5.Contacts), and subscriptions are configured per app rather than per site. Payloads arrive signed and must be verified before use. The catalogue is broad but scattered across service pages, with no single machine-readable index of event types.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

ai_review_browser.pages_fetched@2026-08-19

JAIRF · 6 dimensions

JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Band rationale:B band: JAIRF=N/A HeadlessIndex=68

04 / Embed

Show Wix's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Peers in Commerce

MedusaB

Headless Index 70/100

VTEXB

Headless Index 65/100

BigCommerceB

Headless Index 74/100

See full Commerce ranking →

FAQ

Wix and agent readiness

Is Wix agent-ready?: Wix scores Band B on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is MCP and agent posture; its weakest is schema observability.
Does Wix publish an OpenAPI spec?: No published OpenAPI specification was found when Wix was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Wix's Headless Index score?: Wix scores 68/100 on the Headless Index thesis-fit rubric and sits in Band B in the Commerce category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.