# Lulu — API Agent Score

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

Lulu scored 73/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 97/100 (A+)
- Developer Experience: 65/100 (C)
- Agent Discovery: 61/100 (C)
- Agent Understanding: 70/100 (B)
- Agent Usability: 74/100 (B)

## Check Results

### API Design

- [pass] Schema coverage & depth — 16/16 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%, spec 67%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: docs 100%, spec 50%, wellknown 0%.
- [warn] Machine-readable, versioned contract — info.version="v1" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 88%, docs 75%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.
- [pass] Example coverage — 67% example coverage (target 80%+). Investigated: spec 100%, sdk 100%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://api.lulu.com/auth/realms/glasstree/protocol/openid-connect/registrations?client_id=project-wizard&redirect_uri=https://www.lulu.com/&response_type=code&scope=openid; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Description completeness — 91% of operations + parameters have substantive descriptions. Investigated: spec 100%, sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://developers.lulu.com/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [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%, sdk 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (objective-see/lulu, 18 snippets). Investigated: docs 100%, sdk 100%, 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] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developers.lulu.com/llms.txt, https://developers.lulu.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Only 3 distinct 4xx/5xx codes documented (plus 0 "default" catch-all responses). Investigated: docs 100%, sdk 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 (root detected); agents using HTTP fetches will see no content. Investigated: docs 43%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 1% (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%.

### 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 params detected on 4 list endpoint(s). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — Sandbox server declared but no distinguishable test credentials in scheme descriptions. Investigated: spec 100%, docs 100%, sdk 100%.
- [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

Lulu's API program has a strong, machine-readable contract as its foundation — a real asset for partners and the agents they use to build integrations. However, two areas are holding back partner activation: agents and developers cannot reliably find or understand the API surface without a structured discovery layer (no llms.txt, no agent instructions, no structured docs metadata), and partners lack the runnable, versioned context — changelog, code samples, test collections — needed to integrate confidently and keep pace with changes. Prioritizing discoverability and executable onboarding will unlock self-serve partner growth and reduce integration support burden.