# Ecwid — API Agent Score

> Score: 79/100 (Grade: B) | Domain: ecwid.com | Rubric: 1.0.0 | Checked: August 31, 2026

Ecwid scored 79/100 (B), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/ecwid)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 79/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 72/100 (B)
- Developer Experience: 78/100 (B)
- Agent Discovery: 60/100 (C)
- Agent Understanding: 84/100 (A)
- Agent Usability: 100/100 (A+)

## Check Results

### API Design

- [warn] Schema coverage & depth — 0/20 (0%) enum-like params are realized as constrained types (not bare strings). Investigated: sdk 85%.
- [warn] Machine-readable, versioned contract — `--help --format json` exits 0 but output is not JSON. Investigated: cli 75%.
- [pass] Security & governance hygiene — Code is formatter-clean with zero linter errors and zero style warnings. Investigated: sdk 100%, wellknown 0%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, cli 100%.
- [fail] Auth declared & discoverable — no auth/config hint in --help. Investigated: cli 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page found at https://www.ecwid.com/, but no free tier or sandbox is documented in docs/pricing, so an agent may hit a paywall. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 7 day(s) ago. Investigated: sdk 100%.
- [warn] Description completeness — 495/502 operations lack a description. Investigated: sdk 1%.
- [skip] Quickstart present — No surface produced evidence for this capability in this run.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/ecwid, 4722 snippets). Investigated: docs 100%, sdk 67%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Crawlable / AEO — Sitemap has 5 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms-full.txt was found at any candidate origin, so agents can't grab your full docs in one fetch. Investigated: docs 0%, sdk 0%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "NotDataClass" with 7 subclasses. Investigated: sdk 100%, cli 0%.
- [warn] Operation purpose clarity — Read/write classification is mostly ambiguous: only 226/502 operations classified. Investigated: sdk 73%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, cli 0%, wellknown 0%.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Docs structured data — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, cli 0%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Ecwid's API program shows meaningful strengths in agent understanding and operation semantics, giving AI agents a solid foundation to work with once they're connected. However, two areas demand immediate attention: agents and partners cannot discover your documentation automatically — there is no machine-readable entry point for AI agents to fetch your full API surface in a single request — and your CLI gives no indication of how to authenticate, forcing partners to hunt for auth instructions before writing a single line of code. Closing these two gaps will materially shorten the time partners and their agents spend finding and connecting to your APIs, and remove the most common friction points before they become support escalations.