# Wells Fargo — API Agent Score

> Score: 62/100 (Grade: C) | Domain: wellsfargo.com | Rubric: 1.0.0 | Checked: July 24, 2026

Wells Fargo scored 62/100 (C), classified "partially-ready".

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

## Summary

- Overall: 62/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 77/100 (B)
- Developer Experience: 65/100 (C)
- Agent Discovery: 69/100 (C)
- Agent Understanding: 76/100 (B)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

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

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.wfhmconsumerevents.com/default.aspx?l=y; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 73% description completeness (target 90%+). Investigated: spec 100%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://developer.wellsfargo.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%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/developer_wellsfargo, 1940 snippets). Investigated: docs 100%, sdk 0%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — 50 of 50 sampled 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.wellsfargo.com/llms.txt, https://developer.wellsfargo.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] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: spec 100%, docs 100%.
- [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 — 10 of 50 sampled pages appear to be client-side rendered SPA shells (root detected); agents using HTTP fetches will see no content. 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 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] 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] 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%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Wells Fargo's partner API program shows solid fundamentals in contract readability and authentication, but agent usability is the most urgent gap — partners and their AI agents cannot safely or reliably execute real workflows today, with no sandbox separation, no runnable collections, and undocumented rate-limit and idempotency behavior. Agent understanding and discoverability are also materially weak: AI agents lack the structured context and machine-readable instructions to parse and act on the API surface without human intervention. Prioritize making the API safe and runnable first, then close the context and discoverability gaps to unlock self-serve partner onboarding at scale.