# Walgreens — API Agent Score

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

Walgreens scored 53/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 68/100 (C)
- Developer Experience: 52/100 (D)
- Agent Discovery: 64/100 (C)
- Agent Understanding: 53/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Security & governance hygiene — security.txt valid at https://walgreens.com/.well-known/security.txt (Contact + unexpired Expires). Investigated: wellknown 100%.
- [fail] Example coverage — No detectable code samples across 9 sampled docs pages. Investigated: docs 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Schema coverage & depth — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.walgreens.com/register/pharmacyRegistration; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 9 sampled docs pages. Investigated: docs 0%.
- [fail] Changelog published — Official SDKs stale: newest activity 4242 days ago. Investigated: sdk 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/11 pages return markdown). Investigated: docs 70%.
- [warn] Registry & SDK presence — Discovered SDKs in only 1 language(s); target ≥3. Investigated: sdk 50%, docs 0%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.walgreens.com/llms.txt, https://developer.walgreens.com/docs/llms.txt). Investigated: docs 33%.
- [warn] Crawlable / AEO — Sitemap present (11 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/11 tested). Investigated: docs 64%.
- [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 2 assessed pages (2 JS-rendered). Investigated: docs 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — 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

- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [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.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Walgreens' API program shows solid discoverability foundations but has critical gaps that block partners and their AI agents from getting to a first successful call quickly. The weakest areas are agent usability — there are no runnable collections or test scripts for agents to build against — and agent understanding, where missing structured context files and docs metadata leave AI agents guessing at how to use the APIs correctly. Prioritizing runnable, executable API context alongside richer onboarding materials and agent-readable documentation will unlock self-serve partner activation and reduce integration friction significantly.