{
  "fixes": {
    "slug": "ecwid",
    "name": "Ecwid by Lightspeed",
    "listing": "https://www.anchorterminal.com/tools/ecwid",
    "markdown": "# Fix list: Ecwid by Lightspeed\n\nFrom Anchor Terminal's listing at https://www.anchorterminal.com/tools/ecwid, the October 2026 research run, assessed 8 October 2026. Grade B, 63.2 out of 100.\n\nThis 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.\n\nFor a coding agent working on Ecwid by Lightspeed: 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.\n\n## 1. Payments \u0026 pricing, 15 out of 100, up to 10.6 more on the total\n\nWhy it scored 15: No x402, MPP or L402 (0). Plan prices are public, Starter $5, Venture $35, Business $65 and Unlimited $149 a month, with nothing per call (10). No free plan or trial was found on the pricing page, and the docs say only paid plans reach the API. Developers can email API support for a free upgrade of a test store, which earns part of the line (5). A person signs up in a browser and copies the token from the admin (0).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):\n\nThe published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).\n\n- 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.\n- 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.\n- 20, a free tier or trial that doesn't need a card.\n- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).\n\nPayment 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.\n\nOpen-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.\n\n## 2. Security \u0026 auth, 61 out of 100, up to 6.8 more on the total\n\nWhy it scored 61: 40 access scopes fixed per app, with tokens revoked by uninstalling the app. Tokens never expire and can't be rotated in place. Tokens in the query string were switched off in March 2025 (24). Scopes split read, update and create, and the public token reads only enabled catalogue data and places unpaid orders. No confirmation step for deletes (13). The API returns merchant and shopper text, and no prompt-injection guidance was found (5). No audit log or per-call log for API use was found in the developer docs. A deleted-items history endpoint exists (3). SOC 2 Type II and a PCI attestation listed for E-Series, a public bug bounty and yearly penetration tests per Lightspeed's security page. No security.txt was read (16).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-security):\n\n- 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.\n- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.\n- 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.\n- 0 to 15, audit logs or per-call visibility for the operator.\n- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.\n\nModels 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.\n\n## 3. Schema \u0026 documentation, 66 out of 100, up to 5.5 more on the total\n\nWhy it scored 66: OpenAPI 3.0.3 definitions are embedded in the reference for store profile, store logo, orders and order extra fields only, marked version 0.0.1. No complete downloadable spec was found (10). `llms.txt`, `llms-full.txt` and a Markdown twin of every page (10). Reference pages state what each call does and which scopes it needs, with little on when not to use one (12). Parameters are typed in tables, and the published OpenAPI fragments carry almost no enums or required markers (9). Request and response examples on reference pages and a page of named error codes by area (12). The version sits in the path as `/api/v3` and a dated changelog marks breaking changes, though it was silent from 30 April to 30 September 2026 (13).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):\n\nAPIs and MCP servers.\n\n- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).\n- 10, llms.txt or Markdown docs served for agents.\n- 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.\n- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.\n- 0 to 15, examples and documented error responses.\n- 15, versioning and a public changelog.\n\nModels 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.\n\n## 4. Agent ergonomics, 66 out of 100, up to 5.5 more on the total\n\nWhy it scored 66: `responseFields` cuts any response to named fields, including nested ones, and `limit` caps list size (20). Searches page with `offset` and `limit` up to 100 and take filters such as keyword, date ranges and status (18). A published list of named error codes with HTTP status, including scope and plan errors an agent can act on (15). No idempotency keys on REST writes were found. The only idempotency key in the docs belongs to app billing charges (2). A GET needs only the store ID and a token. The official TypeScript package covers GET calls only and the official Java and Kotlin client is on GitHub. No official Python client (11).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):\n\n- 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).\n- 20, pagination, filtering and output-size controls.\n- 20, actionable, documented error responses, codes and messages an agent can recover from.\n- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.\n- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.\n\nModels 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.\n\n## 5. Reliability, 80 out of 100, up to 4 more on the total\n\nWhy it scored 80: Graded as a hosted service, on the REST API. Atlassian Statuspage at status.ecwid.com with six components, API among them, and a full incident history (20). The incident feed shows one incident between 10 July and 8 October 2026, storefronts slowed for 48 minutes on 7 August, marked minor and not on the API component. We score that between clean and minor (25). 600 requests a minute per token is published (15). A 429 carries `Retry-After`, but no backoff guidance and no idempotency keys for REST writes were found (10). The Lightspeed Service Agreement disclaims any service level commitment (0). The REST API is generally available at `/api/v3` (10).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):\n\nHosted APIs, MCP servers, models and platforms.\n\n- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).\n- 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.\n- 15, rate limits documented with numbers.\n- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.\n- 10, an SLA published for any paid tier.\n- 10, the surface agents use is generally available, not beta or preview.\n\nLocal packages, SDKs, frameworks and stdio MCP servers.\n\n- 20, installs from an official package with supported runtimes stated.\n- 25, a public CI and test suite, passing on the default branch.\n- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).\n- 15, semver discipline and breaking changes called out in a changelog.\n- 15, version 1.0 or later, or declared stable.\n\nProtocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.\n\n## 6. Transparency \u0026 trust, 72 out of 100, up to 2.5 more on the total\n\nMade of editorial 56, provenance 87.\n\nWhy it scored 72: Closed service with a published service agreement, updated 26 February 2026, that names Ecwid, Inc. as the contracting entity for E-Series (15). Privacy policy effective 8 July 2026 and a public DPA, both written for the whole Lightspeed group. Retention is stated as for as long as reasonably needed, with no periods (18). No deprecation policy was found. The changelog marks breaking changes, and the March 2025 entry on query-string tokens announces a change already made (5). The sub-processor list, updated 30 September 2026, gives purpose, product line and country for each provider, with E-Series rows (18).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):\n\n- 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.\n- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).\n- 0 to 20, a deprecation policy or notices with dates.\n- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).\n\nThe other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.\n\nProvenance checks not met in full (half of this category, computed from checked facts):\n\n- Terms of service: read, states 7 of the 7 things a reader expects, and has 1 clause that costs points (8 of 10)\n- Privacy policy: read, states 7 of the 8 things a reader expects (9.3 of 10)\n- security.txt: could not be fetched (0 of 10)\n\n## 7. Maintenance \u0026 community, 79 out of 100, up to 1.8 more on the total\n\nWhy it scored 79: The API changelog's newest entry is 30 September 2026 (30). That is its only dated entry in 90 days, but the official `@lightspeed/ecom-headless` package had five npm releases since 10 July, 1.2.0 on 2 September and 1.2.1 on 1 October among them, so we count the line as met on SDK releases (20). Public changelog, API support that states a reply within 24 hours on business days, and a Slack community. Replies were not tested (10). Official TypeScript package current, Java and Kotlin client last committed 15 September 2026, no official Python, Ruby or PHP client (12). The Java client runs pull-request and push workflows on GitHub (7).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):\n\n- 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.\n- 20, at least three releases or dated changelog entries in the last 90 days.\n- 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.\n- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).\n- 10, package health, current dependencies and CI.\n\nModels are read for deprecation notice periods and model churn rather than release counts.\n\n## What we couldn't check\n\nWhat 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.\n\n- unchecked: which plans include API access. The docs say paid plans only, the pricing page does not list the API, and the help centre at support.ecwid.com answered with a bot check\n- unchecked: whether signing up for a store needs a card, and whether any trial exists beyond the test-store upgrade developers request by email\n- unchecked: security.txt. www.ecwid.com/.well-known/security.txt answered 403 and the lightspeedhq.com path 404\n- Lightspeed's API licence agreement does not name Ecwid or E-Series, so its application to the Ecwid API rests on the service agreement's API clause\n- No audit log, deprecation policy or MCP server was found in the developer docs. The store admin was not inspected\n- The lead described APIs for carts and checkout. The REST API reads abandoned carts and creates orders directly, and live cart and checkout calls exist only in the browser JavaScript API\n\n## Weaknesses\n\n- Access tokens never expire and change only when the app is uninstalled and installed again\n- No test mode. The docs advise a separate test store, and only stores on paid plans can call the API\n- No idempotency keys on REST writes found in the reviewed documentation\n- OpenAPI 3.0.3 definitions are published for store profile and orders only, with no complete downloadable spec found\n- The REST API has no endpoint that builds a live cart or runs checkout. Those sit in the browser JavaScript API\n- The service agreement disclaims any service level commitment\n\n## What costs an agent a turn today\n\nThe notes we give agents before they call it. Each one is a workaround an agent shouldn't need.\n\n- Send the token as `Authorization: Bearer` to `https://app.ecwid.com/api/v3/{storeId}`. Tokens in the query string stopped working in March 2025\n- Use the secret token server-side only. The public token reads enabled products and places orders that are not marked paid\n- Add `responseFields`, for example `total,items(id,name,price)`, to keep responses small, and page with `offset` and `limit` (maximum 100)\n- Stay under 600 requests a minute per token and wait the `Retry-After` seconds on a 429. Repeated calls with a bad token get the token and IP blocked for longer\n- Work in a separate test store. There is no test mode, and `POST /orders` writes a real order with no idempotency key\n- After changing an app's scopes, uninstall and reinstall it, then replace the stored tokens. The old ones stop working\n\n## When it's done\n\nSend 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.\n",
    "grade": "B",
    "score": 63.2,
    "assessed": "2026-10-08",
    "run": "October 2026 research run",
    "categories": [
      {
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "score": 15,
        "maxGain": 10.6,
        "reason": "No x402, MPP or L402 (0). Plan prices are public, Starter $5, Venture $35, Business $65 and Unlimited $149 a month, with nothing per call (10). No free plan or trial was found on the pricing page, and the docs say only paid plans reach the API. Developers can email API support for a free upgrade of a test store, which earns part of the line (5). A person signs up in a browser and copies the token from the admin (0).",
        "checklist": [
          "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.\n- 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.\n- 20, a free tier or trial that doesn't need a card.\n- 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."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-payments"
      },
      {
        "key": "security",
        "name": "Security \u0026 auth",
        "score": 61,
        "maxGain": 6.8,
        "reason": "40 access scopes fixed per app, with tokens revoked by uninstalling the app. Tokens never expire and can't be rotated in place. Tokens in the query string were switched off in March 2025 (24). Scopes split read, update and create, and the public token reads only enabled catalogue data and places unpaid orders. No confirmation step for deletes (13). The API returns merchant and shopper text, and no prompt-injection guidance was found (5). No audit log or per-call log for API use was found in the developer docs. A deleted-items history endpoint exists (3). SOC 2 Type II and a PCI attestation listed for E-Series, a public bug bounty and yearly penetration tests per Lightspeed's security page. No security.txt was read (16).",
        "checklist": [
          "- 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.\n- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.\n- 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.\n- 0 to 15, audit logs or per-call visibility for the operator.\n- 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."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-security"
      },
      {
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "score": 66,
        "maxGain": 5.5,
        "reason": "OpenAPI 3.0.3 definitions are embedded in the reference for store profile, store logo, orders and order extra fields only, marked version 0.0.1. No complete downloadable spec was found (10). `llms.txt`, `llms-full.txt` and a Markdown twin of every page (10). Reference pages state what each call does and which scopes it needs, with little on when not to use one (12). Parameters are typed in tables, and the published OpenAPI fragments carry almost no enums or required markers (9). Request and response examples on reference pages and a page of named error codes by area (12). The version sits in the path as `/api/v3` and a dated changelog marks breaking changes, though it was silent from 30 April to 30 September 2026 (13).",
        "checklist": [
          "APIs and MCP servers.",
          "- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).\n- 10, llms.txt or Markdown docs served for agents.\n- 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.\n- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.\n- 0 to 15, examples and documented error responses.\n- 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."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-schema"
      },
      {
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "score": 66,
        "maxGain": 5.5,
        "reason": "`responseFields` cuts any response to named fields, including nested ones, and `limit` caps list size (20). Searches page with `offset` and `limit` up to 100 and take filters such as keyword, date ranges and status (18). A published list of named error codes with HTTP status, including scope and plan errors an agent can act on (15). No idempotency keys on REST writes were found. The only idempotency key in the docs belongs to app billing charges (2). A GET needs only the store ID and a token. The official TypeScript package covers GET calls only and the official Java and Kotlin client is on GitHub. No official Python client (11).",
        "checklist": [
          "- 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).\n- 20, pagination, filtering and output-size controls.\n- 20, actionable, documented error responses, codes and messages an agent can recover from.\n- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.\n- 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."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-ergonomics"
      },
      {
        "key": "reliability",
        "name": "Reliability",
        "score": 80,
        "maxGain": 4,
        "reason": "Graded as a hosted service, on the REST API. Atlassian Statuspage at status.ecwid.com with six components, API among them, and a full incident history (20). The incident feed shows one incident between 10 July and 8 October 2026, storefronts slowed for 48 minutes on 7 August, marked minor and not on the API component. We score that between clean and minor (25). 600 requests a minute per token is published (15). A 429 carries `Retry-After`, but no backoff guidance and no idempotency keys for REST writes were found (10). The Lightspeed Service Agreement disclaims any service level commitment (0). The REST API is generally available at `/api/v3` (10).",
        "checklist": [
          "Hosted APIs, MCP servers, models and platforms.",
          "- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).\n- 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.\n- 15, rate limits documented with numbers.\n- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.\n- 10, an SLA published for any paid tier.\n- 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.\n- 25, a public CI and test suite, passing on the default branch.\n- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).\n- 15, semver discipline and breaking changes called out in a changelog.\n- 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."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-reliability"
      },
      {
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "score": 72,
        "maxGain": 2.5,
        "reason": "Closed service with a published service agreement, updated 26 February 2026, that names Ecwid, Inc. as the contracting entity for E-Series (15). Privacy policy effective 8 July 2026 and a public DPA, both written for the whole Lightspeed group. Retention is stated as for as long as reasonably needed, with no periods (18). No deprecation policy was found. The changelog marks breaking changes, and the March 2025 entry on query-string tokens announces a change already made (5). The sub-processor list, updated 30 September 2026, gives purpose, product line and country for each provider, with E-Series rows (18).",
        "blend": "editorial 56, provenance 87",
        "checklist": [
          "- 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.\n- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).\n- 0 to 20, a deprecation policy or notices with dates.\n- 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."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-transparency"
      },
      {
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "score": 79,
        "maxGain": 1.8,
        "reason": "The API changelog's newest entry is 30 September 2026 (30). That is its only dated entry in 90 days, but the official `@lightspeed/ecom-headless` package had five npm releases since 10 July, 1.2.0 on 2 September and 1.2.1 on 1 October among them, so we count the line as met on SDK releases (20). Public changelog, API support that states a reply within 24 hours on business days, and a Slack community. Replies were not tested (10). Official TypeScript package current, Java and Kotlin client last committed 15 September 2026, no official Python, Ruby or PHP client (12). The Java client runs pull-request and push workflows on GitHub (7).",
        "checklist": [
          "- 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.\n- 20, at least three releases or dated changelog entries in the last 90 days.\n- 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.\n- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).\n- 10, package health, current dependencies and CI.",
          "Models are read for deprecation notice periods and model churn rather than release counts."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-maintenance"
      }
    ],
    "provenance": [
      {
        "label": "Terms of service",
        "value": "read, states 7 of the 7 things a reader expects, and has 1 clause that costs points",
        "points": 8,
        "max": 10
      },
      {
        "label": "Privacy policy",
        "value": "read, states 7 of the 8 things a reader expects",
        "points": 9.3,
        "max": 10
      },
      {
        "label": "security.txt",
        "value": "could not be fetched",
        "points": 0,
        "max": 10
      }
    ],
    "unchecked": [
      "unchecked: which plans include API access. The docs say paid plans only, the pricing page does not list the API, and the help centre at support.ecwid.com answered with a bot check",
      "unchecked: whether signing up for a store needs a card, and whether any trial exists beyond the test-store upgrade developers request by email",
      "unchecked: security.txt. www.ecwid.com/.well-known/security.txt answered 403 and the lightspeedhq.com path 404",
      "Lightspeed's API licence agreement does not name Ecwid or E-Series, so its application to the Ecwid API rests on the service agreement's API clause",
      "No audit log, deprecation policy or MCP server was found in the developer docs. The store admin was not inspected",
      "The lead described APIs for carts and checkout. The REST API reads abandoned carts and creates orders directly, and live cart and checkout calls exist only in the browser JavaScript API"
    ],
    "weaknesses": [
      "Access tokens never expire and change only when the app is uninstalled and installed again",
      "No test mode. The docs advise a separate test store, and only stores on paid plans can call the API",
      "No idempotency keys on REST writes found in the reviewed documentation",
      "OpenAPI 3.0.3 definitions are published for store profile and orders only, with no complete downloadable spec found",
      "The REST API has no endpoint that builds a live cart or runs checkout. Those sit in the browser JavaScript API",
      "The service agreement disclaims any service level commitment"
    ],
    "agentNotes": [
      "Send the token as `Authorization: Bearer` to `https://app.ecwid.com/api/v3/{storeId}`. Tokens in the query string stopped working in March 2025",
      "Use the secret token server-side only. The public token reads enabled products and places orders that are not marked paid",
      "Add `responseFields`, for example `total,items(id,name,price)`, to keep responses small, and page with `offset` and `limit` (maximum 100)",
      "Stay under 600 requests a minute per token and wait the `Retry-After` seconds on a 429. Repeated calls with a bad token get the token and IP blocked for longer",
      "Work in a separate test store. There is no test mode, and `POST /orders` writes a real order with no idempotency key",
      "After changing an app's scopes, uninstall and reinstall it, then replace the stored tokens. The old ones stop working"
    ],
    "recheck": "https://www.anchorterminal.com/builders/#disputes"
  },
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-08",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  }
}