# Medusa — API Agent Score

> Score: 80/100 (Grade: A) | Domain: medusajs.com | Rubric: 1.0.0 | Checked: July 24, 2026

Medusa scored 80/100 (A), classified "ai-ready".

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

## Summary

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

## Category Scores

- API Design: 94/100 (A+)
- Developer Experience: 79/100 (B)
- Agent Discovery: 89/100 (A)
- Agent Understanding: 76/100 (B)
- Agent Usability: 67/100 (C)

## Check Results

### API Design

- [pass] Schema coverage & depth — package.json "types" → dist/index.d.ts. Investigated: sdk 100%, spec 42%.
- [pass] Auth declared & discoverable — authentication documented in the docs site at https://medusajs.com/api-keys-module/. Investigated: spec 100%, docs 100%.
- [warn] Machine-readable, versioned contract — info.version="2.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — 56% example coverage (target 80%+). Investigated: spec 100%, docs 100%, sdk 50%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://medusajs.com/contact/; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 1/1 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [pass] Description completeness — 83% description completeness (target 90%+). Investigated: spec 100%.
- [pass] Changelog published — changelog documented in the docs site at https://medusajs.com/changelog/. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — llms-full.txt reachable at https://docs.medusajs.com/llms-full.txt. Investigated: docs 100%, sdk 0%.
- [pass] Registry & SDK presence — Indexed on Context7 (rpuls/medusajs-2.0-for-railway-boilerplate, 104 snippets). Investigated: docs 100%, cli 100%, mcp 100%, sdk 17%, wellknown 0%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 25%.
- [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) — 6 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 11% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.

### Agent Usability

- [pass] Idempotency documented — idempotency documented in the docs site at https://medusajs.com/blog/idempotency-nodejs-express-open-source/. Investigated: spec 100%, docs 100%, sdk 0%.
- [pass] Pagination documented & consistent — Pagination params detected on 1 list endpoint(s). Investigated: spec 100%, docs 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Medusajs has a strong, machine-readable API contract and good overall discoverability — a solid foundation for a partner program. However, the two areas that most directly determine whether partners and their AI agents can successfully self-serve are significantly underdeveloped: docs lack the structured, agent-parseable formats and instruction files that modern coding agents require, and there are no runnable, test-backed collections to give agents or partners a verified path to a working integration. Prioritize making your documentation agent-readable first, then back it with executable, validated examples so partners can go from discovery to production without friction.