# Progressive — API Agent Score

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

Progressive scored 57/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 65/100 (C)
- Developer Experience: 43/100 (F)
- Agent Discovery: 57/100 (D)
- Agent Understanding: 75/100 (B)
- Agent Usability: 48/100 (F)

## Check Results

### API Design

- [warn] Machine-readable, versioned contract — info.version="1.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%.
- [warn] Schema coverage & depth — Only 0% of operations have documented schemas. Investigated: spec 50%, sdk 50%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Auth declared & discoverable — securitySchemes declared but never applied. Investigated: spec 0%, docs 0%.

### Developer Experience

- [pass] Description completeness — 100% of operations + parameters have substantive descriptions. Investigated: spec 100%, sdk 77%.
- [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] 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 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

- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/29 pages return markdown). Investigated: docs 75%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.
- [warn] Registry & SDK presence — No official SDKs discovered via npm, PyPI, or GitHub. Investigated: sdk 33%, docs 0%, cli 0%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.progressive.com/s/llms.txt, https://developer.progressive.com/llms.txt, https://developer.progressive.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "ProgressiveException" with 4 subclasses. Investigated: sdk 100%, spec 0%, docs 0%.
- [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 — No pages support .md URLs (0/29 tested). Investigated: docs 71%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 5% (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] Sandbox separation — sandbox documented in the docs site at https://developer.progressive.com/s/test. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 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

Progressive's API program shows strength in core API design fundamentals, but two areas critically undermine partner success: developer onboarding and agent readiness. Partners currently have no self-service path to a first working call — no portal, no quickstart, no code samples — and AI agents cannot find, parse, or reliably act on your APIs without guessing. Prioritize building a self-service onboarding experience with runnable examples first, then close the agent discoverability and reliability gaps to unlock both human partners and automated integrations.