# Capital One — API Agent Score

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

Capital One scored 52/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 50/100 (D)
- Developer Experience: 66/100 (C)
- Agent Discovery: 69/100 (C)
- Agent Understanding: 51/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [warn] Security & governance hygiene — security.txt present but served only at the legacy /security.txt path; missing or expired Expires. Investigated: wellknown 50%.
- [fail] Example coverage — No detectable code samples across 20 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 — Self-service signup at https://verified.capitalone.com/enroll/pii?external_id=MS_ISL_DigEnroll; no free tier or sandbox language detected. Investigated: docs 100%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://developer.capitalone.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 20 sampled docs pages. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (capitalone/dataprofiler, 743 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — 34 of 34 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.capitalone.com/llms.txt, https://developer.capitalone.com/docs/llms.txt). Investigated: docs 33%.
- [warn] Crawlable / AEO — Sitemap present (34 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/34 tested). Investigated: docs 57%.
- [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 20 sampled pages — likely a CSR-only docs site. 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 0 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

Capital One's API program shows strength in discovery reachability and crawlability, but faces critical gaps in two areas that directly block partner and agent productivity: the API contract lacks concrete examples agents can build against, and there is no runnable, test-backed collection partners can execute to validate integrations. Closing these gaps — alongside adding agent-readable instruction files, structured documentation data, and in-doc code samples — will dramatically shorten the time partners and their AI agents spend guessing at behavior and dramatically increase integration success rates.