# Cigna — API Agent Score

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

Cigna scored 51/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 66/100 (C)
- Developer Experience: 43/100 (F)
- Agent Discovery: 60/100 (C)
- Agent Understanding: 56/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — Versioning declared (info.version="1.0") and url-versioning detected. Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — Only 0% of operations have documented schemas. Investigated: spec 67%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [fail] Auth declared & discoverable — No securitySchemes declared. Investigated: spec 0%, docs 0%.
- [fail] Example coverage — 0% example coverage. Investigated: spec 0%, docs 0%.

### Developer Experience

- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://developer.cigna.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] Description completeness — 50% description completeness. Investigated: spec 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 — 1 of 1 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [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.cigna.com/llms.txt, https://developer.cigna.com/docs/llms.txt). Investigated: docs 33%.
- [warn] Crawlable / AEO — Sitemap present (0 entries) but carries no lastmod values. Investigated: wellknown 75%.

### 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 — 1 of 1 pages appear to be client-side rendered SPA shells (root detected); agents using HTTP fetches will see no content. Investigated: docs 64%.
- [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%.
- [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%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [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] Idempotency documented — 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

Cigna's API program shows strength in basic discoverability and crawlability, but partners and their AI agents face two critical barriers to successful integration: documentation is incomplete and lacks the structure agents need to act autonomously, and the onboarding experience requires significant manual effort before a partner can make a first meaningful call. Prioritizing runnable examples, machine-readable errors, and a self-service portal will unlock partner velocity and reduce support burden.