# The Guardian Life Insurance Company of America — API Agent Score

> Score: 55/100 (Grade: D) | Domain: guardianlife.com | Rubric: 1.0.0 | Checked: July 29, 2026

The Guardian Life Insurance Company of America scored 55/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 75/100 (B)
- Developer Experience: 65/100 (C)
- Agent Discovery: 49/100 (F)
- Agent Understanding: 63/100 (C)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [warn] Machine-readable, versioned contract — info.version="v1" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [warn] Schema coverage & depth — Only 67% of operations have documented schemas. Investigated: spec 75%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.
- [pass] Example coverage — 0% example coverage. Investigated: spec 100%, docs 0%.
- [warn] Auth declared & discoverable — No securitySchemes declared. Investigated: docs 30%, spec 21%, wellknown 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://developer.guardianlife.com/partner/register/activate; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 21% description completeness. Investigated: spec 100%.
- [warn] Quickstart present — Quickstart page reachable (1 variants scanned starting at https://developer.guardianlife.com/getting-started) 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%.

### Agent Discovery

- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [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://developer.guardianlife.com/llms.txt, https://developer.guardianlife.com/docs/llms.txt). Investigated: docs 0%.
- [fail] Registry & SDK presence — Not indexed on Context7 — agents can't pull this API's docs on demand via Context7. Investigated: docs 0%, sdk 0%, cli 0%.

### 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%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 86%.
- [warn] Operation purpose clarity — 0% of operations are agent-inferable. Investigated: spec 20%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 4% (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

- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Pagination documented & consistent — 1 list endpoint(s) exist but no pagination params found. Investigated: spec 0%, docs 0%.
- [fail] Sandbox separation — No sandbox/test server declared across 1 server entries; no test-key prefixes 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

Guardianlife's API program shows meaningful strength in core API design — the contract is machine-readable, schemas are typed, and auth is solid — but the program is not yet ready for self-serve partners or AI agents. The most urgent gaps are in agent usability and discoverability: agents cannot reliably execute workflows because sandbox environments, idempotency, rate-limit, and pagination behaviors are undocumented, and there is no runnable collection to ground them. At the same time, the program is effectively invisible to agents and partners discovering APIs autonomously, with no llms.txt, no registry presence, and no agent instruction context. Prioritize making the API executable and trustworthy first, then close the discovery and change-communication gaps to enable self-serve partner onboarding at scale.