# The Kroger Co. — API Agent Score

> Score: 73/100 (Grade: B) | Domain: kroger.com | Rubric: 1.0.0 | Checked: July 24, 2026

The Kroger Co. scored 73/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 94/100 (A+)
- Developer Experience: 49/100 (F)
- Agent Discovery: 69/100 (C)
- Agent Understanding: 74/100 (B)
- Agent Usability: 78/100 (B)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: docs 100%, spec 83%, wellknown 0%.
- [warn] Schema coverage & depth — 34/35 (97%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 99%, spec 67%.
- [warn] Machine-readable, versioned contract — info.version="1.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 — 100% example coverage across params + responses. Investigated: spec 100%, sdk 100%, docs 0%.

### Developer Experience

- [pass] Description completeness — 19/19 operations carry a description. Investigated: sdk 100%, spec 17%.
- [warn] Quickstart present — Quickstart page reachable (6 variants scanned starting at https://developer.kroger.com/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/developer_kroger, 145 snippets). Investigated: docs 100%, sdk 67%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — 1 of 1 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.kroger.com/llms.txt, https://developer.kroger.com/docs/llms.txt). Investigated: docs 33%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (0 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. 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] Agent-navigable, token-efficient docs — 1 of 1 pages appear to be client-side rendered SPA shells (___gatsby detected); agents using HTTP fetches will see no content. Investigated: docs 71%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, sdk) is 2% (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 sampled pages — likely a CSR-only docs site. 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 — pagination documented in the docs site at https://developer.kroger.com/pagination. Investigated: docs 100%, spec 50%, sdk 50%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.

## Executive Summary

Kroger's API program shows strong API design fundamentals — the contract is machine-readable and well-typed, giving partners a solid foundation to build on. However, two areas are dragging down partner outcomes: partners have no self-serve path to get hands-on quickly (no portal, no code samples, no changelog), and AI agents cannot reliably discover, parse, or act on the API without manual guidance (missing agent instructions, structured data, and rate-limit signals). Prioritizing self-serve onboarding infrastructure first, then agent-readiness signals, will unblock both human partners and the AI-powered workflows they increasingly depend on.