# Walmart — API Agent Score

> Score: 58/100 (Grade: D) | Domain: walmart.com | Rubric: 1.0.0 | Checked: July 24, 2026

Walmart scored 58/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 58/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 67/100 (C)
- Developer Experience: 64/100 (C)
- Agent Discovery: 62/100 (C)
- Agent Understanding: 57/100 (D)
- Agent Usability: 48/100 (F)

## Check Results

### API Design

- [warn] Schema coverage & depth — Medium parameter complexity (avg 6.4 params/op; nested/body schemas present). Investigated: spec 83%, sdk 0%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.
- [warn] Machine-readable, versioned contract — No info.version and no versioning scheme detected. Investigated: spec 50%, docs 0%.
- [pass] Example coverage — 55% example coverage (target 80%+). Investigated: spec 100%, sdk 0%.
- [fail] Auth declared & discoverable — No securitySchemes declared. Investigated: spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.walmart.com/blocked?url=L3NpZ251cA==&uuid=2436805c-8739-11f1-8b65-7ce8f1beb345&vid=&g=b; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 100% of operations + parameters have substantive descriptions. Investigated: spec 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%.
- [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/developer_walmart, 19870 snippets). Investigated: docs 100%, sdk 50%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.walmart.com/llms.txt, https://developer.walmart.com/docs/llms.txt). Investigated: docs 33%.
- [warn] Docs reachable, not hard auth-gated — 1 of 50 sampled pages return 200 for non-existent URLs (soft 404). Investigated: docs 25%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 2 of 49 pages have substantive content differences between markdown and HTML (avg 2% missing). Investigated: docs 60%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, sdk) is 5% (threshold 35% for full credit).
- [fail] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: spec 0%, docs 0%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Docs structured data — No surface produced evidence for this capability in this run.

### Agent Usability

- [pass] Sandbox separation — Sandbox server declared but no distinguishable test credentials in scheme descriptions. Investigated: spec 100%, docs 100%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: 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%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Walmart's API program shows strength in its underlying contract and schema quality, but two areas critically undermine partner and agent success: agents cannot reliably understand, execute, or recover from errors in your APIs, and partners lack the operational guardrails needed to build production-grade integrations with confidence. The most urgent priorities are closing the agent-readability and error-signaling gaps — without these, both human partners and their AI agents will stall, misintegrate, or churn before they ship. Fixing runnable truth and change communication will unlock sustained partner expansion and reduce integration support burden.