Is Ecwid agent-ready?

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

Does Ecwid publish an OpenAPI spec?

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

What is Ecwid's Headless Index score?

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

03 / Scorecard / Commerce

Ecwid

Headless Index

51/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Ecwid earns Band C in the Commerce category of The Headless Index, with a thesis-fit score of 51/100. Its strongest dimension is webhooks and events (15/20); its weakest scored dimension is MCP and agent posture (4/20). No public OpenAPI specification was found when Ecwid was scored, which limits how far an agent can go without human integration work.

Editorial verdict

Ecwid is partially headless and partly UI-led. The Headless Index thesis-fit score of 51/100 puts it mid-table on 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 are partly machine-consumable: the core flows are reachable through code but several adjacent surfaces still expect a human at a dashboard, and the rest of this verdict explains where Ecwid lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. The REST v3 API is competent and old-fashioned: store-scoped paths under app.ecwid.com/api/v3/{storeId}, OAuth tokens per installed app, batch endpoints for bulk work. Client libraries are uneven. The Kotlin client is maintained (github.com/Ecwid/ecwid-java-api-client), while the JavaScript package has not been touched since 2023 and draws roughly ten weekly installs on npm (@ecwid/sdk). An agent can drive parts of this product, but not all of it: integrators should plan for human-in-the-loop checkpoints where the headless surface stops short. On headless operability: Products, categories, orders, customers and coupons are all reachable over the API, so the merchandising core is scriptable. Everything around it is not: there is no CLI, no Terraform provider, no configuration export, and storefront design, payment setup and shipping profiles are done in the control panel. Ecwid stayed a hosted store with an API attached (api-docs.ecwid.com).^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: None. A search across the organisation returns nothing (org:Ecwid mcp, zero results), the registry has no entry, and the docs carry no agent guidance. Lightspeed, which owns Ecwid, has not pushed one either. For a product whose main appeal is being embeddable everywhere, sitting out the agent-tooling shift is a strategic miss rather than a technical one.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Easily Ecwid's best surface. The catalogue is explicit and covers order.created, order.updated, order.deleted, product.created, category.updated, customer.created, unfinished_order.updated and application.installed. Payloads are signed with HMAC-SHA256 and delivered in a dedicated header (X-Ecwid-Webhook-Signature), and the retry policy is written down. Small payloads that carry only an entity id force a follow-up fetch, which is a fair trade. Net assessment: integrators can build agent flows against Ecwid, but the rough edge to plan around is MCP posture^[3]. Expect to wrap missing pieces in bespoke glue or accept human-in-the-loop checkpoints. Workable but requires scaffolding.

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 intent13/20

scored

The REST v3 API is competent and old-fashioned: store-scoped paths under app.ecwid.com/api/v3/{storeId}, OAuth tokens per installed app, batch endpoints for bulk work. Client libraries are uneven. The Kotlin client is maintained (github.com/Ecwid/ecwid-java-api-client), while the JavaScript package has not been touched since 2023 and draws roughly ten weekly installs on npm (@ecwid/sdk).

signals (6)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 0 probe paths
·GraphQL endpointDiscovered at https://www.ecwid.com/graphql, introspection disabled or scoped
+SDKs maintained5 (java, javascript, kotlin); top by stars: Ecwid/consul-api (421 stars)
+SDK recency3 of 5 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-14)
·npm weekly downloads10 across published packages; top: @ecwid/sdk @ 10/week

cite (1)

github.sdks@2026-08-19

Headless operation11/20

scored

Products, categories, orders, customers and coupons are all reachable over the API, so the merchandising core is scriptable. Everything around it is not: there is no CLI, no Terraform provider, no configuration export, and storefront design, payment setup and shipping profiles are done in the control panel. Ecwid stayed a hosted store with an API attached (api-docs.ecwid.com).

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 posture4/20

scored

None. A search across the organisation returns nothing (org:Ecwid mcp, zero results), the registry has no entry, and the docs carry no agent guidance. Lightspeed, which owns Ecwid, has not pushed one either. For a product whose main appeal is being embeddable everywhere, sitting out the agent-tooling shift is a strategic miss rather than a technical one.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−Official MCP serverNone found in vendor's GitHub org or the official MCP registry
−Community MCP serversNone found
+Agent-friendly SDKs1 TS/JS SDKs available; top: @ecwid/sdk (10/week downloads)

cite (1)

ai_review_browser.pages_fetched@2026-08-19

Schema observability8/20

scored

No machine-readable contract is published. The documentation source is open, written as Slate markdown in a public repository (github.com/Ecwid/ecwid-api-docs), which is better than a closed portal but is still prose an agent must parse. There is no OpenAPI file, no JSON Schema for resources, and no introspection endpoint. Client generation means reading pages.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 0 standard probe paths
·GraphQL introspectionGraphQL endpoint at https://www.ecwid.com/graphql but introspection is disabled, scoped, or behind authentication

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events15/20

scored

Easily Ecwid's best surface. The catalogue is explicit and covers order.created, order.updated, order.deleted, product.created, category.updated, customer.created, unfinished_order.updated and application.installed. Payloads are signed with HMAC-SHA256 and delivered in a dedicated header (X-Ecwid-Webhook-Signature), and the retry policy is written down. Small payloads that carry only an entity id force a follow-up fetch, which is a fair trade.

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:C band: scores 40-75 range

04 / Embed

Show Ecwid'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

Tiendanube / NuvemshopC

Headless Index 51/100

ShopwareC

Headless Index 50/100

WooCommerceC

Headless Index 52/100

See full Commerce ranking →

FAQ

Ecwid and agent readiness

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