# Mews — API Agent Score

> Score: 84/100 (Grade: A) | Domain: mews.com | Rubric: 1.0.0 | Checked: September 18, 2026

Mews scored 84/100 (A), classified "ai-ready".

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

## Summary

- Overall: 84/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 96/100 (A+)
- Developer Experience: 63/100 (C)
- Agent Discovery: 96/100 (A+)
- Agent Understanding: 80/100 (A)
- Agent Usability: 81/100 (A)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — The API declares version "v1" and uses url-based versioning, so an agent can pin to a stable contract. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — authentication is documented on the docs site at https://docs.mews.com/connector-api/guidelines/authentication, even though it isn't declared in the API spec. Investigated: docs 100%, spec 50%.
- [warn] Schema coverage & depth — Operations take 0 parameters each on average and some use nested-object or request-body schemas, which are harder for an agent to fill correctly. Investigated: spec 83%, sdk 80%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 0%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 0%, docs 0%.

### Developer Experience

- [pass] Quickstart present — Quickstart at https://docs.mews.com/getting-started/getting-started has a runnable code sample in its plain-text .md variant (https://docs.mews.com/getting-started/getting-started.md). Investigated: docs 100%.
- [pass] Description completeness — Only 50% of operations and parameters have descriptions (0 of 56 ops, 0 of 0 params), leaving an agent to guess what most endpoints do. Investigated: spec 100%, sdk 61%.
- [pass] Changelog published — changelog is documented on the docs site at https://docs.mews.com/connector-api/changelog/changelog2025, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.
- [fail] Self-service developer portal — The signup page is sales-gated (contact-sales / request-access language detected), so an agent can't self-serve. Investigated: docs 0%.
- [fail] Code samples in docs — No code samples detected across 20 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [warn] llms.txt present, valid & comprehensive — llms.txt contains parseable links but doesn't fully follow the proposed structure: https://docs.mews.com/llms.txt: No blockquote summary found. Investigated: docs 94%, sdk 0%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/mews, 2930 snippets). Investigated: docs 100%, cli 100%, sdk 83%.
- [warn] Crawlable / AEO — Sitemap has 7 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No error responses (4xx/5xx or a catch-all default) are documented anywhere in the spec, so an agent can't anticipate or handle failures. Investigated: docs 100%, spec 50%, sdk 0%.
- [pass] Operation purpose clarity — Read/write classification is partial: 5/5 classified (3 read, 2 write). Investigated: sdk 100%, spec 33%.
- [warn] Agent-navigable, token-efficient docs — 4 of 50 pages have substantive content differences between markdown and HTML (avg 8% missing). Investigated: docs 75%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, sdk) is 10% (threshold 35% for full credit).
- [fail] Docs structured data — No JSON-LD or OpenGraph/meta tags found across 2 assessed pages (2 JS-rendered), so answer engines have nothing to cite. Investigated: docs 0%.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Pagination documented & consistent — 1/1 list method(s) return an auto-paginating iterable. Investigated: sdk 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 0%.
- [fail] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 0%, docs 0%.

## Executive Summary

Mews's API program demonstrates strong discoverability and schema design, giving partners a solid structural foundation to build on. The two areas most likely to slow partner adoption are developer onboarding — where a sales-gated signup and the complete absence of code samples create friction before a partner writes a single line of integration code — and agent-readiness of documentation, where missing structured metadata means AI answer engines cannot cite or surface Mews APIs to the agents partners increasingly rely on. Prioritizing these two gaps will convert the program from a well-architected but hard-to-access API into one where partners and their agents can evaluate, onboard, and integrate without a sales conversation.